RE: When can I include my package in stable?
Thanks everyone for your answers!
Since I wasn't counting on making it into the current frozen, and there
isn't a great many people asking for kvirc to be part of stable, I am not in
a great hurry to make that happen. I was just wondering whether it required
any special effort on my part to get it there.
So, I will take the time to fix the build problems for kvirc on arm, m68k
and powerpc and then make it pass the autobuilders. The next stable should
be like, what, another 6 months or so? Plenty of time for me then :)
> -----Original Message-----
> From: Robert Bihlmeyer [mailto:email@example.com]
> Sent: Thursday, September 06, 2001 8:39 AM
> To: firstname.lastname@example.org
> Subject: Re: When can I include my package in stable?
> Robin <email@example.com> writes:
> > What are the conditions for a package to be included in stable?
> You can't get your package into the current stable (potato) unless it
> is tremendously important, and another point release is made. So I'll
> assume your talking about the next stable release (woody).
> For this you mainly have to get into testing. Then, unless your
> package is removed again due to major problems, it will end up in
> stable when release time comes by.
> > Currently, I maintain the kvirc (and kvirc-doc, kvirc-dev) packages
> > which have been in unstable since June 20 this year. There are no open
> > bugs against either of the packages anymore and I think that from a
> > quality point of view, it could be included in stable.
> Look for your package on
> <URL:http://ftp-master.debian.org/testing/update_excuses.html>. It
> will tell you that some archs (arm, m68k, powerpc) had trouble
> compiling it. Links to relevant build logs are included -- review
> those and try to fix the bugs.
> Also note that normally versions younger than 10 days are not
> considered for moving to testing ... but that also means that if you
> upload every 7 days, your package will be ignored until you slack off
> a bit.
> > Also, with the freeze currently in progress, do I have to wait with
> > this?
> Only base is frozen ATM.