On Fri, Jun 25, 2004 at 11:36:50AM +1000, Andrew Pollock wrote:
> On Thu, Jun 24, 2004 at 06:42:32PM +0200, Adeodato Sim? wrote:
> > then do not many orphaned packages (if not most) fit into one of the
> > proposed resons and should be removed from testing?
> >
> > I think many packages coul
On Thu, Jun 24, 2004 at 06:42:32PM +0200, Adeodato Sim? wrote:
> * Matthew Palmer [Mon, 21 Jun 2004 10:12:22 +1000]:
> > On Sun, Jun 20, 2004 at 02:28:04PM +0100, Martin Michlmayr wrote:
>
> > > I wish more people had an attitude like this. Maybe it would make
> > > sense to ask people on d-d-a t
On Thu, Jun 24, 2004 at 06:42:32PM +0200, Adeodato Sim? wrote:
[snip]
>
> then do not many orphaned packages (if not most) fit into one of the
> proposed resons and should be removed from testing?
>
> I think many packages could benefite from this in-the-middle approach:
> instead of co
* Matthew Palmer [Mon, 21 Jun 2004 10:12:22 +1000]:
> On Sun, Jun 20, 2004 at 02:28:04PM +0100, Martin Michlmayr wrote:
> > I wish more people had an attitude like this. Maybe it would make
> > sense to ask people on d-d-a to review their own new packages and
> > consider whether it makes sense t
On Sun, Jun 20, 2004 at 02:28:04PM +0100, Martin Michlmayr wrote:
> * Matthew Palmer <[EMAIL PROTECTED]> [2004-06-20 11:44]:
> > I'll volunteer to check my own packages, with a couple of recommendations:
>
> I wish more people had an attitude like this. Maybe it would make
> sense to ask people o
* Martin Michlmayr ([EMAIL PROTECTED]) [040620 14:25]:
> * Colin Watson <[EMAIL PROTECTED]> [2004-06-20 12:06]:
> > If as maintainer you want your package not to be released but to remain
> > in unstable, then file a serious bug on the package to that effect and
> > tell the release team.
> Is the
* Frank Lichtenheld <[EMAIL PROTECTED]> [2004-06-20 21:20]:
> I played around a bit, my current stuff (nothing serious yet)
> is at http://people.debian.org/~djpig/pkg-invest/
> status.html at least shows the amount of work we're talking about:
> today it were 3350 new source packages when comparin
On Sat, Jun 19, 2004 at 02:20:38PM +0100, Martin Michlmayr wrote:
> In any case, I'd really like volunteers for something else: check
> which packages are going to ship new with sarge (i.e. which have not
> been in woody or another stable release) and take a closer look at
> them to see if we reall
* Matthew Palmer <[EMAIL PROTECTED]> [2004-06-20 11:44]:
> I'll volunteer to check my own packages, with a couple of recommendations:
I wish more people had an attitude like this. Maybe it would make
sense to ask people on d-d-a to review their own new packages and
consider whether it makes sense
On Sun, Jun 20, 2004 at 01:19:28PM +0100, Martin Michlmayr wrote:
> * Colin Watson <[EMAIL PROTECTED]> [2004-06-20 12:06]:
> > If as maintainer you want your package not to be released but to remain
> > in unstable, then file a serious bug on the package to that effect and
> > tell the release team
* Colin Watson <[EMAIL PROTECTED]> [2004-06-20 12:06]:
> If as maintainer you want your package not to be released but to remain
> in unstable, then file a serious bug on the package to that effect and
> tell the release team.
Is there no cleaner solution so those RC bugs don't show up in the RC
b
On Sun, Jun 20, 2004 at 11:44:53AM +1000, Matthew Palmer wrote:
> Do I bug FTPmasters about getting those two removed from testing, or the
> release team?
If as maintainer you want your package not to be released but to remain
in unstable, then file a serious bug on the package to that effect and
On Sat, Jun 19, 2004 at 02:20:38PM +0100, Martin Michlmayr wrote:
> In any case, I'd really like volunteers for something else: check
> which packages are going to ship new with sarge (i.e. which have not
> been in woody or another stable release) and take a closer look at
> them to see if we reall
* Andreas Barth <[EMAIL PROTECTED]> [2004-06-18 18:38]:
> I'm prepared to do the work for it, but would like to pre-warn the
> other developers in time. Therefor, I would e.g. like to send a mail
> like this to d-d-a:
I think it's a good idea in principle to check which stuff should be
removed.
>
On Fri, Jun 18, 2004 at 08:27:14PM +0200, Andreas Barth wrote:
> * Frank Lichtenheld ([EMAIL PROTECTED]) [040618 19:40]:
> > Hmm, I don't quite understand why this would be a good idea. The
> > packages are not in testing so I would rather not waste more time
> > on them _before_ the release but co
On Fri, Jun 18, 2004 at 11:57:24PM +0200, Andreas Barth wrote:
1. I really hope that we are able to release more often in future.
Releasing only every four years is a dead end.
People have been saying that since I joined the project, if not earlier. :)
2. Please see "exception" below: Of cour
* Michael Stone ([EMAIL PROTECTED]) [040618 23:10]:
> On Fri, Jun 18, 2004 at 08:27:14PM +0200, Andreas Barth wrote:
> >Well, I'm not speaking of investing any time now on them, but just to
> >alert their maintainers and users that if the packages keep on being
> >unfit for release, these packages
On Fri, Jun 18, 2004 at 08:27:14PM +0200, Andreas Barth wrote:
Well, I'm not speaking of investing any time now on them, but just to
alert their maintainers and users that if the packages keep on being
unfit for release, these packages will be removed after release.
Why? I'd actually like to se
* Frank Lichtenheld ([EMAIL PROTECTED]) [040618 19:40]:
> On Fri, Jun 18, 2004 at 06:38:58PM +0200, Andreas Barth wrote:
> > I'd consider it a good idea if we try to get rid of some of the
> > packages that are in unstable, but not in the release of sarge
> > ("release" as in: stable -> sarge). I'm
On Fri, Jun 18, 2004 at 06:38:58PM +0200, Andreas Barth wrote:
> I'd consider it a good idea if we try to get rid of some of the
> packages that are in unstable, but not in the release of sarge
> ("release" as in: stable -> sarge). I'm prepared to do the work for
> it, but would like to pre-warn th
Hi,
I'd consider it a good idea if we try to get rid of some of the
packages that are in unstable, but not in the release of sarge
("release" as in: stable -> sarge). I'm prepared to do the work for
it, but would like to pre-warn the other developers in time. Therefor,
I would e.g. like to send a
21 matches
Mail list logo
