From: Matthew Fernandez <matthew.fernandez@gmail.com>
Date: Wed, 3 Feb 2021 01:48:11 +0000 (-0800)
Subject: add details of updating the website to the release procedure
X-Git-Tag: 2.47.0~92^2
X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=5e93d372cfb4f83c46194455a0dff33051636729;p=graphviz

add details of updating the website to the release procedure

This is addressing the following point I made in the 2.46.0 retrospective:

  We probably need to incorporate www2.graphviz.org and graphviz.gitlab.io
  actions into the release steps in DEVELOPERS.md.

It would be nice to further automate some of this in future.
---

diff --git a/DEVELOPERS.md b/DEVELOPERS.md
index fee6e5c99..694cf8f3e 100644
--- a/DEVELOPERS.md
+++ b/DEVELOPERS.md
@@ -54,6 +54,8 @@ See [`gen_version.py`](https://gitlab.com/graphviz/graphviz/-/blob/master/gen_ve
 
 ### Instructions
 
+#### Creating the release
+
 1. Check that the
 [master pipeline](https://gitlab.com/graphviz/graphviz/-/pipelines?ref=master)
 is green
@@ -118,6 +120,8 @@ is green
    The “deployment” CI task will also create a Git tag for the version, e.g.
    `2.44.1`.
 
+#### Returning to the development series
+
 1. Create a new local branch and name it e.g. `return-to-<version>-dev`
 
    Example: `return-to-2.45-dev`
@@ -146,6 +150,29 @@ is green
 
 1. Merge the merge request
 
+#### Updating the website
+
+1. Fork the
+   [Graphviz website repository](https://gitlab.com/graphviz/graphviz.gitlab.io)
+   if you do not already have a fork of it
+
+1. Checkout the latest master branch
+
+1. Create a local branch
+
+1. Update the download pages, download.md and download/source/index.md, with
+   details of the new release
+
+1. Commit this to your local branch
+
+1. Push this to a branch in your fork
+
+1. Create a merge request
+
+1. Wait for CI to pass
+
+1. Merge the merge request
+
 ## Building
 
 Instructions for building Graphviz from source are available