Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cross-project-issues-dev] Planning Council / Europa meeting at EclipseCon - Sunday, Mar 4, 5:30pm, Tasman Room

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.


Bjorn Freeman-Benson <bjorn.freeman-benson@xxxxxxxxxxx>
Sent by: cross-project-issues-dev-bounces@xxxxxxxxxxx

16/02/2007 11:57 AM

Please respond to
emo@xxxxxxxxxxx; Please respond to
Cross project issues <cross-project-issues-dev@xxxxxxxxxxx>

"" <>
Cross project issues <cross-project-issues-dev@xxxxxxxxxxx>
[cross-project-issues-dev] Planning Council / Europa meeting at EclipseCon - Sunday, Mar 4, 5:30pm, Tasman Room

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 to:

Sunday, March 4th (the day before EclipseCon)
Tasman room of the Hyatt (
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
Please RSVP to emo@xxxxxxxxxxx_______________________________________________
cross-project-issues-dev mailing list

Back to the top