[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [eclipse.org-planning-council] Notes from today's meeting ... and a request to those not there ...
|
The EDP allows for "rollup" reviews. Webtools, for example, does a
single release review for all of its subprojects. BIRT does the same.
So, IMHO, there's no need to change the development process.
I think that this speaks more to the conventions on the Participation
page. What does it mean for projects to group themselves in a row
anyway? I think that one implication can be that they do a single
release review for all contained projects. For project that it doesn't
make sense to group together, they can pull out to the "top level".
More pragmatically, it'll allow me to have a better sense of how much
release review work the EMO is going to have to do.
Wayne
David M Williams wrote:
No, I do not think a change is _required_ in our PC documents ... but
if this "rule" deviates from the Eclipse Development Process, then it
should be documented somewhere. I'd recommend the dev. proc. document
be changed, if there's a fundamental change in rules. The Simultaneous
Release rules are more of _extra_ requirements that are agreed to, not
different from the normal release process.
But, what is the "rule" that you are going by? I doubt we want it to
literally be "rows in table". I'm not sure what all those rows
represent, but perhaps the rule should be "release reviews are done at
either a top level project level or a first level sub-project level.
Sub-sub-projects need to be aggregated to their first level
sub-project. This includes Docuware and IP Logs for anything releasing
at the same time. If appropriate, sub-sub-projects can still release
on their own, if they are the only thing releasing at that time". Or
something similar to that. I suspect there's a spot or two in the Dev.
Guide that could be changed, which would be best if you'd want this to
be a consistent rule for all reviews ... not only the yearly ones ...
which seems reasonable to me (though, I realize the other periods of
time are not as "crunched", there'd still be a lot of minutia even if,
say, 3 or 4 sub-sub-projects were releasing.
I suspect this would be easier for most sub-sub-projects ... a little
coordination to make sure someone was pulling it all together, but
less documentation to produce.
HTH
From: Wayne Beaton <wayne@xxxxxxxxxxx>
To: "eclipse.org-planning-council"
<eclipse.org-planning-council@xxxxxxxxxxx>
Date: 12/02/2009 05:34 PM
Subject: Re: [eclipse.org-planning-council] Notes from today's
meeting ... and a request to those not there ...
Sent by: eclipse.org-planning-council-bounces@xxxxxxxxxxx
------------------------------------------------------------------------
+1 on all documents.
I'd like to restrict the total number of reviews that we have to do. In
that light, I'm going to push for one release review for each row in the
table on the Participating Projects page.
I don't think that this requires any changes in the documents.
Does this sound reasonable?
My apologies for missing the call.
Wayne
David M Williams wrote:
>
> I've updated our notes from todays call:
>
> http://wiki.eclipse.org/Planning_Council/December_02_2009
>
> Let us know if inaccuracies or omissions.
>
> For those of you had to drop off early (Oisin, Cedric) or did not
> attend the call (Wayne, John, Chris, Anthony, and Christian), I would
> appreciate you documenting here to the mailing list your approval (or
> not) of our plan and requirements documents. While we had a unanimous
> agreement of those present, and that would be a majority (10 of 16) it
> is good form to document more agreement than a simple majority. Plus,
> it is my way of not letting you off the hook for not attending the
> meeting. :)
>
> I have update the main planning document in some minor ways as
discussed,
> http://wiki.eclipse.org/Helios_Simultaneous_Release
>
> most notably pulling the participating projects table into its own page
> http://wiki.eclipse.org/Helios/Participating_Projects
>
> and did some simple edits to requirements document
> http://www.eclipse.org/helios/planning/EclipseSimultaneousRelease.php
>
> I'll announce these documents to Cross Project list on Thursday.
>
> Thanks very much for your help with the Simultaneous Release!
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> eclipse.org-planning-council mailing list
> eclipse.org-planning-council@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/eclipse.org-planning-council
>
> 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.
_______________________________________________
eclipse.org-planning-council mailing list
eclipse.org-planning-council@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/eclipse.org-planning-council
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.
------------------------------------------------------------------------
_______________________________________________
eclipse.org-planning-council mailing list
eclipse.org-planning-council@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/eclipse.org-planning-council
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.
