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

Bug#681687: Call for votes on evince MIME entry



I'm calling for votes on the following proposal.  There are
three options - two positive versions, and FD.  In summary
 A.  Do not overrule release team.  It is too late for automation.
 B.  Do not overrule release team.  Defer to them on automation.
 F.  Further Discussion.

Here are the full texts (lines not marked A or B are in both
versions):

    1. The Technical Committee agrees with Neil McGovern's analysis of
       the situation regarding evince's missing mime type entry.

    2. If changes are desirable to our system for dealing with mime
       type entries and desktop files, including changes to policy or
       additional automation, these should be made via the usual
       development and policy amendment processes.

 A  3. We agree with the Release Team that it is now too late to deploy
 A     such automation in wheezy.

 B  3. We defer to the Release Team's decision that it is now too late
 B     to deploy such automation in wheezy.

    4. We do not disagree with the Release Team's assessment that
       the failure of the evince package to provide a mime type
       entry is a release critical bug.

    5. We therefore decline to overrule the Release Team.  The bug
       remains RC against evince.

    6. The release team should clarify which mime types the RC-bugginess
       applies to.  We recommend that the starting point should be those
       mime types advertised by evince via the mime system in squeeze.

Ian.


Reply to: