[Development] Release branch change criteria

Giuseppe D'Angelo dangelog at gmail.com
Sat Jun 29 21:34:56 CEST 2013

On 29 June 2013 00:18, Thiago Macieira <thiago.macieira at intel.com> wrote:
> Every change to the release branch MUST have a Task-number associated and said
> task number must be classified as P0 to P2. Changes without Task-number or
> whose task are P3 or lower must be rejected and bounced off to "stable".
> If you find an issue that is important and you'd like fixed in the upcoming
> release, but there's no task for, open a task and classify it P0 to P2. This
> extra step is to make us think whether the change is really important for this
> release.

I agree, although I see the risk of not being 100% objective when
doing such bug triaging and being very close to a (minor) release...

Giuseppe D'Angelo

More information about the Development mailing list