Skip to content

Commit f30a25c

Browse files
fstagnialdbr
authored andcommitted
fix: minor fixes to the release process
1 parent e1be922 commit f30a25c

2 files changed

Lines changed: 7 additions & 11 deletions

File tree

docs/dev/explanations/extensions.md

Lines changed: 0 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -284,7 +284,3 @@ flowchart LR
284284
linkStyle 4 stroke: blue
285285
linkStyle 5 stroke: blue
286286
```
287-
288-
=== "Gitlab"
289-
290-
This assumes you are

docs/dev/how-to/make-a-release.md

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -2,11 +2,11 @@ This page describes how to mechanically make releases of DiracX and extensions.
22

33
# How to make a new DiracX release
44

5-
1. Merge any PR you want in your release
5+
Execute the following points in the presented order.
66

7-
2. Find the `release-please` [pull request](https://github.com/DIRACGrid/diracx/pulls?q=is%3Apr+is%3Aopen+%22chore%28main%29%3A+release%22) for your release
7+
1. Find the `release-please` [pull request](https://github.com/DIRACGrid/diracx/pulls?q=is%3Apr+is%3Aopen+%22chore%28main%29%3A+release%22) for your release. If you can't find it, it means that the currently existing latest release includes already all code changes.
88

9-
3. Review the release number **and** the content of the changelog
9+
2. Review the release number **and** the content of the changelog
1010

1111
- If you need to change the release number, follow the [ `release-please` doc](https://github.com/googleapis/release-please?tab=readme-ov-file#how-do-i-change-the-version-number)
1212

@@ -15,13 +15,13 @@ This page describes how to mechanically make releases of DiracX and extensions.
1515
git push upstream HEAD:main
1616
```
1717

18-
- TODO: update the release notes manually
18+
- If you want to update the release notes manually, follow the [`release-please` doc](https://github.com/googleapis/release-please?tab=readme-ov-file#how-can-i-fix-release-notes)
1919

20-
4. Merge the PR
20+
3. Merge the `release-please` PR
2121

22-
5. Check the [deployment action](https://github.com/DIRACGrid/diracx/actions/workflows/deployment.yml?query=event%3Apush+actor%3ADIRACGridBot)
22+
4. Check the [deployment action](https://github.com/DIRACGrid/diracx/actions/workflows/deployment.yml?query=event%3Apush+actor%3ADIRACGridBot)
2323

24-
6. Check that the [CI](https://github.com/DIRACGrid/diracx-charts/actions/workflows/chart-ci.yml?query=actor%3ADIRACGridBot) in `diracx-charts` is successful
24+
5. When the above will be finished, check that the [CI](https://github.com/DIRACGrid/diracx-charts/actions/workflows/chart-ci.yml?query=actor%3ADIRACGridBot) in `diracx-charts` is successful
2525

2626
At this stage, there is a new `diracx` and `diracx-chart` release.
2727

0 commit comments

Comments
 (0)