1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
|
# Release Process for GSS-Proxy
The process is currently quite simple and requires write access to the
project's git repository.
# Prepare the sources
## Version and Tag the release
- Change in version.m4 with the new version number (ex. 0.1.0)
- Test locally with "make rpms" that everything builds fine
- Make a signed tag for the release in the main branch like this:
```
git tag -s v0.1.0
```
This will apply the tag to the last commit
- Push the tag:
```
git push origin v0.1.0
```
## Create a release tarball and SHA hash
- Run the following commands (on a git clean tree, please):
```
autoreconf -f -i
./configure
make dist
make distcheck
```
... will generate a tarball named like: gssproxy-0.1.0.tar.gz
```
sha512sum gssproxy-0.1.0.tar.gz > gssproxy-0.1.0.tar.gz.sha512sum.txt
```
... will generate a file with a sha512 checksum
## Publish the release
- Use Github to create a Release page from the tag.
Use the option to create release notes from the PR log.
- Announce th new release on the gssproxy mailinglist
(https://lists.fedorahosted.org/mailman/listinfo/gss-proxy)
|
