Robert Millan <[EMAIL PROTECTED]> writes:
> On Sat, Sep 27, 2003 at 02:30:37PM -0700, Ben Pfaff wrote:
> > Robert Millan <[EMAIL PROTECTED]> writes:
> >
> > > As you most certainly know, the autoconf team is going to release 2.58
> > > very
> > > soon, and they have rolled out a release candidate known as 2.57d so that
> > > it is properly tested before becoming 2.58.
> >
> > I don't package prereleases.
>
> Why not? Woody+1 will release with autoconf 2.58. If 2.57d happens
> to be broken and breaks hundreds of packages, then you'd rather want to
> discover that before it becomes 2.58.
If you follow the autoconf mailing lists, you know that bugs have
already been found in 2.57d that will presumably be fixed in
2.58. I'd rather let what bugs get fixed in 2.57d get fixed in
2.57d, and then deal with bugs in 2.58 after it comes out.
There is no point to making me deal with bugs that will be fixed
upstream before release. When people report upstream bugs to me
through the BTS, I have to deal with them. Why should I increase
my workload (by packaging an intermediate release, dealing with
extra upstream bugs, etc.) for no benefit?
I'll package 2.58 when it comes out. Not before.
--
<[EMAIL PROTECTED]> <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> <[EMAIL PROTECTED]>
Stanford Ph.D. Candidate - MSU Alumnus - Debian Maintainer - GNU Developer
www.benpfaff.org
