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.
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?
Cheers,
ma.
_______________________________________________
PySide mailing list
PySide@lists.openbossa.org
http://lists.openbossa.org/listinfo/pyside
