Working for the next release

pokorra

Now that the release 0.2.22 is done, I want to mention some rules that we should follow when resolving a bug:

Please always select the version in which the bug will be fixed. Christian had to set the "fixed in version" combobox for many bugs.

For bugs, that did not exist in the previous release, and should not be part of the buglist that we publish with the release notes, please use the DEV version number, eg. 0.2.23 Dev, ie. always with the odd number. For proper bugs or features, please use the even number, eg. 0.2.24. But never leave the "fixed in version" combobox empty. Thanks!

You are welcome now to merge into trunk again.
If we find bugs which require a 0.2.22-1 or more, I will create a new branch off the tag ALPHA-0.2.22.

Thanks,
Timotheus

tim_ingham

Are we all supposed to know what the release version is / will be, by some sort of sixth sense?

pokorra

The next release number is always the highest number available in the combobox.
Of course, we might decide later that 0.2.24 becomes 0.3, but we will work with 0.2.24, and then at the release rename it to 0.3.

hope that makes sense.
though we probably need a sixth sense for the rest of our work anyway...