The release notes file should be in the top-level directory for the current release

Bug #671862 reported by Vincent Ladeuil on 2010-11-06
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Bazaar
Wishlist
Unassigned

Bug Description

After a few weeks spent working on the new NEWS file arrangement, I feel that editing doc/en/release-notes/bzr-2.3.txt is a bit tedious.

Would people agree to 'bzr mv doc/en/release-notes/bzr-2.3.txt bzr-2.3.txt' followed by 'bzr mv bzr-2.3.txt doc/en/release-notes' when we start the bzr-2.4 series ?

This will require same tweaks to the doc build process but nothing spectacular I think.

Vincent Ladeuil (vila) wrote :

Alternatively we also spoke about having the news entry for the branch to "float" and be inserted in the right release notes file when merged by pqm but the above seems to be a simpler step in the right direction ?

Gordon Tyler (doxxx) wrote :

Apologies if this is off-topic, but something related to this that I encountered yesterday was that I had entered notes into the 2.3b3 section of 'doc/en/release-notes/bzr-2.3.txt' but after I merged bzr.dev into my branch, I had to move my stuff into the 2.3b4 section because a release had been made since I last updated. Minor annoyance but it would be nice if we could think of a way to avoid that.

No objection, as long as the build proces is set up to make it work
properly, and as long as we're careful to to cause last-minute
untested breakage by moving it after the main release. Perhaps we
should move before doing the final beta.

Jelmer Vernooij (jelmer) on 2017-11-09
tags: added: check-for-breezy
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers