The old 3.0 version was in previous Helios milestones (as this was
going to be the version number for the December release). I can send a
note to cross project to notify the wider audience.
Neil
David M Williams wrote:
Gee, we didn't even get to this in
today
meeting!
And, I know you already made the
change
... but, just wanted to document here I agree with it.
Thanks for announcing widely, as you
have, as I know some people pick builds every week or two and
"accumulate them". When something
like this happens, they usually have to do something special to remove
the up-level ones from their pool.
Not
a big deal, if they know that's what's coming. Normally even a note to
cross-project would be in order. Was
this actually in a milestone? I know some people accumulate "all of
helios"
and they don't really follow WTP or
Dali, so might not have seen our own notes and announcements.
Thanks for the attention to detail.
PMC,
I meant to bring this up yesterday in our meeting, but obviously we
didn't have time for this issue. I am proposing to change the Dali
version number of the Helios release from 3.0 -> 2.3. Please take
a
quick look at my proposal below and let me know if you see problems
with
this. I am trying to make this change for M5.
------------------------------------
In an effort to accurately follow the Eclipse Version Numbering
guidelines*, the Dali version number for Helios is being changed from
"3.0" to "2.3" to correspond with the largest version
increment
experienced in the Dali plugins (2.2 -> 2.3). Plugin versions
as always
continue to be governed by the guidelines.
This change does not indicate any loss of planned functionality. Dali
2.3 is still adding comprehensive support for JPA 2.0 and support for
EclipseLink 2.x, but due to the fact that no *Public* API has been
broken from the previous version, it is technically incorrect to
increment the major version segment of the overall Dali feature since
no
plugin has incremented its major segment.
Feature version numbers will be changed in code and 3.0 bugs will be
migrated to corresponding 2.3 buckets. Project metadata and the
project
plan will also be updated, as well as bug queries that point to 3.0
bugzilla entries.
Let me know if you have any question about this. From what I can
deduce, this should not be problematic from a technical (install)
perspective, assuming that previous milestones are not published or
maintained on future production repositories.
Neil
* - http://wiki.eclipse.org/Version_Numbering
_______________________________________________
wtp-pmc mailing list
wtp-pmc@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/wtp-pmc
_______________________________________________
wtp-pmc mailing list
wtp-pmc@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/wtp-pmc
|
