Re: change sources.list to follow testing, not jessie
On Friday 17 April 2015 11:36:26 Darac Marjal wrote:
> On Thu, Apr 16, 2015 at 04:25:41PM -0500, David Wright wrote:
> > Quoting Joe (joe@jretrading.com):
> > > On Thu, 16 Apr 2015 21:11:06 +0100
> > >
> > > Lisi Reisz <lisi.reisz@gmail.com> wrote:
> > > > As opposed to problems in a fortnight? If you change all of them,
> > > > you will have a whirlwind as soon as Jessie becomes Stable. If I
> > > > were in your shoes, I would change the one reference to testing to
> > > > Jessie. Track Jessie into next month and change all references to
> > > > Jessie to testing or Stretch then, when things have calmed down a
> > > > little.
> > > >
> > > > > Running `aptitude update' with the changes in place does not
> > > > > produce any output that looks problematice (to me). But maybe that
> > > > > is not a thorough test?
> > > >
> > > > It's no test at all. At the moment testing and Jessie are the same
> > > > thing.
> > > >
> > > > But it will be awful the day that Jessie goes Stable because
> > > > everything will immediately update willy-nilly and out of your
> > > > control, all at once, to Stretch (which will be the new testing).
> > > >
> > > > I really should wait a few days if I were you. If I were me I would
> > > > wait at least a month!
> > >
> > > However long the wait, the result will be the same. In fact, the longer
> > > the wait, the more upgrades there will be in one go.
> >
> > This may be true, but there's a difference. If you wait a few months
> > in jessie before moving to stretch, a lot more people will have tried
> > the latter and discussed, maybe fixed, the bugs that crop up.
>
> Just a thought: What do you think people have been doing for the last
> five months?
>
> Jessie froze on the 5th of November 2014. At that point, the idea of the
> released software is clearly defined. The only changes allowed after a
> freeze (as per the Freeze Policy) are: fixes for critical *bugs*, fixes
> for important *bugs* (and then, only until 5th December), translation
> updates and pre-approved fixes (until the 5th January).
>
> I've highlighted those changes which are driven by bugs. Now, the main
> way to find bugs is for people to TEST the operating system. That means
> installing it, using it, adapting it to their needs, updating the
> applications or services which they run atop debian and so on. If
> everyone followed your advice, Jessie would sit on a shelf for five
> months then someone would come along and say "Yes, this has ripened long
> enough" and then it'd be marked as "stable" and people would say "Why
> didn't you spot this glaring bug?"
>
> On the day of release, Debian is saying "This set of packages, at these
> versions, have been tested, approved and we believe they are good enough
> for *everyone* to use". If you don't trust that, then why are you using
> Debian in the first place?
He is suggesting using Jessie. I don't get your problem.
Lisi
Reply to: