[gst-devel] GStreamer needs a maintainer

[Jeroen Zwartepoorte]

I don't see what kind of trouble people have with ChangeLog entries.
Here's what i usually do:

- Update first so you sync with the changes made in CVS (this includes
ChangeLog).
- Run prepare-ChangeLog.pl script which automatically scans your source,
does a diff and generates a ChangeLog skeleton for you (part of the
eazel-hacking module in gnomecvs).
- Fill the skeleton ChangeLog entry.
- And commit (posting the ChangeLog entry in the cvs commit message).

This works really well.

Jeroen

On Wed, 2003-12-17 at 13:14, Ronald Bultje wrote:
> On Wed, 2003-12-17 at 12:28, Murray.Cumming at Comneon.com wrote:
> > > The bad thing is that *every single 
> > > commit* by someone else would cause a CVS conflict in the 
> > > ChangeLog file, because I had a bunchload of changes there 
> > > too.
> > This is a minor annoyance.
> 
> Well, I'm affraid I have to disagree there. It's a huge annoyance for a
> high-traffic project like GStreamer. It'll happen every time.
> *Literally* every time. I personally consider that unacceptable.
> 
> Isn't there a simpler system to do this sort of stuff? I mean, there
> must be a better way to keep track of changes apart from having a
> ChangeLog file?
> 
> Ronald