Nag asks committers to merge without taking into account grace period

Bug #1293611 reported by Sandy Carter (http://www.savoirfairelinux.com)
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenERP Launchpad Community Utils
Invalid
Undecided
Unassigned

Bug Description

I have noticed this while checking the nag list:

As soon as an MP has 2 approves, it will suggest to merge it without taking into account the 3 day grace period described here:

http://pad.openerp.com/p/community-review

* A MP cannot be merged before 5 calendar days or 3 working days (based on this thread https://lists.launchpad.net/openerp-community/msg02733.html, https://lists.launchpad.net/openerp-community/msg02735.html, one say 5 calendar days and the other 3 working days, which are close, but I don't think that any final decision has been made)
* That means the MP has at least 2 approved reviews
* But the 5 calendar / 3 working days rule can be lifted if a MP is approved by at least 3 reviewers

Revision history for this message
Guewen Baconnier @ Camptocamp (gbaconnier-c2c) wrote :

The final decision was 5 calendar days.

This 5 day grace period is supposed to be handled by the nag: http://bazaar.launchpad.net/~openerp-community-reviewer/lp-community-utils/openerp-reviewers-nag/view/head:/openerp-nag#L219

But it is broken since rev.30 ('age' has been removed)

Revision history for this message
Guewen Baconnier @ Camptocamp (gbaconnier-c2c) wrote :

(it was working before rev 30)

Revision history for this message
Guewen Baconnier @ Camptocamp (gbaconnier-c2c) wrote :
Changed in lp-community-utils:
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.