PhoneGap supposedly releases monthly. In theory, there is no optimal schedule, and my understanding of the Apache Way is to release often mainly to keep the committers and other contributors feeling like their work is hitting the streets often enough to keep contributing.
PhoneGap seems to have lots more committers committing so I can understand monthly. And they seem to have one or two folks who like doing the releases. For us, I don't think we should set a schedule, but if one of you thinks there is enough stuff or it has been long enough, then start a discuss thread and see what others think. For me, it feels like we just did one, and I know that 4.9.1 was minor but it still took "release energy" to produce. Mark Kessler looks like he's going to crank out some fixes and Nick is saying he'll have time soon, so maybe around the end of April would be a good time. I'll try to get everything to build to my satisfaction this week unless something blows up, but I probably won't put it out for a vote. On 4/7/13 7:44 AM, "Erik de Bruin" <e...@ixsoftware.nl> wrote: > +1 on all but "1" > > Making releases is not only about getting new stuff out there, it is > also about attracting attention to the product. Maybe someone (Scott?) > with some more "marketing" background can chime in and voice an > opinion about the "optimal release frequency" or a maybe some variants > we can think about? > > EdB > > > > On Sat, Apr 6, 2013 at 11:54 PM, Justin Mclean <jus...@classsoftware.com> > wrote: >> Hi, >> >>> Are we trying to actually ship a release soon or is this just practice? >> >> 1. About time we did it been several months since the last (4.9 was Dec/Jan, >> 4.9.1 was a very minor update). I like to see us releasing every 2 months at >> a minimum. The longer we leave it the harder it is to make a release. >> 2. We should always be in a state that we can make a release - that's the >> point right? >> 3. We are lagging being in versions of AIR. AIR 3.7 should be out this week. >> 4. There's a fair number of bug fixes that have been checked in. >> 5. There's new experimental components for people to play with. >> 6. Move to git have broken making a release and should be fixed and the >> documentation updated. >> 7. Need to fix CI as well as it did tell up when the release build was >> broken. >> >> Thanks, >> Justin > > -- Alex Harui Flex SDK Team Adobe Systems, Inc. http://blogs.adobe.com/aharui
