Comment 1 Jacques Bouthillier 2013-06-27 08:56:59 EDT

IP Log submitted

Comment 2 Jacques Bouthillier 2013-06-27 11:36:14 EDT

Project plan Updated
http://www.eclipse.org/projects/project-plan.php?planurl=/r4e/plans/plan.xml

Comment 3 Jacques Bouthillier 2013-07-04 14:30:07 EDT

Created attachment 233093 [details]
Release Documentation

Comment 4 Jacques Bouthillier 2013-07-04 14:48:29 EDT

IP Log approval received +1
Please review release documentation

Comment 5 Wayne Beaton 2013-07-11 14:47:47 EDT

Do you have a target date in mind?

AFAICT, the project does not have a "dummy" inbox set up for Bugzilla. Consider requesting one.

http://wiki.eclipse.org/Webmaster_FAQ#Dummy_Inboxes

Comment 6 Jacques Bouthillier 2013-07-19 08:31:04 EDT

IP log approval is on Bug 412788

Comment 7 Jacques Bouthillier 2013-07-19 09:08:20 EDT

The release document was available on this bug, 
how should I proceed to get the review approval for the R4E release 0.20?

In fact, this release is only a bug fix release
When can we proceed with the R4E release, lest us know . earliest time is better

Referencing comment #5, we have r4e-inbox@eclipse.org, dio we need something else ?

Comment 8 Wayne Beaton 2013-07-19 09:15:02 EDT

(In reply to comment #7)
> The release document was available on this bug, 
> how should I proceed to get the review approval for the R4E release 0.20?

AFAICT, R4E has done several releases already, so I'm surprised that you don't know what you need to do here. 

You need to get PMC approval, and then forward your approved review materials to the EMO with a request to schedule the actual public review.

> In fact, this release is only a bug fix release
> When can we proceed with the R4E release, lest us know . earliest time is
> better

Page 4 of the review documenation and your comments on the mailing list indicated that there is new functionality. You do not include new functionality in a bug fix release. Also, bug fix releases should increment the third segment of the version number, not the second.

If this is really a service release, then you don't need a review.

> Referencing comment #5, we have r4e-inbox@eclipse.org, dio we need something
> else ?

No. I'm not sure what I saw to prompt my comment.

Comment 9 Jacques Bouthillier 2013-07-22 08:08:29 EDT

Created attachment 233665 [details]
R4E schedule Review

E-mail sent to EMO  to schedule a review for R4E 0.20

Comment 10 Jacques Bouthillier 2013-07-22 13:29:49 EDT

Created attachment 233679 [details]
R4E-0.20 release new date

Modify the release date to be July 26, 2013 on slide 1 and 12

Comment 11 Wayne Beaton 2013-07-22 14:27:09 EDT

(In reply to comment #10)
> Created attachment 233679 [details]
> R4E-0.20 release new date
> 
> Modify the release date to be July 26, 2013 on slide 1 and 12

The best we can do is a review ending on July 31. The release will have to come on that date or later.

Comment 12 Jacques Bouthillier 2013-07-23 08:34:05 EDT

Created attachment 233704 [details]
R4E-0.20-Release July31

Updated document for the release review for July 31

Comment 13 Jacques Bouthillier 2013-08-20 07:30:09 EDT

Review completed,
Update site available with the latest R4E 0.20 on http://download.eclipse.org/r4e/updates/