You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@couchdb.apache.org by GitBox <gi...@apache.org> on 2018/07/24 05:37:32 UTC

[GitHub] wohali edited a comment on issue #1453: Cut 2.2.0 release

wohali edited a comment on issue #1453: Cut 2.2.0 release
URL: https://github.com/apache/couchdb/issues/1453#issuecomment-407286867
 
 
   @janl you asked about my process for creating release notes - I wrote it up - maybe this will help you:
   
   -----------
   
   Get a list of things to care about:
   `git show-branch --sha1-name master X.X.X|more`
   * use this to find common ancestor (very last thing in the output)
   * use this to make sure everything on X.X.X has been pulled fwd to master
   * use this to eliminate anything that "looks the same" on X.X.X branch and master
       * cannot use sha-1s because they will be different on each branch
       * research if there is a way to auto-eliminate cherry picked stuff?
   
   For each remaining commit on master:
   1. use GH web UI to find the commit's related PRs or issues and write up
      something nice
   1. sort by GH issue/PR number
   1. any issues that merge without a useful GH/PR number should go either at the
      very top or bottom of the list, depending on importance of issue
   1. do not explicitly list out things like Jenkins/Travis/rebar.config changes
      unless they are significant in some fashion
   
   Now do the same thing as above, but for documentation and fauxton. Pull out only
   the big-ticket items.

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services