[GRASS-git] [OSGeo/grass] 6af6fa: contributing: Make release procedure cleaner and m...

Vaclav Petras noreply at github.com
Tue May 31 10:01:56 PDT 2022


  Branch: refs/heads/releasebranch_8_2
  Home:   https://github.com/OSGeo/grass
  Commit: 6af6fa375094f59feadb0059dfaa6b2553a916d2
      https://github.com/OSGeo/grass/commit/6af6fa375094f59feadb0059dfaa6b2553a916d2
  Author: Vaclav Petras <wenzeslaus at gmail.com>
  Date:   2022-05-31 (Tue, 31 May 2022)

  Changed paths:
    M doc/howto_release.md

  Log Message:
  -----------
  contributing: Make release procedure cleaner and more detailed (#2346)

- List all assumptions.
- Prep repo before a first update step.
- Create tag locally. GitHub Actions workflow creates the release.
- Unlike the 8.2.0RC1 and the past releases done through GitHub which created lightweight tags, create an annotated tag for more metatada (old tags converted from Subversion are annotated).
- Cover all cases for the version file updates.
- Remove the local copy reset after creation of a tag. There are no changes online which should be updated locally (unlike in the previous approach).
- Use consistent heading levels.
- Add step to publish the release.
- Mention the open issues or PRs in assumptions and milestone closing.
- Format git log and git show in text as code with backticks, although they really refer to the tools because they valid code too.


  Commit: 2d00cb8ad12fe95520ef2929c5c9219f52cf05b2
      https://github.com/OSGeo/grass/commit/2d00cb8ad12fe95520ef2929c5c9219f52cf05b2
  Author: Vaclav Petras <wenzeslaus at gmail.com>
  Date:   2022-05-31 (Tue, 31 May 2022)

  Changed paths:
    M doc/howto_release.md

  Log Message:
  -----------
  contributing: Add missing addons repo, headings (#2349)

* Add entry for grass-addons repo update (no new branch only, possibly move to branching howto or consider testing against latest release too).
* Improve heading structure in the last part of the document.
* Notifying packagers manually is no longer part of the procedure. They may follow GitHub or grass-dev/grass-accounce.


  Commit: ee221fe7a3dc356b824628e4bbb88fb4c6756be2
      https://github.com/OSGeo/grass/commit/ee221fe7a3dc356b824628e4bbb88fb4c6756be2
  Author: Vaclav Petras <wenzeslaus at gmail.com>
  Date:   2022-05-31 (Tue, 31 May 2022)

  Changed paths:
    M doc/howto_release.md
    M utils/update_version.py

  Log Message:
  -----------
  contributing: Create tag message, add more details (#2396)

* Tag message is created automatically.
* Version script clarifies meaning of the different messages it produces.
* Commit command for changed version file is easier to edit.
* More details in the tagging and general Git procedure.
* Acknowledge that checks may take some time to run.
* Add more about tags, changes, clarify releases versus branches.
* Add Zenodo DOI step, mention Binder and notebooks.

Based on releasing 8.2.0RC2.


  Commit: 2000463d4a0cdd1a095ed1142628906833ff977a
      https://github.com/OSGeo/grass/commit/2000463d4a0cdd1a095ed1142628906833ff977a
  Author: Vaclav Petras <wenzeslaus at gmail.com>
  Date:   2022-05-31 (Tue, 31 May 2022)

  Changed paths:
    M doc/howto_release.md

  Log Message:
  -----------
  contributing: Add separate section for OSGeo server uploads (#2405)

* Get the tag using Git assuming another person is doing the change, so variables need to be created and update version script gives a different status.
* Move changelog step to the server section because it is needed only for that and the file is needed on the computer.
* Move winGRASS steps into a separate section (copied as is).
* Fix syntax error in the tagging part of the doc.


  Commit: c73568691ba7f5477e3ea752b00d5d3b53689021
      https://github.com/OSGeo/grass/commit/c73568691ba7f5477e3ea752b00d5d3b53689021
  Author: Vaclav Petras <wenzeslaus at gmail.com>
  Date:   2022-05-31 (Tue, 31 May 2022)

  Changed paths:
    M .github/workflows/additional_checks.yml
    M .github/workflows/create_release_draft.yml

  Log Message:
  -----------
  CI: Add test run for release workflow (#2398)

* Run the create release workflow for PRs and on branches, too, for testing puproses, but exclude the release-only steps one by one. (Not even expression syntax is not checked when workflow does not run.)
* Fix expression syntax: Use single quotes for a string.
* Run only for selected paths for PRs, run always for selected branches and all tags.
* Upload artifacts always since now it runs for non-release commits as well.
* Don't use tags in the git log release notes test in additional checks because there for tags, this would be the same tag and so no difference (although the workflow now runs only for branches, not tags).
* Avoid confusion by adding 'check' into the workflow name.


  Commit: 19a846c6815f08d0199fcea5ead19ae9cfab6140
      https://github.com/OSGeo/grass/commit/19a846c6815f08d0199fcea5ead19ae9cfab6140
  Author: Vaclav Petras <wenzeslaus at gmail.com>
  Date:   2022-05-31 (Tue, 31 May 2022)

  Changed paths:
    M README.md
    R doc/notebooks/basic_example.ipynb
    R doc/notebooks/basic_example_grass_jupyter.ipynb
    R doc/notebooks/grass_jupyter.ipynb
    A doc/notebooks/jupyter_example.ipynb
    A doc/notebooks/jupyter_tutorial.ipynb
    A doc/notebooks/scripting_example.ipynb
    M python/grass/jupyter/__init__.py
    M utils/generate_release_notes.py

  Log Message:
  -----------
  grass.jupyter: Center notebooks around the package (#2408)

Previously, the primary notebook was the one without grass.jupyter. Now the shorter grass.jupyter is the primary one
and the original notebook is for scripting use cases only. The notebooks are still similar, so one can compare the
differences, but there is no need to keep this for future versions as the aim of having the comparison is valid only
for introduction of grass.jupyter, i.e., for 8.0 and 8.2.

The text now reflects that grass.jupyter is officially released. Some additional info is included, e.g., about the mini grant
which will become less relevant in the next versions and may be removed or significantly revised.

Other files, such as readme, now point to the notebook which is using grass.jupyter.


Compare: https://github.com/OSGeo/grass/compare/463f964b7172...19a846c6815f


More information about the grass-commit mailing list