Am 11.10.2010 17:40, schrieb Matt Madia:
Now that things have calmed down with GSoC, networking, and mediaplayer+mediakit, would it be a good time to start thinking about R1/A3? A while back, I started organizing some thoughts about the R1/A2 release process. For now, it's at http://dev.haiku-os.org/wiki/SandBox Basically it boils down to enforcing self-discipline to commit only fixes during the actual release process, instead of "this changeset shouldn't have any negative affect". This would reduce the need/workload for a formal branch maintainer and would hopefully allow us to channel our time and energy on developing a stronger QA for the release process. http://dev.haiku-os.org/wiki/R1/Alpha2/ImprovementsSinceRelease This has some items, but could really use edits by anyone. (even if someone without wiki rights wanted to prep some text on an enhancement ticket) Are there any really important issues that should be fixed before R1/A3?
I think we should fix the Intel driver issue. Besides that one, I think everything is in quite good shape compared to the Alpha2. (By which I just mean it's either better or not worse.) I regret we can't call the next release Beta 1, but for that we would need to be feature complete, which we aren't without package management. I would propose that the Coding Sprint before BeGeistert focusses on bug fixes, and that we release Alpha 3 at BeGeistert. But at the same time I regret to say that I can't participate in the Coding Sprint, and so this is not up to me at all. It just seems fitting that we could finally use a Coding Sprint to polish the next release, like was often intended, and this time the Coding Sprint precedes BeGeistert again. It's up to the participants. :-D
Best regards, -Stephan