[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [emf-dev] Bugzilla Milestones for Maintenance Release

+1 on less clutter. Might need to open a bug to get some of the old ones removed. Oh, and just for the sake of process comedy, remember that to edit Bugzilla setting thru the Portal / Committer Tools UI, you must log in with your Eclipse ID, nor your Bugzilla email address [1]. I know, crazy.

As to the identification of when a bug's fixed, you can always look at the last comment in the bug, which will tell you what branch & version in which a bug was fixed, eg:

https://bugs.eclipse.org/bugs/show_bug.cgi?id=231574#c6
https://bugs.eclipse.org/bugs/show_bug.cgi?id=233862#c2

Or the release notes.

Or Search CVS.

:)

Nick

[1] https://bugs.eclipse.org/bugs/show_bug.cgi?id=233507

Anthony Hunter wrote:

Hi Christian,

-1 on the 2.4.x, In 2009, how will we know if the bug was fixed in 2.4.1 or 2.4.2 ?

It is safe to use 2.4.1 and 2.4.2 as a start to align with our two scheduled Ganymede maintenance releases.

Cheers...
Anthony
--
Anthony Hunter mailto:anthonyh@xxxxxxxxxx
Software Development Manager: Eclipse Open Source Components
IBM Rational Software: Aurora / GMF / Modeling Tools
Phone: 613-270-4613


Inactive hide details for "Christian W. Damus" ---05/30/2008 12:47:54 PM---Hi, I am finding myself needing to schedule a bug fo"Christian W. Damus" ---05/30/2008 12:47:54 PM---Hi, I am finding myself needing to schedule a bug for my Transaction 1.2



From: "Christian W. Damus" <cdamus@xxxxxxxxxxxxx>

To: 	
emf-dev@xxxxxxxxxxx

Date: 	
05/30/2008 12:47 PM

Subject: 	
[emf-dev] Bugzilla Milestones for Maintenance Release

------------------------------------------------------------------------



Hi,

I am finding myself needing to schedule a bug for my Transaction 1.2 maintenance release, and that raises some practical questions.

I see that the EMF core component does not yet have any milestone(s) created for 2.4 maintenance, but I see that the 2.2 maintenance stream has 2.2.1 and 2.2.3 entries. Curiously, there is nothing for the 2.3 branch (not even the 2.3.0 release).

So, going forward with the various components that we have at various version numbers, I propose that each maintenance branch be identified by a single *.x milestone (e.g., 1.2.x, 2.4.x). This has the benefit of being distinct from the next release (2.5, 1.3) and avoiding clutter in the drop-down list. I don't think it's necessary to identify individual releases on the same maintenance branch, because they happen in serial order and any bug scheduled on the maintenance branch would just go into the next maintenance release.

What do y'all think? If we are agreed, I can volunteer to create the following milestones:

- 2.4.x for Core
- 1.2.x for QTV

(the CDO, Net4J, and Teneo components already have a 1.0.1 waiting and ready).

Thanks,

Christian
------------------------------------------------------------------------

Christian W. Damus
Senior Software Developer, _Zeligsoft Inc._ <http://www.zeligsoft.com/>
Component Lead, Eclipse _MDT OCL_ <http://www.eclipse.org/modeling/mdt/?project=ocl> and _EMF-QTV_ <http://www.eclipse.org/modeling/emf/?project=transaction>


_______________________________________________
emf-dev mailing list
emf-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/emf-dev


------------------------------------------------------------------------

_______________________________________________
emf-dev mailing list
emf-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/emf-dev

--
Nick Boldt :: Release Engineer, IBM Toronto Lab
Eclipse Modeling :: http://www.eclipse.org/modeling http://wiki.eclipse.org/index.php/User:Nickb