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
|
Here are the steps to follow to create a new release (version) of BLIS:
1. Make sure there are no commits that have yet to be pulled into
local repository.
$ git pull
If there are any commits upstream, merge them as appropriate.
2. Consider whether the so_version should be updated (via the so_version
file in the 'build' directory) due to any ABI changes since the previous
version. If so, commit that change now.
3. Verify that the code builds properly.
$ ./configure auto; make
4. Verify that the code passes BLIS and BLAS tests:
$ make check # BLIS testsuite (fast) + BLAS test drivers
$ make checkblis # BLIS testsuite (full ex. mixed-datatype)
$ make checkblis-md # BLIS testsuite (mixed-datatype only)
$ make checkblis-salt # BLIS testsuite (fast + salt)
5. Draft a new announcement to blis-devel, crediting those who
contributed towards this version by browsing 'git log'.
6. Update CREDITS file if 'git log' reveals any new contributors.
7. Update docs/ReleaseNotes.md file with body of finalized announcement
and the date of the release.
8. Commit changes from steps 5 and 6.
9. Bump the version number:
$ ./build/bump-version.sh "0.3.2"
This will result in two new commits: a version file update and a CHANGELOG
file update.
10. Push the new commits and new tag associated with the new version:
$ git push
$ git push --tag
11. Send finalized announcement to blis-devel.
|
