[haiku-development] Post-alpha 1 changes on dev.haiku-os.org
- From: Niels Reedijk <niels.reedijk@xxxxxxxxx>
- To: haiku-development@xxxxxxxxxxxxx
- Date: Wed, 26 Aug 2009 12:27:04 +0200
Hi guys.
As dev.haiku-os.org maintainer I want to run a few changes through you
for the post-alpha 1 period.
Milestones
---------
I will make a new R1/alpha2 milestone. I am thinking about making this
one around September 9 (the tagging date for alpha 1), though I see
reasons for doing it earlier.
The current R1/alpha1 milestone will be closed as soon as the release
has taken place. All the tickets that are still open will be
reassigned to the R1/alpha2 milestone (though the release coordinator
should decide whether the remaining issues aren't too big to postpone
the alpha 1 first).
Versions
--------
I will do the following:
* The current version (R1 Development) will be renamed to R1
pre-alpha1 so that we can track which tickets were created before
alpha 1 (ideally, these tickets should be checked whether they still
exist in alpha 1 and the version should be changed if so).
* I will create a new version "R1 Alpha 1" for tickets made against
the official alpha images/builds.
* I will create a new "R1 Development" for issues found in post-alpha 1 builds.
Question: which should be the default version? I personally prefer to
make the R1 Alpha 1 version the default, since I imagine that
incidental testers might not be into our version numbering, and this
will point them to the right version right away. At the other hand, it
might be that our regular testers/developers report more issues and
then they'd have to move the version every time.
What do you think?
[Note: Trac does not provide the functionality to 'close' versions,
but it's not that complex yet that we need to do this.]
N.
Other related posts:
- » [haiku-development] Post-alpha 1 changes on dev.haiku-os.org - Niels Reedijk
