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
54
55
56
57
58
59
60
|
***** VERY IMPORTANT *****
Test headless build.
Test clean build with clang.
Ensure all new files have been added to commit!!!
Don't forget to create and push the tag on releases!
use /usr/bin/appstream-util validate {file} to check metadata.
Get images from:
https://yoshimi.sourceforge.io/docs/user-guide
/src/CMakeLists.txt
Ensure version number is correct.
Disable extra compiler tests.
Before the commit (but after build) run the python file:
run 'sh set' to update build number and guide.
This will ensure the guide has the correct version number.
/desktop/yoshimi.1
Ensure version number and dates are correct.
Check for any changes in info or commands.
/desktop/metainfo/yoshimi.metainfo.xml
Ensure version number and dates are correct.
Check that urls for images are correct.
Check contact details.
/dev-notes
Ensure these notes are up-to-date - especially ToDo.txt
/doc
Ensure these are up-to-date - especially check yoshimi-user-manual
is up to date and has the correct version number.
Move Yoshimi_2.n.x_features.txt into doc/Histories and
replace with new one for the current version.
Changelog
Make sure the top line is the current release, not rc!
README.txt/README.md
Update!
set tag to release version.
push to both github and sourceforge.
Some of the Yoshimi Pi units out in the wild are set to the 'yoshipi'
branch. This is synchronised with the latest release version, so allows
those users to update without needing to know anything about the code.
Therefore, switch to the yoshipi branch and rebase this to the current
release pushing it to both github and sourceforge.
After commit release
Update wikipedia entry.
Tell everyone :)
|
