|Re: [eclipse.org-planning-council] Reminder of "First Wednesday" Meeting, 10/2, 12:00 Noon (Eastern)|
For your consideration.
As promised, here is my proposal for requirements on projects who wish to do minor releases at SR time.
- First major releases not allowed. Projects must maintain backwards compatibility with the release.
- Projects must follow the ramp down schedule for the SR. The bits for the release must be made available at RC1 and can not be introduced later than that. Bug fixes of course can be made during the release candidate cycle.
- Release review material must be available to the community by RC1 to document the changes and new features in the release.Like to keep it short and succinct. We can discuss and adjust at the meeting or here on the mailing list.
BTW, in full disclosure, CDT will be doing this for Kepler SR-3 with CDT 8.3. So I am in a bit of a conflict of interest here. But I do have vested interest in being clear about the process.
Remember our regularly scheduled meeting is tomorrow, Wednesday, 10/2, at 12 Noon (Eastern).
Please arrange for a delegate if you can not attend.
There's not much on the agenda (representatives are free to add items, if I've forgotten anything) so I hope to discuss "action items", and spend some time discussing "Kepler retrospective" to see if there is anything we should document.
eclipse.org-planning-council mailing list
IMPORTANT: Membership in this list is generated by processes internal to the Eclipse Foundation. To be permanently removed from this list, you must contact emo@xxxxxxxxxxx to request removal.
Back to the top