On Sat, 12 Mar 2005, Steve Langasek wrote: Hi,
> If 2.0.4 will include other significant changes besides the removal of the > fonts, this is really not the time in the release cycle to be packaging new > upstream releases to fix RC bugs that can easily be fixed in other ways. And what is the time in release cycle now? I appreciate your (Release Team) work, but the sad truth is that from my point of view the sarge release is as far away as it was a year ago. A few months ago I losted my hope sarge would be released in predictable future and I have just (re)started normal work on my packages e.g. by uploading to unstable some packages which I hadn't planned to be included in sarge and which I used to upload to experimental. Afterstep was one of them since the 2.0 version was rewritten almost from scratch so it was sure it would have plenty of new bugs. Of course there are some bugs, although not as many as I thought, but despite them afterstep2 is quite usable now and much better then outdated 1.8. > would be far better, IMHO, to repackage the upstream .orig.tar.gz with the > fonts removed, and upload to Debian without waiting for an upstream release > that may not immediately be in releasable condition. I think 2.0.4 will be mostly a bugfix release (like any other release after 2.0.0), so it probably will go to testing anyway. Obviously I can upload repackaged 2.0.3 (and I will do it tomorrow), but thanks to mipsel,arm,etc. there is no warranty it will go to testing before 2.0.4 is released. > > > But for now I'm lowering *temporarily* its priority to have afterstep > > 2.0.3 propagated into testing. > > In the future, please don't do this without talking to the release team > first. OK. I will do. But I don't think lowering the severity changed anything apart from having newer afterstep available for testing in sarge now. Mind you, both previous and current version of afterstep *do* have the bug. Of course I could have uploaded new package only to fix this bug, but then I had to wait another some days for afterstep being allowed into testing. I even thought about doing that until it turned out that 2.0.3 would finally build on mipsel. > (In this case, afterstep 2.00.03-1 has already been accepted into > testing today.) That's great! Best Regards, robert -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
