Task #10788 (new)
Opened 11 years ago
Last modified 11 years ago
4.4.8 release setup — at Version 1
| Reported by: | jamoore | Owned by: | sbesson |
|---|---|---|---|
| Priority: | blocker | Milestone: | OMERO-4.4.x |
| Component: | General | Version: | n.a. |
| Keywords: | n.a. | Cc: | rleigh, khgillen, mlinkert, pwalczysko, sbesson |
| Resources: | n.a. | Referenced By: | n.a. |
| References: | n.a. | Remaining Time: | n.a. |
| Sprint: | n.a. |
Description (last modified by jamoore)
General TODOs
- Add a sync job which pushes tags from gh:ome/* to gh:snoopy/*
- Setup proper directory permissions for the hudson user
Ideal job
The ideal job for performing a release would be runnable via: %build OME-release now version=4.4.8. It would perform the following steps:
- Checkout the latest ome/ome code
- Update all submodule pointers similar to OMERO-submods-{stable,develop}
- Push that branch to snoopy
- Open a PR (Note: when this commit is pushed back to ome/ome, the PR will be autoclosed)
- Kick off the ice33 and ice34 builds.
- ...
- Once all other activities are finished, there are 2 options:
- Either delete the job executions, in which case there's no evidence of the tag that snoopy created; or
- Sign the snoopy commit and push it to ome/ome and promote the builds. The release was a success!
Larger tasks (ticketable)
- Remove need for version PRs in bioformats
- Move release notes into source (See https://github.com/PyTables/PyTables/pull/240/files. From Roger: "Being able to update the release notes with the PR to implement a feature/fix a bug would be very nice, then it's always in a "ready to release" state ahead of the release. ")
Change History (1)
comment:1 Changed 11 years ago by jamoore
- Cc rleigh khgillen mlinkert added
- Description modified (diff)
Note: See
TracTickets for help on using
tickets.
You may also have a look at Agilo extensions to the ticket.
