Fedora 17 Change Freeze

Peter Robinson pbrobinson at gmail.com
Thu May 3 10:52:44 UTC 2012


On Thu, May 3, 2012 at 11:17 AM, Paul Howarth <paul at city-fan.org> wrote:
> On 05/03/2012 09:22 AM, Paul Howarth wrote:
>>
>> On 05/03/2012 09:17 AM, Peter Robinson wrote:
>>>
>>> On Thu, May 3, 2012 at 9:12 AM, Paul Howarth<paul at city-fan.org> wrote:
>>>>
>>>> On 05/03/2012 08:50 AM, Peter Robinson wrote:
>>>>>
>>>>>
>>>>> On Thu, May 3, 2012 at 8:26 AM, Paul Howarth<paul at city-fan.org> wrote:
>>>>>>
>>>>>>
>>>>>> On 05/01/2012 07:30 PM, Dennis Gilmore wrote:
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> the fedora 17 schedule
>>>>>>> http://fedoraproject.org/wiki/Releases/17/Schedule lists the final
>>>>>>> change freeze as 2012-05-07 this means that you need to make sure
>>>>>>> that
>>>>>>> any changes you want in Fedora 17 final must be submited for
>>>>>>> stable in
>>>>>>> Bodhi before 2012-05-07 there will be a small window on monday where
>>>>>>> you can get your build in still but it is not assured. after this
>>>>>>> time
>>>>>>> only blocker bugs will be accepted to be pushed for stable. please
>>>>>>> work on testing and ensuring anything you want in final has the
>>>>>>> appropriate karma. If you have questions please drop by
>>>>>>> #fedora-releng
>>>>>>> on freenode
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> I have a critical path update that has been in testing since 18th
>>>>>> April:
>>>>>>
>>>>>>
>>>>>>
>>>>>> https://admin.fedoraproject.org/updates/FEDORA-2012-6165/perl-IO-Socket-SSL-1.66-1.fc17
>>>>>>
>>>>>>
>>>>>> It's now over two weeks in testing (no feedback, either positive or
>>>>>> negative) but I still can't push it to stable - why not?
>>>>>
>>>>>
>>>>>
>>>>> Because it's a critical path package and they need at least 2+ karma.
>>>>> I've added one, you'll need to find another.
>>>>
>>>>
>>>>
>>>> I don't believe that's the case any more:
>>>>
>>>>
>>>> http://fedoraproject.org/wiki/Package_update_acceptance_criteria#Updates_to_.27critical_path.27_packages
>>>>
>>>>
>>>> "Updates that constitute a part of the 'critical path' package set
>>>> (defined below) including security updates must follow the rules as
>>>> defined for critical path packages for pending releases, meaning:
>>>>
>>>> * At the time of the request to stable, the update needs to have
>>>> either a Bodhi karma sum of 2 OR
>>>> * It must spend at least 14 days in updates-testing AND have no
>>>> negative Bodhi karma points."
>>>>
>>>> My update meets the second of these criteria, so I should be able to
>>>> push it
>>>> to stable, shouldn't I?
>>>
>>>
>>> The time elapsed is based on when the composes are done as I believe
>>> it's updated during the compose run so 14 days was yesterday so you'll
>>> likely get a message to say it can be pushed to stable during today's
>>> compose then.
>>
>>
>> We'll see, but I'm 100% sure I've been able to push to stable in the
>> past as soon (within a minute at the most) as the "time in testing"
>> period has passed from the time an update has been recorded as having
>> been pushed to testing in Bodhi.
>
>
> I've now got the message in Bodhi that it's been 14 days in testing and can
> be pushed to stable now if the maintainer wishes - but I still can't do it:
> there's no "push to stable" link, editing the update to set "Request" to
> "stable" has no effect, and neither does the bodhi cli client, which reports
> back:
>
>  "This critical path update has not yet been approved for pushing to
>   the stable repository.  It must first reach a karma of 2, consisting
>   of 0 positive karma from proventesters, along with 2 additional
>   karma from the community. Or, it must spend 14 days in testing
>   without any negative feedback."

Right, so it still needs some more karma, it just doesn't need
proventesters karma.

Peter


More information about the devel mailing list