| [tools-pmc] RE: [mylyn-dev] Re: Mylyn 2.1 did not have a Release Review |
|
Thanks Bjorn. We’re scheduling the 2.1 review, and
will schedule the other 2.x reviews as they come up. I wish that we could
minimize our overhead by sticking to Platform’s patter of unreviewed milestones,
service builds and single annual release and review. But I figure
that you’re right about the overhead being low enough not to adjust our
release plans. Mik From: mylyn-dev-bounces@xxxxxxxxxxx
[mailto:mylyn-dev-bounces@xxxxxxxxxxx] On Behalf Of Bjorn Freeman-Benson Mik, The
problem here is my assumption that our 2.x releases would be covered by the
Europa release review as are Platform’s 3.3.x releases, and that we would
not require another release review until Mylyn 3.0. It sounds like this
reasoning was flawed due to the fact that Mylyn’s UI evolves in the 2.x
releases, and that we need to have a release review for each of those? Correct. The Platform 3.3.x are bugfixes and thus do not
need reviews. Mylyn's 2.x are considered "major releases" and thus
require reviews. After
that I’d like to figure out how exactly we fit into the current policy
because having 4 release reviews a year will cause additional administrative
overhead on the project that we didn’t factor in, Hopefully a very low additional overhead? I think the two
biggest issues will be: (i) remembering to schedule the reviews and (ii)
updating the slides from your previous review to cover anything new (new
committers, new IP, etc). -- [end of message] |