From ca0c1e69cab67276b2f701f7c3ea43658a52fd83 Mon Sep 17 00:00:00 2001 From: Dylan Baker Date: Thu, 24 Oct 2019 13:21:45 -0700 Subject: [PATCH] docs: update releasing process to use new scripts and gitlab There were several out of date entries in this document, update them to current practices. Reviewed-by: Juan A. Suarez --- docs/releasing.html | 49 +++++++++++---------------------------------- 1 file changed, 12 insertions(+), 37 deletions(-) diff --git a/docs/releasing.html b/docs/releasing.html index d2dc72ff7a4..7c4e213fb92 100644 --- a/docs/releasing.html +++ b/docs/releasing.html @@ -26,8 +26,7 @@
  • Pre-release announcement
  • Making a new release
  • Announce the release -
  • Update the mesa3d.org website -
  • Update Bugzilla +
  • Update Gitlab Issues @@ -517,35 +516,21 @@ So we do a quick 'touch test' unset VK_ICD_FILENAMES -

    Update version in file VERSION

    - -

    -Increment the version contained in the file VERSION at Mesa's top-level, then -commit this change. -

    -

    Create release notes for the new release

    -Create a new file docs/relnotes/X.Y.Z.html, (follow the style of the previous -release notes). Note that the sha256sums section of the release notes should -be empty (TBD) at this point. -

    +The release notes are completely generated by the +
    bin/gen_release_notes.py
    script. Simply run this script before +bumping the version -

    -Two scripts are available to help generate portions of the release notes: +The only thing left to do is add the sha256 sums.

    -
    -	./bin/bugzilla_mesa.sh
-	./bin/shortlog_mesa.sh
-
    +

    Update version in file VERSION

    -The first script identifies commits that reference bugzilla bugs and obtains -the descriptions of those bugs from bugzilla. The second script generates a -log of all commits. In both cases, HTML-formatted lists are printed to stdout -to be included in the release notes. +Increment the version contained in the file VERSION at Mesa's top-level, then +commit this change.

    @@ -591,11 +576,9 @@ Something like the following steps will do the trick: git cherry-pick -x X.Y -

    -Also, edit docs/relnotes.html to add a link to the new release notes, -edit docs/index.html to add a news entry and a note in case of the -last release in a series, and remove the version from -docs/release-calendar.html. Then commit and push: +

    Then run the 

    ./bin/post_verison.py X.Y.Z
    , where X.Y.Z is the +version you just made. This will updated docs/relnotes.html and +docs/index.html. Remove docs/release-calendar.html. Then commit and push: 

    @@ -616,15 +599,7 @@ series, if that is the case.
 
    
 
 
-
    Update the mesa3d.org website
    
-
-
    
-As the hosting was moved to freedesktop, git hooks are deployed to update the
-website. Manually check that it is updated 5-10 minutes after the final git push
-
    
-
-
-
    Update Bugzilla
    
+
    Update gitlab issues
    
 
 
    
 Parse through the bugreports as listed in the docs/relnotes/X.Y.Z.html
-- 
2.30.2