[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

What warrants a non-maintainer release number?

This is part of an email exchange Sven and I had.  Simply put, I put
in a new alpha binary of dpkg-1.4.0.19 that represented nothing but a
recompile to pick up new libg++, ncurses, etc.  Sven suggested that
this warranted a non-maintainer-release number, whereas I had gotten
the idea that non-maintainer-releases suggested code changes.

Policy people?  Any suggestions?

Mike.
--- Begin Message --- 
Michael Alan Dorman <mdorman@viper.law.miami.edu> writes:

> Sven Rudolph <sr1@os.inf.tu-dresden.de> writes:
> > Michael Alan Dorman <mdorman@viper.law.miami.edu> writes:
> > > This is simply a recompile to pick up current libraries, libg++272,
> > > ncurses3.4, etc.  If you could please shove it in, despite the version
> > > number match, I'd appreciate it.  I've cc:'d debian-alpha so they'll
> > > know it's there as well.
> > IMHO you should make such a recompile a regular non-maintainer
> > release.
> 
> I thought about it, but it's literally 0 source changes, simply a
> recompile.  non-maintainer-release suggests source changes to me---as
> I have just done with gpm.

But it is the official mechanism to tell people that something
changed.

Whenever someone reports a bug and includes the complete version
number you have to ask whether he took the old or the new one.

We might want to turn ithis into a policy topic.

	Sven
-- 
Sven Rudolph <sr1@inf.tu-dresden.de>
http://www.sax.de/~sr1/

--- End Message ---
Reply to: