Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cross-project-issues-dev] Is it to late to change our Ganymede Plans?

> why we need something between 3.4 RC4 and 3.4?

Hopefully you don't! Hopefully everyone is done by RC4, and they then just copy/rename what ever to their final zip files.
(Maybe that's the source of the confusion I'm causing -- I'm not saying everyone will need to do this?)

In some cases, I know teams want to fix, or at least discuss fixing, something after their RC4 build. So, the question is, in that case, what bugzilla milestone target should they use for that?

Sounds like each project may have their own desired way to do that. So much for my attempts to coordinate :)
But, by far, the most important thing is to communicate, so what ever method you find to do that is just fine.  
And ... hopefully there won't be _that_ much need, (that is, hopefully very very few changes).
So few changes it might not even be worth discussing in a coordinated way?
Except, last minute changes are the ones people need to communicate the most!

From: Eike Stepper <stepper@xxxxxxxxxx>
To: Cross project issues <cross-project-issues-dev@xxxxxxxxxxx>
Date: 06/07/2008 04:31 AM
Subject: Re: [cross-project-issues-dev] Is it to late to        change        our        Ganymede        Plans?

Hi David,

I find the RC5 idea confusing.
Can you please once more explain why we need something between 3.4 RC4 and 3.4?


David M Williams schrieb:

That would probably be fine, and maybe could be made to work, but 1) not all projects use "3.4" so then everyone is using something different, which is maybe no big deal, but just seems
conceptually wrong ... and might make communication more complicated instead of coordinated. (But, as I noted, the raw number is what would be used in driver IDs, etc.).

This "RC5" is mostly for bugzilla and giving a common language to discuss "the final bits" (such as ... "are your RC5 bits ready"? Are you going to do an RC5 build? Instead of a different question to each project ... "are your 4.5 bits ready", "do you plan to do a 2.4 build"?

Also, for us, in WTP, we use the naked milestone number, "3.0" in bugzilla to signify "anything that's planned to be done in 3.0" and then once we have
the work predictably done, we assign it a specific milestone. So, at this point, I suspect we still have a bunch of stuff targeted to "3.0" in bugzilla, and we'd have to clean that up quick, to re-use it for a slightly different meaning here at the last step of shutdown.

That's us.

From: Philippe P Mulet <philippe_mulet@xxxxxxxxxx>
To: Cross project issues <cross-project-issues-dev@xxxxxxxxxxx>
Date: 06/07/2008 04:02 AM
Subject: Re: [cross-project-issues-dev] Is it to late to change        our        Ganymede        Plans?

Just wondering.
Why isn't the "3.4" target a fair representation of the 3.4 GA ? This is what we usually would use in our project to denote work done post 3.4RC4.

David M Williams <david_williams@xxxxxxxxxx>
Sent by:

06/06/2008 09:05 PM

Please respond to
Cross project issues

Cross project issues <cross-project-issues-dev@xxxxxxxxxxx>
Re: [cross-project-issues-dev] Is it to late to change our        Ganymede        Plans?

Thanks for some quick feedback. I think if individual projects want to (or already are) using 'GA', that's fine ... but, I'd already entered my webtools targets as 'RC5', so will leave.
(Sometimes it saddens me how my rigid mind must continue to think in the same incremental patterns -- guess that's a  sign of a programmer?)   :)  

Also, I got the bright idea I didn't actually need a new row in that table that had the same dates as subsequent row ... I just added RC5 in parenthesis after 'Ganymede' in the table.

And .. improved the text description.

Thanks again,

= = = =

Note: in the following table, RC5 on the 'Ganymede' line does not mean this final build is a release 'candidate' ... it is still to be the 'final build' for this Release ... but 'RC5' is the suggested "target" to have some consistent terminology in Bugzilla, and similar things, to be able to mark things that are different in the final release build than in the RC4 build. [The full word, "Ganymede" doesn't make a very good bugzilla milestone target, since it's a little too inclusive, and "R" (for "Release") is too short. TODO: next year consider "GA" for this final target?]

Hopefully there will not by ANY differences between RC4, and RC5 ... but, some projects may find they have to make doc additions, readme files, etc., so ... this just provides a way that such changes can be consistently marked, tracked, etc., to better keep everyone informed about what might be different between RC4 and the RC5 (the final released code). [Note: it's probably obvious, but this does not mean "RC5" should be part of the final zip file names or anything. those can still be what ever "final" name they would always have been.]

= = = =

cross-project-issues-dev mailing list


Sauf indication contraire ci-dessus:/ Unless stated otherwise above:
Compagnie IBM France
Siège Social : Tour Descartes, 2, avenue Gambetta, La Défense 5, 92400 Courbevoie
RCS Nanterre 552 118 465
Forme Sociale : S.A.S.
Capital Social : 542.737.118 euros
SIREN/SIRET : 552 118 465 02430

cross-project-issues-dev mailing list


cross-project-issues-dev mailing list

cross-project-issues-dev mailing list

Back to the top