Re: 2.6.13, experimental and 2.6.14-rc ...
On Tue, Oct 04, 2005 at 06:04:10PM +0900, Horms wrote:
> On Tue, Oct 04, 2005 at 09:19:58AM +0200, Sven Luther wrote:
> I've CCed debian-boot, hopefully Franz or another d-i person can comment
> on this. I'd like to get a better understanding of what the issue
> relating to 2.6.12 in testing and d-i is. Though I do not see a week or
> so as being a major issue.
I was going to do it too, but forgot :/
> > > As for 2.6.13 vs 2.6.14-rc, thats really a bit of a moot point.
> > > My feeling is that by they time we get 2.6.13 ready, 2.6.14 will
> > > probably be out, so aiming at 2.6.14-rc for now might be a good idea.
> > > But I'm really more concerned about making sure that the > 2.6.12
> > > release happens. Walidi and Dilinger were doing some fine work in that
> > > area, but it seems they are busy and not much is happening.
> > Ok, that seems to correspond to my own feeling, so let's try to do a 2.6.13
> > upload ASAP to experimental. I am also busy this week, but we should go ahead
> > on that next WE.
> I'm happy to go with experimental any time. Though time is something
> I have none of right now :(
Seems to be the case for everyone. I think it is enough to say the next guy
with free time will make an upload to experimental, and i guess if we all
agree on that, it will happen.
> > Alternatively we can just upload 2.6.13 as-is to experimental now, and fix
> > things as they go, and migrate it to 2.6.14-rc once people get time, but it is
> > important to get packages out to experimental.
> My impresion of experimental, is that it is very green, and as such
You mean the trunk branch ?
> uploading might not be a good idea. It could help to isolate problems.
> Though does anyone have any time to deal with the bug reports in
> a meaningful way? If not, then there might not be a whole log of point
> to the process.
Well, it will move things forward, right now i think we mostly don't know for
sure about the issues, so experimental is a good place to upload things even
for us to test internally. If nothing else it will create a reference 2.6.13
> As for unstable/testing, that is defianately going to give us
> a bigger audience. We just need to find time to get the packages
> together and time to real with user's responses.