Hi Reid,
see comments inline.
On Aug 21, 2007, at 12:33 PM, Reid Ellis wrote:
On Aug 21, 2007, at 17:19, Mike wrote:
I wanted to comment on the version numbering conversation you
mentioned above and also I heard in the desktop meeting today.
From a build/release point of view, and also from a best-practices
standpoint, the method to use is this:
- when ZBR is hit, branch trunk to 0.7.0 and start the 0.7.0-RC
cycle
- make trunk 0.7.1
- any changes required to 0.7.0 branch due to bugs are patched
and 0.7.0.# is released
---
Bear
The 4-digit version numbering suffers from confusion, e.g. 0.7.1 vs
0.7.0.2 (which one is "better"?)
Just to summarize the two proposals I made in the meeting:
Move the i18n release to "0.7.5", and release interim bug fixes as
0.7.1, 0.7.2, 0.7.3, 0.7.4.
I am a bit confused on how it is known that we need four and only
four bug fix releases
before the i18n release.
Can you explain further.
Thanks,
Brian
Alternatively, change the "0.7.1" bugzilla target release to
someting like "0.7i18n"
- number it appropriately when it's ready, streaming the interim
bug fixes into it, making it just the next 0.7.x release.
Reid
P.S. Hooray for the reply-to change!
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "chandler-dev" mailing list
http://lists.osafoundation.org/mailman/listinfo/chandler-dev
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "chandler-dev" mailing list
http://lists.osafoundation.org/mailman/listinfo/chandler-dev
