[ To save effort for the reader, lets start with unrelated notes: Note 1: I think it's about time to release -7, as we have a large number of pending bugs. Whoever releases it, please fix the cyrus2.3 changelog accordingly. Note 2: I have been back (though I forgot to mention it) from my Semi-Vac mentioned in <[EMAIL PROTECTED]> for a while. I am all settled into college, and am currently using Cyrus work as an excuse to avoid my Lasers and Photonics homework. Do be advised I have joined CU AUV (www.cuauv.org) and may have less free time, but we'll see. ]
Now for something completely different.
I've been working on the Cyrus 2.3 packages that Farzad provided. They
are currently in build able shape, but need some more work still. Here
is my thoughts on the steps to 2.3 release.
1.) Finish packaging work - Several items
1a) Review the diff of debian/ between 2.2 and 2.3. I merged in
Farzad's packages without reviewing the complete diff and this needs to
be done prior to release.
1b) *NOT ME* Someone who knows it (*Cough* Sven *Cough*) has to fix
the idle method selection patch to work with 2.3. It'd be nice to submit
it upstream this time. Also, the kolab patch needs to be reviewed, I
think we applied it (41- I believe)
1c) *ALSO NOT ME* - Review all the stuff I did in the past few
commits to make sure I didn't fuck up. Pay special attention to the POT
handling.
1d) I know I'm forgetting something, so I'll leave space for it here.
1e) Actually, I'm sure there is more than one thing I'm forgetting.
2.) Upload to new queue for experimental. At this time mark the bug as
pending. I'll consider this one a race between our team and elmo. We'll
see whether my account gets created before or after the first package
ready for experimental. My money is on the team.
2.5) Make sure fixed-in-experimental tag gets applied to that bug once
it gets in.
3.) Maintain 2.3 package in experimental until upstream considers it stable.
4.) Once it's stable, release to unstable. This is the 2nd race. This
time, I'm actually betting on elmo, though it's a tough decision.
5.) ???
6.) PROFIT!!!!!
Benjamin
signature.asc
Description: OpenPGP digital signature
