[Pkg-crosswire-devel] Packaging Project Planning
dmitrij.ledkov at gmail.com
Wed May 20 14:10:39 BST 2009
2009/5/20 Eeli Kaikkonen <eekaikko at mail.student.oulu.fi>:
> On Wed, 20 May 2009, Dmitrijs Ledkovs wrote:
>> > Is very close to 2.0 rc1, so by the time our SWORD 1.6.0 packaging is done
>> > we may have a BT 2.0. I'm not sure we should put 2.0beta2 into Debian
>> > unstable, although we could if necessary/appropriate.
>> I'm a little bit uneasy about betas in unstable. They do automaticly
>> migrate to testing.... ~70% of Debian users run testing....
> Lest you get a wrong picture, I want to emphasize that BibleTime has
> been in a good shape for a while and we are conservative in versioning.
> My statements above which may sound negative against the quality of
> BibleTime are due to my general high quality standards and don't mean
> that BibleTime 2.0 final would be worse than any other application - on
> the contrary.
Ok, my cretiria for inclusion up for discussion:
1) Compilies with sword 1.6
2) Runs with sword 1.6
3) Runs with KDE 4.x
4) No major release-critical bugs (Data loss, System halt, etc)
5) Any other known bugs documented in release notes
6) Upstream should set a target date for 2.0 release before Debian
Import Freeze - 25th of June
Let's rut bibletime through 1-3, upload the current version to the PPA
and ask wider community to test it from the PPA. This should cover
1-4. And 4-5 is left to the upstream =D
With best regards
Dmitrijs Ledkovs (for short Dima),
Ледков Дмитрий Юрьевич
More information about the Pkg-crosswire-devel