[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [cdt-dev] Updated bugzilla Versions/Targets
|
I like the idea of a "Next" target. Then we can re-use this as time goes
on. I guess the problem though is that "Next" for the uninformed onlooker
could mean 4.0.x or it could mean... whatever we're going to number the
Ganymede release.
Or... we could just use "Future" and tag them with a "Ganymede" keyword.
Or... the best of both worlds... create a "Next" target and we tag
everything with the "Ganymede" keyword just to be safe.
===========================
Chris Recoskie
Team Lead, IBM CDT Team
IBM Toronto
http://www.eclipse.org/cdt
Doug Schaefer
<DSchaefer@xxxxxx
m> To
Sent by: "CDT General developers list."
cdt-dev-bounces@e <cdt-dev@xxxxxxxxxxx>
clipse.org cc
Subject
21/08/2007 10:32 [cdt-dev] Updated bugzilla
AM Versions/Targets
Please respond to
"CDT General
developers list."
<cdt-dev@eclipse.
org>
Hey gang, I?ve added a 4.0.2 target milestone and a 4.0.1 version. If you
find bugs in 4.0.1 that weren?t there in 4.0 you can now mark it that way.
Also if you need to push 4.0.1 bugs to the next maintenance release, you
can do that.
I?m struggling with creating a target for the Ganymede release. We?re not
sure what the number will be and you can?t change it once you?ve added it
to bugzilla.
I though we could use Future to denote next release, but we already have
500 bugs on Future. We?d probably have to move them to ??? first. The other
option is to create a new one called ?Next? and then when we do figure out
the number, we could move them all to it.
Opinions?
Doug Schaefer, QNX Software Systems
Eclipse CDT Project Lead, http://cdtdoug.blogspot.com
_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cdt-dev
