On Tue, Mar 04, 2003 at 09:53:18PM +0000, Colin Watson wrote:
> On Tue, Mar 04, 2003 at 04:11:02PM -0500, stan wrote:
> > On Tue, Mar 04, 2003 at 07:30:05PM +0000, Colin Watson wrote:
> > > On Tue, Mar 04, 2003 at 02:04:48PM -0500, stan wrote:
> > > > Not idael at all. As a matter of fact, it makes the whole concept of a
> > > > testing release pretty useless.
> > >
> > > No it doesn't. It's designed to help developers get an idea of how close
> > > we are to having something releasable, and to make the release process
> > > itself easier. If some users find it useful, that's great - an added
> > > bonus. But you should still take care when using it on machines
> > > connected directly to the net (which, remember, is not anywhere close to
> > > all Debian systems).
> >
> > Well, then shouldn't it allow "stable" to be released often enough that it
> > acn be used in production> For instance how old are the prel modules, and
> > devlopment environment in it? Ancinet by modern standards.
>
> We're trying, damnit.
Excuse me if I implied anything but hat!
I'm _extremely_ happy with all the good things that are being done _on a
volunter_ basis_ within the Debian developer community. I have never meant
to imply otherwise. If I hacve, the I herby retract such a stament,and
apologize for it!
>
> > > That's nice. When "resources" (i.e. developers) come along who have the
> > > time and skill to start performing testing security updates, it'll be
> > > done: this came up on -devel fairly recently, and all the technical
> > > facilities to allow such updates to happen are there. Until then we can
> > > but admit once again that it's not ideal and shrug.
> >
> > I'm curious as to why it can't be done in conhunction with the stable
> > security fixes?
>
> The fact that most of the developers working on stable security are
> already working completely flat out, perhaps?
Is it possible that some mechanisim could be set up such that a package
which has recieved a security related update in stable, could become the
latest package for testing?
I'm trying to think of a way to leverage the fact the security issues _are_
being addressed in stable into the testing regim.
Perhpas someone who understands the Debian packagin system better than I
could comment on whether this makes sense or not?
--
"They that would give up essential liberty for temporary safety deserve
neither liberty nor safety."
-- Benjamin Franklin
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
