Christian Theune a écrit :

This post refers to Philipp's guide for `Maintaining software in the Zope
software repository` [1].

I noticed that I kept getting confused about maintaining CHANGES.txt entries
when merging bug fixes around, looked around a bit and thought I'd share my


I find that Philipp's guide could be extended/clarified a bit more about this.

Comments, suggestions, etc. welcome.

Hi Christian,

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?




Zope-Dev maillist  -
**  No cross posts or HTML encoding!  **
(Related lists - )

Reply via email to