EMAIL PROTECTED]
07/13/2007 10:49 AM
Please respond to
Equinox development mailing list
To
Equinox development mailing list
cc
Subject
Re: [equinox-dev] What to do with 3.3.1 candidate bugs and milestones
So far, the respondents want #2. Tom was just observing that #1 has been
the case in the
elopment mailing list
To
Equinox development mailing list
cc
Subject
Re: [equinox-dev] What to do with 3.3.1 candidate bugs and milestones
ok. in theory I support #2 but if everyone else is doing #1 then there
may be more merit in consistency. there is some logic that says things
r
Thomas Watson <[EMAIL PROTECTED]>
Sent by: [EMAIL PROTECTED]
07/13/2007 08:59 AM
Please respond to
Equinox development mailing list
To
Equinox development mailing list
cc
Subject
Re: [equinox-dev] What to do with 3.3.1 candidate bugs and milestones
No we have not done #2 in th
-0=noop&value0-0-0=
Tom
Jeff McAffer <[EMAIL PROTECTED]>
Sent by: [EMAIL PROTECTED]
07/12/2007 09:19 PM
Please respond to
Equinox development mailing list
To
Equinox development mailing list
cc
Subject
Re: [equinox-dev] What to do with 3.3.1 candidate bugs and milestones
i t
i thought we were all already doing #2...
Jeff
Thomas Watson <[EMAIL PROTECTED]>
Sent by: [EMAIL PROTECTED]
07/11/2007 01:42 PM
Please respond to
Equinox development mailing list
To
equinox-dev@eclipse.org
cc
Subject
[equinox-dev] What to do with 3.3.1 candidate bugs and mile
2)
Thomas Watson
<[EMAIL PROTECTED]
com>
.
John
Thomas Watson <[EMAIL PROTECTED]>
Sent by: [EMAIL PROTECTED]
07/11/2007 01:42 PM
Please respond to
Equinox development mailing list
To
equinox-dev@eclipse.org
cc
Subject
[equinox-dev] What to do with 3.3.1 candidate bugs and milestones
Each major release the same thing h
TED]
Sent by: [EMAIL PROTECTED]
2007-07-11 13:42
Please respond to
Equinox development mailing list
To
equinox-dev@eclipse.org
cc
Subject
[equinox-dev] What to do with 3.3.1 candidate bugs and milestones
Each major release the same thing happens. We start fixing bugs in HEAD
for the
Each major release the same thing happens. We start fixing bugs in HEAD
for the next major release but find a few fixes that we would like to also
release into a maintenance release. Then we have to decide what to do
with the status of the original bug report which was used to release the
fix
