Current status?

[Sven Mueller]

Fabian Fagerholm wrote:
>> Choice a: take our time, ship Etch with code that has barely been
>> maintained in two years and has no good instructions
>> Choice b: put some speed behind it, ship Etch with code that is properly
>> maintained and has no good instructions
>>
>> I'd rather take choice b.  Not saying we need to cut corners, just that
>> we need to prioritize.  If we can get something that is *at least* as
>> good as what we have now, but two years fresher, we are much better off.
> 
> Well, there's of course some opinion and personal preference involved,
> mine, yours, and everyone else's. For instance, I wouldn't call Cyrus
> SASL "properly maintained" -- the people who were most familiar with the
> software at CMU have left, and so far there hasn't been any indication
> that more resources have been allocated. Perhaps that'll change in the
> future.

Hopefully.

> Anyhow, I'm just voicing my concern and I don't intend to be a blocker
> if the team wants to work on getting this into etch. My goal is just to
> have the best possible package and that goal stretches beyond etch.

Sure.

Anyway, I agree with Roberto: The newer upstream release is surely the
better choice. Given the time left before etch release, we basically
have two options:
1) ship the old code and add documentation to it
   - this leaves us with potentially more buggy code, and also with
     worse packaging as we won't have time left to work on the bugs
     and packaging.
2) ship the new code and skip adding documentation
   - this leaves us with hopefully better code and better packaging,
     but with equally bad docs as currently in the archive
Like Roberto, I would go for (2) though we should try to add and/or
update documentation as soon as possible.

cu,
Sven

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 251 bytes
Desc: OpenPGP digital signature
Url : http://lists.alioth.debian.org/pipermail/pkg-cyrus-sasl2-debian-devel/attachments/20061020/828a2dff/signature.pgp