RFC: Handling of NEWS with N active branches

Robert Collins robertc at robertcollins.net
Sun Aug 30 22:32:06 BST 2009


So, we have two branches:
2.0
bzr.dev aka 2.1-at-the-moment.

I think we should duplicate NEWS entries - once for each active branch
they are merged into.

Why?

Because merging 2.0 to bzr.dev *doesn't actually release the fix'.

And in 3 or 4 months time, a fix done for 2.0 and merged to bzr.dev will
be many pages apart, and the ordering in the NEWS file will make it even
harder to tell what it means for 'something fixed in 2.0.1' unless we
sort NEWS chronologically, not numerically.

In dev
2.1b3
2.0.2  <===
2.1b2
2.0.1  <===
2.1b1
2.0
1.18.1

Thats not (IMO) as clear as having the NEWSworthy changes *in 2.1b1* be
*in 2.1b1*.

-Rob
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: This is a digitally signed message part
Url : https://lists.ubuntu.com/archives/bazaar/attachments/20090830/4f5c906b/attachment.pgp 


More information about the bazaar mailing list