1 On Tue, Jul 14, 2009 at 01:17:25PM -0400, W. Trevor King wrote:
2 > On Wed, Jul 15, 2009 at 12:54:05AM +1000, Ben Finney wrote:
3 > > "W. Trevor King" <wking@drexel.edu> writes:
5 > > > On Tue, Jul 14, 2009 at 10:36:26PM +1000, Ben Finney wrote:
6 > > > > Please, no. Timestamps aren't version strings, that's conflating two
7 > > > > pieces of information with very different meanings. Correlating the
8 > > > > two is the job of a changelog.
10 > > > Which we don't bother keeping (also NEWS), since "bzr log" works so
13 > > That's not a changelog, that's a commit log of every source-level commit
14 > > made. Far too much detail for a changelog of *user-visible* changes
15 > > associated with a release.
17 > I need a user around to help me determine "user-visable" changes ;).
18 > My labmates loose interest after be init/new/comment :p. None of
19 > which has ever changed, other than set-root -> init ;).
21 Thinking about this some more, I think that the role of the
22 main-branch is to officially sanction the current state of the code as
23 "released". If a series of commits will leave a branch in a
24 known-unusable form, they should be carried out in some appropriately
25 named development branch. Then the log of commits to the main branch
26 ("bzr log -n 1" for bzr > ) should produce a fairly respectable
27 changelog. Obviously we are all quite guilty of doing most of our
28 development in single branches, but it may be a useful model going
29 forward. This also means that _every_commit_ to a main branch would
30 be an official release.
33 This email may be signed or encrypted with GPG (http://www.gnupg.org).
34 The GPG signature (if present) will be attached as 'signature.asc'.
35 For more information, see http://en.wikipedia.org/wiki/Pretty_Good_Privacy
37 My public key is at http://www.physics.drexel.edu/~wking/pubkey.txt