This sounds reasonable to me. All we need is a volunteer to be the release manager. I would rather not be it.
On 12/4/12 12:26 PM, "Greg Reddin" <gred...@gmail.com> wrote: > On Tue, Dec 4, 2012 at 12:27 PM, Alex Harui <aha...@adobe.com> wrote: > >> I¹m leaning towards waiting, but I feel bad for folks who are waiting to >> see their work get out the door. This will truly separate the Apache Flex >> SDK from the Adobe Flex SDK because non-Adobe code will finally be released! >> > > I think we should go ahead and start the process and see if it finishes > before or after graduation. I'd suggest we wait till after graduation to > vote for the release because we can then skip the step of having the vote > on general@. It's true that it may take some time to get the website > migrated, but actually, the dist directories and mirrors that will contain > the release should be available sooner (or already there). So worst case (I > think) is that we've voted on a release and pushed it to the mirrors, and > announced it on the list, but the website is behind. > > Regarding the arduous release process, it will be a bit less arduous once > we're out of the incubator and we'll have more control over the process. > > I expect that the board will approve graduation. I'm not putting words in > their mouths, but I can't think of a situation where a resolution has been > passed through the incubator and the board has rejected it. We should be > prepared for what to do if they reject it, but I will be very surprised if > they do. > > Greg -- Alex Harui Flex SDK Team Adobe Systems, Inc. http://blogs.adobe.com/aharui
