From:
tools-pmc-bounces@xxxxxxxxxxx [mailto:tools-pmc-bounces@xxxxxxxxxxx] On Behalf Of Mike Milinkovich
Sent: Thursday, November 16, 2006
9:19 AM
To: 'Tools
PMC mailing list'
Cc: 'Yossi Leon'
Subject: [tools-pmc] FW:
[eclipse.org-planning-council] Questions About Release Review
Tools PMC,
Although Yossi had his questions answered,
it seems that these questions should really be ones that the Tools PMC should
be helping him with as part of the PHP IDE's incubation process.
Mike Milinkovich
Executive Director,
Eclipse Foundation, Inc.
Office: 613-224-9461 x228
Cell: 613-220-3223
mike.milinkovich@xxxxxxxxxxx
blog: http://milinkovich.blogspot.com/
From:
eclipse.org-planning-council-bounces@xxxxxxxxxxx
[mailto:eclipse.org-planning-council-bounces@xxxxxxxxxxx] On Behalf Of Oberhuber, Martin
Sent: November 16, 2006 7:07 AM
To: eclipse.org-planning-council
Subject: RE:
[eclipse.org-planning-council] Questions About Release Review
Hi Yossi,
1.
from www.eclipse.org,
tab "Projects", Useful Links: Howto Release Review
http://www.eclipse.org/projects/dev_process/release-review.php
Search for "Project Log" and
follow the Link
http://www.eclipse.org/projects/dev_process/project-log.php
from www.eclipse.org,
tab "Projects", Useful Links: Project Status Infrastructure
http://www.eclipse.org/projects/dev_process/project-status-infrastructure.php
3.
If you want a slide deck template, the
ones available officially are only available as PDF.
Ours is available as PPT as well, from http://www.eclipse.org/dsdp/tm/ by
following
"Events: Release Review: PPT"
http://www.eclipse.org/dsdp/tm/doc/TM_1.0_Release_Review_v3.ppt
4.
For the bugzilla statistics, see the links
"For Release Review" on our bug process page
http://www.eclipse.org/dsdp/tm/development/bug_process.php
I simply copied & pasted this into
Excel, it came out quite nicely; adding a few formulas
around it formatted it in a form suitable
for the slide deck, see attached xls
Cheers,
--
Martin Oberhuber
Wind River Systems, Inc.
Target Management Project Lead, DSDP PMC Member
http://www.eclipse.org/dsdp/tm
From:
eclipse.org-planning-council-bounces@xxxxxxxxxxx
[mailto:eclipse.org-planning-council-bounces@xxxxxxxxxxx] On Behalf Of Yossi Leon
Sent: Thursday, November 16, 2006
8:47 AM
To: eclipse.org-planning-council
Subject: RE:
[eclipse.org-planning-council] Questions About Release Review
1. How do i get/create the IP log?
2. What do you mean by "Project metadata"?
--
Yossi Leon, Product Manager, Development Tools & PHP IDE
Project Leader
yossi@xxxxxxxx http://www.zend.com/
+972-3-6139665 ext.229
From:
eclipse.org-planning-council-bounces@xxxxxxxxxxx
[mailto:eclipse.org-planning-council-bounces@xxxxxxxxxxx] On Behalf Of Tim Wagner
Sent: Thursday, October 26, 2006
6:37 PM
To: eclipse.org-planning-council
Subject: RE:
[eclipse.org-planning-council] Questions About Release Review
-->
Release reviews need to be scheduled (posted) for the public at
least 1 week prior to the event, and the materials should be readied in advance
of the scheduling, since they are part of the posting along with the
date/time/callin number that goes out to the community.
Some other random bits of advice from my own experiences:
- Have
an email statement from Janet Campbell stating that your IP log has been
reviewed and blessed for release *in
writing* available to show at the release review. Oral
confirmation is not sufficient.
- In
general, the release “deck” should point back (via URLs) to
most of the persistent information – your IP log, your project plan,
Bugzilla, etc. in addition to summarizing them. This helps to show that
you are being transparent and communicative outside the review per se.
- Project
metadata should be up to date and your website should reflect the release
schedule, etc. contained in the metadata.
- Remember
that you need PDF as well as PPT format for the posting.
- I
would separate the release review into a small number (1-2) of
“important” slides and then a larger number of
“backup” slides – no one may ask you to go through
history, feature lists, etc. (though you should have them ready) but you
will certainly need to address issues like IP cleanliness as part of the
public forum.
- I’d
suggest you invite some known adopters or users to attend as advocates and
as a demonstration of your community building and outreach.
From: eclipse.org-planning-council-bounces@xxxxxxxxxxx
[mailto:eclipse.org-planning-council-bounces@xxxxxxxxxxx] On Behalf Of David M Williams
Sent:
Thursday, October 26, 2006 10:08 AM
To:
eclipse.org-planning-council
Subject:
Re: [eclipse.org-planning-council] Questions About Release Review
> 1. Release version: although i have milestones for
0.7, does it make sense (according to Eclipse way) to consider 1.0 version
instead of 0.7?
No,
I'd stick with 0.7. Its always easier to go "up" later, rather to go
end up having to go "down" ... if, for example, in the off-chance you
decided at some point to release a 0.9 version instead of a 1.0 version.
And,
I'm just stating a general rule ... nothing specific to your project. We in WTP
sort of did this wrong once in our distant past (and we still hear about it :)
|
Bjorn Freeman-Benson <emo@xxxxxxxxxxx>
Sent
by: eclipse.org-planning-council-bounces@xxxxxxxxxxx
10/26/2006
10:38 AM
|
Please respond to
"eclipse.org-planning-council"
<eclipse.org-planning-council@xxxxxxxxxxx>
|
|
|
To
|
yossi@xxxxxxxx
|
|
cc
|
tools-pmc@xxxxxxxxxxx, "eclipse.org-planning-council"
<eclipse.org-planning-council@xxxxxxxxxxx>
|
|
Subject
|
Re: [eclipse.org-planning-council] Questions About Release Review
|
|
Yossi,
Your PMC (John and Doug) should help you prepare for a release review - it is a
non-trivial undertaking and I suggest you start planning as soon as you can.
As John noted, the instructions about Release Reviews are here:
http://www.eclipse.org/projects/dev_process/release-review.php
Yossi Leon
wrote:
Hi All,
I'm
taking Tim's advise and i'm posting my questions to the planning council:
As
project leader i want to release the PHP IDE till the end of the year (Dec
21st). The current state is that we're about to release 0.7 Milestone 3.
1.
Release version: although i have milestones for 0.7, does it make sense
(according to Eclipse way) to consider 1.0 version instead of 0.7?
2.
Schedule: How much time before the actual release i need to schedule the
release review?
3. Any
other suggestions i should consider before the release review?
--
_______________________________________________
eclipse.org-planning-council mailing list
eclipse.org-planning-council@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/eclipse.org-planning-council
