Re: [eclipse.org-planning-council] TODOs from today's meeting for compli

[David M Williams <david_williams@xxxxxxxxxx>]

I did not mean to ask anyone
to re-do archival materials any differently than they've already done.
But am hoping the checklists at the portal can be finished soon. 

I was expressing frustration
that the checklists were not already done, but I obviously did a  poor
job of educating everyone and monitoring the process incrementally.  

Re-reading it now, in our "must
do" document at http://eclipse.org/helios/planning/EclipseSimultaneousRelease.php,
in the Release Review section, 
I am not sure if this requirement
was interpreted in a different way than I did, or just not read at all.


"In addition to the
ordinarily required Release Review Archival Materials, all Projects participating
in yearly Release agree to provide a checklist-with-detail form that describes
their compliance (or not) with all of the criteria items described in this
document."

So as it is, I'll console myself
that those projects that did provided it with their archival materials
... maybe only webtools ... will stand out as shining examples of well
organized, well documented projects :)   [But, I admit, webtools has
an edge :) ]

Despite all my grousing, I think
this Simultaneous Release is a very good one and I think next cycle we
can do even better! 

Thank you to everyone for your
help,

From:	John Arthorne <John_Arthorne@xxxxxxxxxx>
To:	"eclipse.org-planning-council" <eclipse.org-planning-council@xxxxxxxxxxx>
Date:	06/03/2010 11:38 AM
Subject:	Re: [eclipse.org-planning-council] TODOs from today's meeting for        compliance checklists
Sent by:	eclipse.org-planning-council-bounces@xxxxxxxxxxx

---

I didn't know about this either. Also, it sounds odd to require this because
the release review and related material is a standard Eclipse Foundation
process that is unrelated to whether a project is on the train or not.
Not suprisingly, the page that outlines the required elements of the release
review documentation doesn't mention this [1]. 

John 

[1] http://wiki.eclipse.org/Development_Resources/HOWTO/Release_Reviews

Thomas Watson <tjwatson@xxxxxxxxxx>
Sent by: eclipse.org-planning-council-bounces@xxxxxxxxxxx

06/03/2010 11:27 AM

Please respond to
"eclipse.org-planning-council"        <eclipse.org-planning-council@xxxxxxxxxxx>

To	"eclipse.org-planning-council" <eclipse.org-planning-council@xxxxxxxxxxx>
cc
Subject	Re: [eclipse.org-planning-council] TODOs from today's meeting for        compliance checklists

I admit that I did not know (or at least remember) that the check list
was supposed to be included in the release materials. The Eclipse and Equinox
projects slideware does not include this information. I hope we can make
an exception this release and let this slide. Sorry if this was discussed
and documented somewhere. If so, I apologize for overlooking this requirement.

Tom

David
M Williams---06/03/2010 02:56:39 AM---This a reminder of issues/oddities
with the "compliance checklists" that need some attention from
some of you:

From:	David M Williams/Raleigh/IBM@IBMUS
To:	"eclipse.org-planning-council" <eclipse.org-planning-council@xxxxxxxxxxx>
Date:	06/03/2010 02:56 AM
Subject:	[eclipse.org-planning-council] TODOs from today's meeting for compliance checklists

---

This a reminder of issues/oddities with the "compliance checklists"
that need some attention from some of you: 
You can start and drill down, if you need to, from here

http://eclipse.org/helios/planning/SimultaneousReleaseGrid.php

Oisin: stp 
only one has data: stp sca 
one 'stp' is probably a "container project" and just needs to
have its Simultaneous Release flag unset? 
stp bpmnmodeler? Are they no longer releasing? releasing, but not in common
repo? Please make sure the form is filled out by release review, if they
plan on releasing. 

Gary: Birt (and a few others) 
please fill in the planning and ip doc urls (at least). 

Wayne/Chris ejit/jget ... looks like it already received a little TLC already?
Thanks! 

Modeling ... where to start :) ... 5 subprojects appear to not be participating
... from a casual glance. 

Anthony mentioned a few of the gmf ones that were containers, or "dropped
out" with their restructuring. Anthony, can you try unchecking the
sim. rel. flag ... or fill in valid data if this are really supposed to
have it. 

Ed, Is there 4 you need to handle? Can you get some help? 
>From a previous note to day, I suspect you've never used this new system
of forms and discovered how easy the Eclipse Foundation has made it. 5-10
minutes would get you 80% done, I suspect. They've done a good job of providing
these tools. 

All: a checklist was supposed to be included with your release materials.
Did you? Did anyone besides webtools? I know this system got on-line a
little late, and I didn't have time to keep a watch on all of you ... but,
I shouldn't have to. 

Long run, I think we'll enjoy these tools more when we can use them over
whole cycle (to better monitor progress) and also if/when some can be better
automated or ... best of all ... tie some to automatic tests! But ... that's
all future. 

I'd appreciate some "clean up" now as we end this release so
we at least we look like a group of professionals working together ...
instead of some haphazard collections of uncoordinated pieces of things.

Sincerest thanks. 






_______________________________________________
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.