Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "Jetty/Contributor/Eclipse Release"
< Jetty | Contributor
(→Eclipse Release Checklist) |
(→Eclipse Release Checklist) |
||
| Line 1: | Line 1: | ||
{{Jetty Contributor}} | {{Jetty Contributor}} | ||
== Eclipse Release Checklist == | == Eclipse Release Checklist == | ||
| + | |||
| + | If its a bugfix release then you are fine to release. | ||
| + | |||
| + | If its a minor version bump then you must follow the process below. | ||
* At least 3 weeks ahead of time, make sure we have a frozen IP Log in place, otherwise submit one to Eclipse Legal for review | * At least 3 weeks ahead of time, make sure we have a frozen IP Log in place, otherwise submit one to Eclipse Legal for review | ||
** http://www.eclipse.org/projects/ip_log.php?projectid=rt.jetty | ** http://www.eclipse.org/projects/ip_log.php?projectid=rt.jetty | ||
| + | ** at bottom the this url click the 'Submit IPLog' button, it gets mailed to Wayne who goes through it with a fine toothed comb | ||
** this step may be skipped if reusing an existing IPLog, which is commonly the case for our minor releases and speeds the process greatly | ** this step may be skipped if reusing an existing IPLog, which is commonly the case for our minor releases and speeds the process greatly | ||
| Line 11: | Line 16: | ||
** template in svn @ admin/template/JettyReleaseReviewTemplate.odp | ** template in svn @ admin/template/JettyReleaseReviewTemplate.odp | ||
** alternately grab the last release review and update it into a new name, the edit the slides accordingly | ** alternately grab the last release review and update it into a new name, the edit the slides accordingly | ||
| − | ** copy into new release directory and | + | ** copy into new release directory and commit accordingly |
| + | ** release review document should have hard link to the IPLog being used for the release, this document can not be submitted until finalize IPLog is in place | ||
* Email Release Docuware to emo@eclipse.org requesting a release review | * Email Release Docuware to emo@eclipse.org requesting a release review | ||
** explain briefly what has changed and why this can't be a bugfix release, updates to protocol like websocket, etc | ** explain briefly what has changed and why this can't be a bugfix release, updates to protocol like websocket, etc | ||
** release reviews are generally on a Wednesday and out about 2 weeks from when you ask for them, ask for as soon of a date as possible | ** release reviews are generally on a Wednesday and out about 2 weeks from when you ask for them, ask for as soon of a date as possible | ||
| + | ** prepare to hear back that there are no RC# releases for the release review being scheduled and then respond that we don't typically require a full on RC# release in our process. | ||
| + | ** wait until required time has passed and release review was successful | ||
| + | ** release! | ||
Revision as of 18:23, 30 March 2011
Eclipse Release Checklist
If its a bugfix release then you are fine to release.
If its a minor version bump then you must follow the process below.
- At least 3 weeks ahead of time, make sure we have a frozen IP Log in place, otherwise submit one to Eclipse Legal for review
- http://www.eclipse.org/projects/ip_log.php?projectid=rt.jetty
- at bottom the this url click the 'Submit IPLog' button, it gets mailed to Wayne who goes through it with a fine toothed comb
- this step may be skipped if reusing an existing IPLog, which is commonly the case for our minor releases and speeds the process greatly
- Create release directory under admin in svn: svn+ssh://dev.eclipse.org/svnroot/rt/org.eclipse.jetty/admin/<release version>
- Create Release Review Document
- template in svn @ admin/template/JettyReleaseReviewTemplate.odp
- alternately grab the last release review and update it into a new name, the edit the slides accordingly
- copy into new release directory and commit accordingly
- release review document should have hard link to the IPLog being used for the release, this document can not be submitted until finalize IPLog is in place
- Email Release Docuware to emo@eclipse.org requesting a release review
- explain briefly what has changed and why this can't be a bugfix release, updates to protocol like websocket, etc
- release reviews are generally on a Wednesday and out about 2 weeks from when you ask for them, ask for as soon of a date as possible
- prepare to hear back that there are no RC# releases for the release review being scheduled and then respond that we don't typically require a full on RC# release in our process.
- wait until required time has passed and release review was successful
- release!