mirror of
https://github.com/amd/blis.git
synced 2026-05-05 15:01:13 +00:00
75da7f2a20
Details: - Updated ReleaseNotes.md in preparation for next version. - Updated docs/FAQ.md to reflect recent developments, and other edits. - Minor updates to RELEASING.
40 lines
1.1 KiB
Plaintext
40 lines
1.1 KiB
Plaintext
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. Verify that the code builds properly.
|
|
|
|
$ ./configure auto; make
|
|
|
|
3. 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)
|
|
|
|
4. Draft a new announcement to blis-devel, crediting those who
|
|
contributed towards this version by browsing 'git log'.
|
|
|
|
5. Update CREDITS file if 'git log' reveals any new contributors.
|
|
|
|
6. Update docs/ReleaseNotes.md file with body of finalized announcement
|
|
and the date of the release.
|
|
|
|
7. Bump the version number:
|
|
|
|
$ ./build/bump-version.sh "0.3.2"
|
|
|
|
8. Push the new commits and new tag associated with the new version:
|
|
|
|
$ git push
|
|
$ git push --tag
|
|
|
|
9. Send finalized announcement to blis-devel.
|
|
|