Issue 1 : +1 Issue 2 : -1 (Binding Votes)
Keep existing package names as is until they are deprecated (change for change-sake makes a LOT of extra work, and only increases the stock in Tylenol) , but any new packages should reside in a new package. Carol: Lazy consensious have on record from this thread in Feb. noted that we would have an Apache Flex 4.8 as our first, feature-parity release, and 5.x for the next major 'overhaul' version. -Nick Kwiatkowski Apache Flex PPMC Member On Sat, Mar 31, 2012 at 8:20 AM, Carol Frampton <cfram...@adobe.com> wrote: > > > On 3/31/12 1 :06AM, "Martin Heidegger" <m...@leichtgewicht.at> wrote: > > >I found that the discussion about the "org.apache.flex" package was not > >finished and there is still the ISSUE Flex-7[1] open. > > > >So I suggest that we start voting on that, please vote on following > >points: > > > > 1) Keep the current package names in the first Apache Flex release 4.8 > > +1 [Binding] *Please* keep the current package names. We have so many > other things to get right without adding unnecessary complication. > > > > 2) Change the package names in the first major Apache release 5 > > +0 > > Carol > > > > >Anything beyond that is too far in the future to discuss that now imho. > > > >yours > >Martin > > > >PS.: Please read about the apache voting process [2] if you are not > >sure what the options are. > > > >[1] https://issues.apache.org/jira/browse/FLEX-7 > >[2] http://www.apache.org/foundation/voting.html > >
