Christian Theune a écrit :
On Wed, Jun 18, 2008 at 01:23:20PM +0200, Christophe Combelles wrote:
let's take a real package as an example (on which I recently did some merges)
CHANGES.txt on the trunk:
CHANGES.txt on the 3.5 branch:
Given what you said, what should these files look like?
*Almost* as they look like now, except that the changes from 3.5.1+ on the
trunk would be visible as a change to 3.6. It would have only one entry for
3.5 which would be 3.5.0; and probably the pre-releases leading to the stable
Something like this?
It allows to have a smaller changes.txt, but I see just one problem:
imagine there is an early bugfix in 3.5.1, before 3.6.0 is released.
If I understand well, the 3.5.1 bugfix should appear later in the trunk in the
3.6.0 section, but not in 3.5 ?
The risk is that people will think the bug is fixed in 3.6.0 and not in the 3.5
Zope-Dev maillist - Zope-Dev@zope.org
** No cross posts or HTML encoding! **
(Related lists -