1) Keep the current package names in the first Apache Flex release I am seeing the risk that this would harm current Flex projects and core businesses, and, it might cause heavy refactoring of Flex apps and Flex libs which we shouldn't impose others to deal with. Vote: +1 (Binding) 2) Change the package names in the first major Apache release 5 It is hard to imagine how the Flex 5 release might look like. Therefore I would want to delay this decision ... Vote: 0
- Sebastian On Mon, Apr 2, 2012 at 10:38 AM, Bertrand Delacretaz <bdelacre...@apache.org > wrote: > On Sat, Mar 31, 2012 at 7:06 AM, Martin Heidegger <m...@leichtgewicht.at> > wrote: > > ....please vote on following points: > > > > 1) Keep the current package names in the first Apache Flex release 4.8 > > +0 > > > 2) Change the package names in the first major Apache release 5 > > Big +1, with my mentor hat on: Apache Flex wouldn't be able to > complain if someone else releases code under the spark.foo package, > whereas org.apache.flex.spark.foo clearly belongs to this project. > > -Bertrand > -- Best regards, Sebastian Mohr Adobe Flex Developer, Interaction Designer & Software Architect http://www.linkedin.com/in/masuland Mobile Belgium: +32 (0) 48 887 55 22 Mobile Germany: +49 (0) 170 722 24 87 Skype name: masuland
