Re: g-v-m's failure to release and release-team's failure to notice

[Elijah Newren <newren gmail com>]

On 8/25/05, Luis Villa <luis villa gmail com> wrote:
> On 8/25/05, Elijah Newren <newren gmail com> wrote:
> > On 8/25/05, Luis Villa <luis villa gmail com> wrote:
> > > So... the last four releases of g-v-m never actually got technically
> > > released, compare:
> > >
> > > http://ftp.gnome.org/pub/GNOME/sources/gnome-volume-manager/1.3/
> > >
> > > with:
> > >
> > > http://primates.ximian.com/~fejj/gvm/
> > >
> > > This is a real problem. I'm willing to cut some slack here and not
> > > scream too much bloddy murder because people will have been building
> > > out of CVS, but...
> > >
> > > (1) the release team needs to develop a better way of flagging shit
> > > that doesn't get released regularly. I guess it should go somewhere in
> > > http://live.gnome.org/ReleasePlanning/MakingARelease but I'm not sure
> > > where.
> >
> > This can be done on window with the release-diff script in
> > releng/tools/release_set_scripts.  Example:
> >
> > $ ./release-diff --same /ftp/pub/GNOME/desktop/2.10/2.10.2/
> > /ftp/pub/GNOME/desktop/2.11/2.11.92/
> > gnome2-user-docs          2.8.1      2.8.1
> > gnome-keyring             0.4.3      0.4.3
> > gnome-mag                 0.12.1     0.12.1
> > gnomemeeting              1.2.1      1.2.1
> > gnome-speech              0.3.7      0.3.7
> > gok                       1.0.5      1.0.5
> > gst-plugins               0.8.10     0.8.10
> > gstreamer                 0.8.10     0.8.10
> > gucharmap                 1.4.3      1.4.3
> > libgail-gnome             1.1.1      1.1.1
> > librsvg                   2.9.5      2.9.5
> > libxklavier               2.0        2.0
> > scrollkeeper              0.3.14     0.3.14
> > startup-notification      0.8        0.8
> >
> > It's kind of annoying in that it only works on one release set at a
> > time (e.g. 'desktop' in this example) and that it requires full paths.
> >  It'd be nicer if it worked on all release sets and only required the
> > release version numbers, e.g.
> >    release-diff --same 2.10.2 2.11.92
> > If you like, I could work on fixing it up to work like that and then
> > add a comment to the wiki requesting that people do so and publish the
> > results with each release.
> 
> That would be great. At the very least what is currently there should
> be documented by somebody.

I documented all the scripts in releng/tools/release_set_scripts a
little while ago.  One just needs to view the top portion of each
script to see it.  Of course, adding something to the wiki as well
probably also makes sense, but since Jeff is going to fix it up I'll
wait off on that...  :)