F14 os2 testing images available for XO-1 and XO-1.5

Simon Schampijer simon at schampijer.de
Mon Nov 22 06:26:08 EST 2010

On 11/22/2010 11:55 AM, James Cameron wrote:
> On Mon, Nov 22, 2010 at 09:03:28AM +0100, Simon Schampijer wrote:
>> I think we should add a Version field for F14 (e.g. 1.5/1.0 software
>> Build F14).
> I disagree.  The version field is for formal releases.  The reporter of
> a bug may use "Development build as of this date" for the current F14
> builds.  Identify the build version in the keywords field.  This has
> been our practice for the past year.

"Development build as of this date" is ambiguous as we have the 10.1.3 
stream and the F14 stream :/

> On Mon, Nov 22, 2010 at 10:36:03AM +0000, Daniel Drake wrote:
>> You could even simplify it a step further: just put all of them in the
>> F14 milestone without thought. As the scope of the release is not yet
>> defined it's not really possible to do a "real" triage. And knowing
>> what bugs are there could also help us define that scope.
> I agree, just throw them into the F14 milestone.
> trac does not allow us to easily manage tickets for multiple release
> engineering streams.  If you sense a fight over which milestone a ticket
> should be in (10.1.3 vs F14), then I suggest opening a new ticket.

Yeah, I guess I have to do that then. The bad thing is that I have to 
touch tickets then and can not pass that to the reporter by indicating 
the version number. For anyone working on the F14 builds please make 
sure to set the milestone then accordingly on the tickets you are touching.

At least I could stop the initial request from a reporter setting 
milestones ;p


More information about the Devel mailing list