On Thu, Jan 27, 2011 at 11:03 AM, Matti Airas <matti.p.ai...@nokia.com> wrote: > Hi list, > > Now that we've been in the beta period for quite some time, we've managed to > get the Bugzilla backlog in control, and it'd seem that the number of new > bug reports is slowly decreasing, I think we should be quite close to the > 1.0 release already, but I'd like to hear more opinions about this one (also > from the core dev team guys, since we haven't discussed this internally > recently). > > What do you think? Is PySide getting stable enough for the 1.0 label? If > not, what's still missing? I don't think we can realistically aim for a > perfect 1.0 release, but it should at least be good enough that any > developers attracted by the "1.0 promise" shouldn't have their fingers > burned by a premature release.
In my opinion we can wait for more 2 betas (beta5, beta6) then if any critical bug appear, we can consider stable to a rc and then the 1.0. > > When would be the right time to make the release? We'll still have beta5 > late next week, but two weeks after that, would we be already all set for a > release candidate? IMO, the release candidate should be really a candidate > for the final release - we make changes between the rc and final only if > there are uncaught regressions in the rc. > > How about the release cadence after 1.0? I hope that by doing the release > candidates, we can avoid any brown paperbag followup releases, and we could > cool down a bit. The two-week release cadence I've insisted upon has been > taxing for both the core dev team (especially for the guys doing integration > to Fremantle, Harmattan, and MeeGo), but also for our valued community > packagers. I still like the predictability of the time-based release cycle, > but maybe monthly releases would be sufficient at first? If the 1.0 was stable enough we can extend the developer time between the releases and I think a release every 2 or 3 months will be nice. Other pointer to consider is how will proceed with the developer process, if we will keep working on bug fix, or we can think out the box and start implement really new things like my dream of implement some introspection like "PyGObject". If implement new things is allowed we will need work in 2 branchs, because we need keep 1.x with bug fix, and the new 2.x, and this demand some extra effort. Ok this is all -- Renato Araujo Oliveira Filho Instituto Nokia de Tecnologia - INdT Mobile: +55 (81) 8704-2144 _______________________________________________ PySide mailing list PySide@lists.openbossa.org http://lists.openbossa.org/listinfo/pyside
