Dear wiki user, You have subscribed to a wiki page "Couchdb Wiki" for change notification.
The page "Release_Preparation" has been deleted by JoanTouzet: https://wiki.apache.org/couchdb/Release_Preparation?action=diff&rev1=6&rev2=7 Comment: whole process has changed and is documented formally now - <<Include(EditTheWiki)>> - = Release Preparation = - - <<TableOfContents(2)>> - - ''This is a work in progress. Please contribute to it and make it better.'' - - == Early in the cycle: early landings == - - * See if we have bundled dependencies that need updating - * ibrowse - * mochiweb - * jQuery - * snappy - * erlang-oauth - - == ~1 week before release: ascertain good shape == - - * Triage open issues for upcoming release - * Bug responsible devs for acting on them - * [[https://issues.apache.org/jira/issues/?jql=project%20%3D%20COUCHDB%20AND%20fixVersion%20%3D%20%221.4%22%20AND%20resolution%20%3D%20Unresolved%20ORDER%20BY%20due%20ASC%2C%20priority%20DESC%2C%20created%20ASC|Open issues with fix version 1.4]] - * Triage open pull requests for upcoming release - * https://github.com/apache/couchdb/pulls - * Triage issues with patches attached - * [[https://issues.apache.org/jira/issues/?jql=project%20%3D%20COUCHDB%20AND%20labels%20%3D%20patch%20AND%20status%20in%20%28Open%2C%20%22In%20Progress%22%2C%20Reopened%29|Open issues with label "patch"]] - * Track deprecations and experimental features from previous release - * Make sure [[CI]] is working, in a good state - - == ~2 days before release: prepare change log == - - * Go through code on the master and check for any changes since last release - * ''@@ Can someone provide a Git command that will do this?'' - * Check changelog.rst and make sure they are up-to-date with respect to new changes - * Go through code on the last release branch and check for any changes since last release - * (Is this needed? Why would we ever merge directly to the release branch outside of doing a release?) - * ''@@ Can someone provide a Git command that will do this?'' - * Check changelog.rst and make sure they are up-to-date with respect to new changes - - == Merging Fixes Into Master == - - This is also the time to consider whether you have any fixes that could land in master. If you've been working on a branch, please review your changes, and merge in anything that seems appropriate. - - You can review your changes against master by running: - - git log --abbrev-commit --pretty=oneline FROM..TO - - ''@@ Is this correct?'' - - If you can think of any other command that would help, or any tooling we might want to make, please update this page. I'd like this page to make things as easy as possible for people to just run a few commands and get the right stuff merged into the right places. -
