[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [p2-dev] newbie committer question
Thanks for posting this John,
As someone who has been "around" Eclipse for a while (but only recently contributing to a core project), I wondered how much thought was given to the "timing" of code releases. A professor at Queens pointed me to a study that showed the majority of Eclipse bugs are introduced on Friday, and the researchers chalked it up to "Developers are tired on Fridays", where as Mondays saw very few bugs. I imagine this phenomenon is more likely related to Eclipse build schedule.
It might be a good idea if we could communicate some of your advice to the wider Eclipse community so people have a better sense of when particular patches / features are likely to be released.
On Thu, Apr 16, 2009 at 10:52 AM, John Arthorne <John_Arthorne@xxxxxxxxxx>
The only other general piece of advice
I would give is to be sensitive to the rhythms of the build and release
cycle. On a weekly basis, integration builds are every Tuesday morning.
This means releasing changes on Monday night there is no chance to verify
in a nightly build before contributing to a real build. A good time to
release larger changes is around Wednesday after the weekly build is out
of the way. In a similar vein, releasing big changes right before milestone
week is risky, but right after a milestone ideal. During milestone week
itself we try to keep changes down to a minimum - mostly major bug fixes
or polish items that would be embarrassing to appear in a milestone build.
At that time we're mainly focused on producing solid builds, and will often
accept leaving a bug in the code rather than risking destabilizing the
milestone (depending on the nature of the bug, the complexity of the fix,
and how close we are to Friday).
During the release candidates we progressively
increase testing and lock down on changes according to the end-game plan
. If you ever want a second a opinion on timing for releasing a change,
just ask. Also if you just want another set of eyes on a change in code
you aren't familiar with, you can always ask someone else for a review
(I usually look at the revision history of a file to see the best person
to ask when I want a second opinion). As a committer you don't need any
review for releasing changes, but we still frequently do reviews between
committers when someone isn't completely comfortable with a change they
are making. Alot of this is common sense that you probably already know
as a Buckminster committer, but thought it worth mentioning.
p2-dev mailing list
R. Ian Bull | EclipseSource Victoria | +1 250 477 7484
http://eclipsesource.com | http://twitter.com/eclipsesource