[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: vote



> >    option 3:  wait for 2.1's release to do potato debs

I'm actually going to go with Option 2...2 archives (both 2.0.1 and 2.1)

> If I have a coice, I prefer stable packages over new features (within
> reasonable limits - I guess you could argue that I really should be
> running KDE1 then...). After all, that's why I'm running Potato, not
> Woody.
> I'd vote for option 2, if (or once) Ivan got the impression that the 2.0.x
> packages have settled down completely, and there is nothing more to fix
> there from a packaging point of view. Is upstream work still continuing on
> the bugfix branch (towards a 2.0.2) ?

there is no 2.0.2...2.0.2.  

In fact, one of the main reasons 2.0.1 isn't as stable as it could be for
potato is that I'm mixing 2.1 with 2.0.1...

for example...the kdm that comes with 2.0.1 has issues...so to fix those issues
I'm have been backporting the 2.1 version which is far more complete and 
is much much better. But, it's a new port so it has bugs (which are getting
worked out extremly fast).

Same thing with a few other packages (knode, kpackage, kmail)

I've been very selective in this...but it still leads to some uncertainty...
Plus it doesn't help that we have been lab mice for i18n patches to QT and KDE.

IMO very few bug fixes with into 2.0.1 after 2.1 kicked off...there were some
major fixes and some security fixes but it was mostly for i18n work.  2.0.1
is not something that Debian would call stable...it has too many major bugs...
If Debian were to freeze woody right now I would be quickly uploading 2.1-beta1

:)

Now...what I plan on doing is to do 1 more round of 2.0.1 packages.  These will
be built on top of QT 2.2.3 and will have more fixes to the stuff I've back
ported plus some other things I've been fixing.

Once I get these packages done I'll be immediatly moving on to 2.1-beta1 
packages.  

-- 
----------------
Ivan E. Moore II
rkrusty@tdyc.com
http://snowcrash.tdyc.com
GPG KeyID=90BCE0DD
GPG Fingerprint=F2FC 69FD 0DA0 4FB8 225E 27B6 7645 8141 90BC E0DD



Reply to: