Difference between revisions of "Planning Council/March 04 2015"

Latest revision as of 14:25, 4 March 2015

Logistics

Members and Attendees

Note: "Inactive" refers to Strategic Members or PMCs we have not heard from for a while, and have been unable to convince to participate. Those members can become active again at any time. Contact David Williams if questions.

Note: feel free to correct any errors/omissions in above attendance record.
Y = Yes, attended
N = No, did not
R = regrets sent ahead of time
D = delegated
X = not expected

Announcements

• bug 453927 - Naming Mars+1 (2016 Eclipse Simultaneous Release)
  • 'Neptune' and 'Nova' and 'Neo' are dead in the water due to trademarks; Took a new poll of remaining "N-words".

Decision was made to "start over", on accelerated cycle, expanding "letters" to "O and P" in addition to "N", and then having voting at "EclipseCon".

We would try to "vet" the names a little better ourselves ... at least a web-search to see if the name of any other "software product".

Will also including asking community about using "numbers". Seemed the consensus of Planning Council was to use "Year" such as "16" for "2016 June Release" (as a "backup plan") but wasn't that clear on what to do with "Service Releases" ... especially since they are not strictly "Service Releases" as they used to be. One alternative was to use "year and month", such as 16.6, 16.9, but that would make the second "service release" be 17.2 (which, sounds confusing, since sounded like a "major release") so, presumably, if we go the "numbered route", we'd stick with "16" (for 16.0) and then 16.1, 16.2, etc.

The notion of using "years of Eclipse" or "years of Simultaneous Release" (especially the former) was thought to be confusing since could be confused with "year", such as 2016 will be release "15" of Eclipse (which started in 2001).

There was concern expressed (by me :) for full disclosure) about continuing 'the naming process' as we do, since by definition it gravitates towards "popular names" which are the ones most likely to lead to "legal issues". (So, IMHO, we need to be prepared to change the process? Or, use a numbering system?)

Was also suggested to get more guidance from "lawyers", but in the end, does not seem they could give that much guidance, at least in an economical way.

An interesting observation was made that going "the numbered route" sounded more "product-like" than the clever "code names" which sounds more "open source community like" ... but, admittedly, that's not necessarily a bad thing.

• EclipseCon Breakfast: Please RSVP to Wayne. (See his message on Planning Council List).

Previous meeting minutes

• Review previous meeting minutes if you'd like.

Luna SR2

• Congratulations!
• Any thing to document in retrospect?

Mars Planning

• Any issues?
• Improving categories in Simultaneous Release repo? See SimRel/Feature Categories -- Wayne? Have a proposal yet?

Wayne reports that focus will likely change on an improved presentation of "Eclipse Projects" in the "Market Place Client". bug 460564

• Moving "Sim Release Aggregation" to "HIPP Instance". (I hope in time for M6) (dw)

- Besides being "HIPP" jobs will be restructured to have a "validation-only job", a "build with cache" job, and (still) a "clean build") job.

Progress on Action Items

• Improve "aggregator examples/doc". (dw -- in progress).

New Business

• Wayne reminded us of the "greatfix competition" and asked for help "spreading the word".

Next Meeting

• April 1, 2015 - No Fooling! Regular First Wednesday Meeting.

Reference

2013 EclipseCon face-to-face follow-through action items. For original meeting notes, see Planning_Council/March_24_2013 and for discussion leading to action items, see Planning_Council/April_10_2013. For last status update, see Planning_Council/May_8_2013.

Luna Wiki page

Kepler Wiki page

Planning Council/Kepler retrospective

Planning Council Members

Simultaneous Release Roles and Simultaneous Release Roles/EMO