Closed GoogleCodeExporter closed 9 years ago
I think changelog files are an artifact from revision control systems that
nobody's used for the last twenty years.
We can either generate one from our git log or our tags, or we can just remove
that file.
Original comment by dsalli...@gmail.com
on 19 Apr 2010 at 4:33
How I can find out changes if I download .tar archive from
http://code.google.com/p/memcached/downloads/list ?
Original comment by feni...@gmail.com
on 21 Apr 2010 at 9:01
I'd prefer an up-to-date Changelog -
no matter which version control system is used.
creation from git log would be fine for me.
Original comment by dl4...@gmail.com
on 21 Apr 2010 at 9:07
I believe it would be much better to maintain changelog with user-visible
changes
outlined. Having good changelog simplifies upgrades a lot.
Creating one from git would be better when nothing, but it's likely to be
polluted with
minor/non-user-visible/intermediate changes, and will have much less
signal-to-noise
ratio.
Original comment by mdou...@gmail.com
on 21 Apr 2010 at 10:01
If you would like to volunteer to maintain notes, that's fine. In the
meantime, I'd just dump the tags like this
(maybe reversed):
git tag | grep -v rc | xargs -n 1 git cat-file tag
Original comment by dsalli...@gmail.com
on 21 Apr 2010 at 6:26
Pretty sure we're good if we just link to the new release notes wiki page at
the top
of the changelog as the source for future changelogs. We do write decent
changelogs
abstracted from the git tree, they're just in the wiki (and in the tags) now.
I'll push a patch for this, unless someone whines :P
Original comment by dorma...@rydia.net
on 22 Apr 2010 at 8:36
Original comment by trond.no...@gmail.com
on 11 Nov 2010 at 12:39
Original issue reported on code.google.com by
feni...@gmail.com
on 19 Apr 2010 at 10:17