Sounds fine by me ... I was told "component
leads contribute them" in the context of talking about access control
for projects which are delivered with Eclipse, but not directly part of
the Eclipse Project (namely, Equinox and P2) and believe in those cases
the component leads are committers in Eclipse too.
So, other than that, unless someone
says otherwise, I think it would be up to each component how they delegate
and divide up the work. I think ultimately, the component lead is responsible
for the N&N, but it'd be quite understandable that they'd have committers
submit their pictures and descriptions directly, and their role would be
to make sure it all "hangs together", is consistent, doesn't
have duplication, etc. So, assuming that is still the way your component
wants to do it, I'd say "business as usual".
This effort (of putting on the web)
is entirely an effort to make things easier, not harder, so if I say something
that "sounds like more work" then I have probably said it wrong.
Lars Vogel <lars.vogel@xxxxxxxxx>
mailing list of the Eclipse project." <eclipse-dev@xxxxxxxxxxx>,
mailing list <equinox-dev@xxxxxxxxxxx>, eclipse-releng@xxxxxxxxxxx
07/30/2014 02:42 PM
Mars M1 is upon us!
What is unclear to me, if now the component leads should
from now on create the N&N. At least in platform.ui the committer added
there entries directly to the document.
Please clarify, if we still should add entries to the
It's surprising how quickly the relaxing summer goes by, eh?
It turns out our Mars M1 is "next week" (our +0 deliverables
due on 8/8 -- and there will be a 2 week window for everyone else, so the
"Simultaneous" Mars M1 will be complete on 8/22).
This means our "stabilization week" begins this Sunday 8/3, when
we start doing 2 I-builds per day, from Sunday 8 PM to Wednesday 8 PM with
the usual sign-off on 8/7.
New and Noteworthy contributions should be made on by end-of-day Wednesday,
8/6 -- and we are going to try a new procedure this development cycle.
Instead of putting N&N in the "news repository" (and copying
a bunch of files around) we will put it directly in our "website repository".
See bug 437930
All component leads should have access to this website repo, and if you've
never used it, the URL is
In the event a component lead can not do it (such as on vacation, or similar)
and in the rare case the person they delegate to, does not have write access,
you can simply reply to this request with attached patch, or add to a bugzilla,
and we'll be sure it gets in there.
I have updated our build
schedule with all this information -- just for
M1, so far -- but wanted to broadly send out this note to increase the
chances everyone sees it ... since it has caught me be surprise and we
are so close to the deadlines.
And, don't forget, our Luna SR1 RC1 is just a couple of weeks away -- but,
we'll worry about M1 first.