Current status?

Fabian Fagerholm fabbe at paniq.net
Sat Oct 21 07:05:33 UTC 2006


On Fri, 2006-10-20 at 22:57 +0200, Sven Mueller wrote:
> Anyway, I agree with Roberto: The newer upstream release is surely the
> better choice.
[...]
> Like Roberto, I would go for (2) though we should try to add and/or
> update documentation as soon as possible.

I agree with Roberto, too: the newer upstream release is the better
choice -- in principle. That's why I started this project ;)

But whether or not we *can* ship the new version in etch -- as opposed
to "try" or "want" -- depends on making a working package, making it
integrate with other packages, testing the package, testing the
integration, working out an upgrade path, etc, and even then, the final
decision is up to the ftp-masters and RMs.

So our part is what it's been from the start of this project: work. :)

The other questions are related to quality, be it in the form of
usability, reliability, maintainability, availability of documentation
or anything else. As maintainers, we have to draw a line and say "this
is the quality we are prepared to offer". Personally, I would set the
quality requirements quite high, but as I said, the team decides -- and
the team takes responsibility of that decision. That's all I'm saying :)

And now, back to work :)

-- 
Fabian Fagerholm <fabbe at paniq.net>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
Url : http://lists.alioth.debian.org/pipermail/pkg-cyrus-sasl2-debian-devel/attachments/20061021/7225c473/attachment.pgp


More information about the Pkg-cyrus-sasl2-debian-devel mailing list