Current status?

[Fabian Fagerholm]

On Thu, 2006-08-24 at 21:27 -0400, Roberto C. Sanchez wrote:
> What is our current status?  I have some time this weekend and next week
> to work on packaging and I would like to see the new SASL packages make
> it in before the general freeze.  IIRC, we only have five or six weeks
> until that freeze.  Where do we currently stand and what can I do?

Here's the latest progress report from me:
http://lists.alioth.debian.org/pipermail/pkg-cyrus-sasl2-debian-devel/2006-August/000051.html
It contains some small tasks that have to do with four patches which are
unclear to me. Note also my reply to that message.

After those are dealt with, my proposed plan is to establish the
criteria for an experimental upload. I guess those criteria could be
pretty lax at the moment, such as "builds packages with the correct
contents in a clean sid chroot". So that would mean I will upload to
experimental once all those patches have been decided on.

As for starting to upload this thing into unstable, the criteria have to
be more strict. In my opinion, we need at least the following:

      * A complete list of reverse dependencies. We need to perform a
        library transition and need to be in touch with those who depend
        on this package. Doing test builds of each of those can also be
        helpful to spot issues early.
      * A special transition is required for OpenLDAP; currently we
        build --without-ldap because of the chicken-and-egg problem
        between it and our package.
      * A double-check of soname versioning and related issues from
        someone with lots of experience. I wouldn't want to risk a
        mistake here.
      * A review of the documentation and preferably better
        documentation on how the package integrates with Debian (how to
        configure SASL in Debian).
      * A blessing from the RM's. If I were in the RM's shoes, I would
        *at least* require assurance that this team is really going to
        work hard on this package to iron out any issues before they
        become a blocker for the release.

This is probably not an exhaustive list. As I've said before, I wouldn't
be too optimistic about getting this into etch -- not that it's
impossible, it just requires a lot of work. So it really boils down to
whether or not each of us can put in that effort.

-- 
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/20060825/eb0ae68d/attachment.pgp