Hi Tim.
The plan is one bookend of the release cycle [1]. The plan (at least
a rudimentary "this is sort of what we're thinking that we'd like to
do with the release" plan should be in place at the beginning of
release development. The plan can evolve over time. It is a means by
which the community can prepare for and participate in the release;
it's a basis upon which adopters can form their own release plans.
At the end of the release cycle, you need to complete the review
information. This is generally a retrospective "this is what we did"
sort of thing with some focus on ensuring that necessary quality
exists in the code and that all aspects of open source development
have been observed (i.e. the open source rules of engagement).
The review also serves as a checkpoint for the IP process.
So... please do the following:
1) Change the date. It should be in the future. I'll be running a
review that concludes on March 5, and then on March 19. You can pick
these dates, or some date that follows one of them (the review date
can be a few days ahead of the actual release date).
2) Provide review information on the "Review Information" page
3) Submit the project's IP Log for review [2].
4) Get approval on the completed review information from the PMC.
Once this is in place, I can schedule the review.
Note that I just noticed that the IP Log generator isn't functioning
for the GitHub-based Vert.x project. I have a fix that I'll deploy
shortly. I'll let you know.
HTH,
Wayne
[1]
https://wiki.eclipse.org/Development_Resources/HOWTO/Release_Cycle
[2] http://www.eclipse.org/projects/ip_log.php?id=rt.vertx
On 02/17/2014 03:25 AM, Tim Fox wrote:
Hell All,
I am new to this game, but would like to release Vert.x 2.1.0
soon. I have created a release plan here:
https://projects.eclipse.org/projects/rt.vertx/releases/2.1.0/plan
Thanks
_______________________________________________
rt-pmc mailing list
rt-pmc@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/rt-pmc
|