Re: slrn version - updating changes.txt
"John E. Davis" <[email protected]>
| Newsgroups | gmane.network.slrn.user |
|---|---|
| Message-ID | <[email protected]> |
Sven Guckes <[email protected]> wrote: >> There may be a way but then the version number is >> tied the version number of the specific repository. >> I prefer to use numbers that track >> those in the changes.txt file. > > ok... makes sense. > > so - then changes.txt needs an update to > reflect the changes unto patch 266, right? In changes.txt, I try to provide a brief one or two line description of every (non-cosmetic) change I make. In that sense it reflects the changes. 266 is the repository version number and changes when the repository changes. For example, if I were to create a new branch of slrn in the repository, its version number would change even though the trunk (where the main line of development takes place) did not change. --John ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/