Re: [cross-project-issues-dev] Planning Council / Europa meeting at EclipseCon - Sunday, Mar 4, 5:30pm, Tasman Room
Please forgive my personal bias (not that of the company for which I work) but IMHO, Service Pack sounds too Microsoft'y and thus carries with it the
implication of breaking changes / problems with installation (think WinXP Pro SP2); Maintenance
abbreviates to "M" and thus conflicts/confuses with Milestones in the
HEAD branch. I like Service Release, as used by IBM JDKs, for example.
+1 for something like Callisto SR1, Callisto SR2, etc... and +1 that this should be on the agenda.
On 2/21/07, John Arthorne <John_Arthorne@xxxxxxxxxx> wrote:
If the subject of release train names
comes up at the planning council, I suggest that you also consider a better
naming convention for maintenance releases. There are obvious problems
with the current "Fall update" and "Winter update"
- it's not flexible, it doesn't scale to more than two or three updates,
and doesn't play well in the Southern hemisphere. The maintenance
releases need a clear, simple "brand name" and/or number to help
reduce confusion and aid in marketing them to the community. I don't
have a concrete suggestion, but something along the lines of "maintenance
release x", "service pack x", etc. As we move away
from using plugin version numbers to identify releases, the need for a
suitable marketing name/number becomes more evident.
Planning Council members (and all the planner-type people
involved with Europa),
By popular request, we have moved our face-to-face Council meeting at EclipseCon
Sunday, March 4th (the day before EclipseCon)
Tasman room of the Hyatt (http://www.eclipsecon.org/2007/image.php?gif=image/floorplan/tasman
5:30pm-7:30pm (after the Commiter
and Project Boot Camp)
- Europa status check
- Europa staging/release sequencing clarification
- provideName issue
- translation project
- other things that arise between now and then
RSVP to emo@xxxxxxxxxxx_______________________________________________