Task #11354 (closed)
Opened 11 years ago
Closed 10 years ago
Review all aspects of mock release
| Reported by: | jamoore | Owned by: | sbesson |
|---|---|---|---|
| Priority: | blocker | Milestone: | 5.0.0-rc1 |
| Component: | Deployment | Version: | 4.4.8 |
| Keywords: | n.a. | Cc: | omero-team@… |
| Resources: | n.a. | Referenced By: | n.a. |
| References: | n.a. | Remaining Time: | n.a. |
| Sprint: | n.a. |
Description
At least one mock release should be prepared of 4.4.9 which should have all of the following aspects reviewed:
- the downloads page including all URLs, the wording, and "what's new" like text, etc.
- location and wording of the announcment
- the location and the state of all the artifacts, including any new artifacts or projects that should be included (C++, etc.)
- synchronization of docs and tutorials.
With that in place, there should be no need for major discussions of particulars (say of the download page) when it comes time for the final release (i.e. GA).
Note: this is initially assigned to Sebastien who is putting the mock releases into place, but will require a general team effort and everyone signing off on the state of the mock releases.
Change History (1)
comment:1 Changed 10 years ago by jamoore
- Milestone changed from OMERO-4.4.x to 5.0.0-beta2
- Resolution set to fixed
- Status changed from new to closed
Note: See
TracTickets for help on using
tickets.
You may also have a look at Agilo extensions to the ticket.
Taken care of as part of #11523 (OMERO5 beta releases)