Mailing-List: contact flex-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: flex-dev@incubator.apache.org
Received-SPF: neutral (nike.apache.org: local policy)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Apple Message framework v1251.1)
Subject: Re: Codename for the new version?
From: Justin Mclean <justin@classsoftware.com>
In-Reply-To: 
 <CAAd0WrYZt1J-XsOzz=SghobqM-Nnd5Jm3U0zdfE10BT5r4mJEA@mail.gmail.com>
Date: Thu, 26 Jan 2012 14:25:11 +1100
Content-Transfer-Encoding: quoted-printable
Message-Id: <927E3B79-96E1-46D5-B266-658D7B365CEE@classsoftware.com>
References: 
 <CAA2EYBwPwb1tPR_ZB4MZybGQUdziON0RK+AUh+oayJExXbg+_g@mail.gmail.com>
 <CAAd0WrajYGECHiQwrvMpv_yMrMCB0OrXaoG1_TH6hQEsVABMaA@mail.gmail.com>
 <4B74E9B3-F5A2-4E5E-A3CD-44710E705C76@classsoftware.com>
 <CAAd0WrYZt1J-XsOzz=SghobqM-Nnd5Jm3U0zdfE10BT5r4mJEA@mail.gmail.com>
To: flex-dev@incubator.apache.org

Hi Jonathan,

> You could always work with a committer and push up your idea.
Sure but would it then go under the committers name not yours? And you =
have to go through them for every check in or change. Not that I think =
it's a big issue I've just seen a few people on the list suggest/imply =
that anyone can place code on the whiteboard area when it's not quite as =
straight forward as that.

> Ultimately the idea of a "codename" goes back to the idea of a =
"roadmap"; and this has been discussed before on the list.
True "codenames" fit in more with the traditional project/release cycle. =
But as we don't know what the next version of Apache Flex is going to be =
(4.7 or perhaps 4.8 seem likely) perhaps coming up with a code name for =
is is a good idea. How about picking a name of an old arcade game? =
There's a wide range of names and it has geek appeal.

Ah looking at the couple of responses that just come in I guess there's =
a clear consensus on it and that's a no to code names. :-)

Thanks,
Justin=