id,summary,reporter,owner,description,type,status,priority,milestone,component,version,resolution,keywords,cc,drp_resources,i_links,o_links,remaining_time,sprint 10788,4.4.9 release setup,jamoore,jamoore,"== General TODOs == * Add a sync job which pushes tags from gh:ome/* to gh:snoopy/* (UNNEEDED) * Setup proper directory permissions for the hudson user (#11523) ---- == 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 (Don) * Update all submodule pointers similar to OMERO-submods-{stable,develop} (Done) * Push that branch to snoopy (Done: pushes a tag) * Open a PR (Note: when this commit is pushed back to ome/ome, the PR will be autoclosed) (Not needed) * Kick off the ice33 and ice34 builds. (Done; as matrix job) * ... * 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 (Mostly done; not maven - see #11523) * 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. "" (#11523)",task,closed,blocker,OMERO-4.4.9,General,4.4.8,fixed,,rleigh khgillen mlinkert pwalczysko sbesson,,,,,