[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#658341: Conclusion: upload multi-arch enabled dpkg (in time for wheezy)



On Thu, 02 Feb 2012 08:16:34 -0700, Bdale Garbee <bdale@gag.com> wrote:
> I therefore call for an immediate vote on the following ballot.

With votes from 7 of 8 committee members, all ranking A as their first
preference, the outcome of this ballot is no longer in doubt, and we have
met the required > 3:1 majority.  

The decision of the committee is:

> A. While recognizing the substantial benefits of thorough code review, the
>    Technical Committee believes the goal of multiarch support in the
>    Debian wheezy release is sufficiently important as to warrant accepting
>    the current draft implementation into the archive, even if code review
>    by the primary dpkg C maintainer cannot be completed in time.  However,
>    as much review as possible is strongly desired.
> 
>    The Technical Committee therefore overrides the decision of the dpkg
>    maintainer to require complete code review before upload of the
>    multiarch implementation in dpkg to the Debian archive and sets the
>    following upload dates:
> 
>    February 6th: upload to experimental for general testing
>    February 20th: upload to unstable
> 
>    For each of those deadlines, if no implementation of dpkg with
>    multiarch support has been uploaded to the archive for that
>    distribution by that date, Raphaël Hertzog is empowered by the
>    Technical Committee to upload a version of dpkg with multiarch support
>    to that distribution.  The upload may be done on or after that date,
>    when, in his judgement, the dpkg implementation meets the quality
>    standards expected for a Debian core package in those archive
>    distributions.
> 
>    The Technical Committee strongly encourages anyone with the required
>    knowledge to review the multiarch implementation proposed for upload
>    and provide the results of that review to the debian-dpkg list as soon
>    as possible so that the code can receive as much review as possible and
>    the results of that review can be incorporated into the code by those
>    dates.  Similarly, the Technical Committee encourages as broad testing
>    and review of the experimental implementation as possible so that as
>    many bugs as possible can be resolved prior to uploading it to
>    unstable.

Thank you again to Russ Allbery for help with the resolution text, and
to my fellow committee members for prompt attention to this matter. 

Bdale

Attachment: pgpO1x5pAlHPq.pgp
Description: PGP signature


Reply to: