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
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
|
Release checklist for Tux Paint
Last updated 2021-02-05 -bjk
During development
------------------
Make sure any new options are documented in the "OPTIONS" docs
(now maintained in the "tuxpaint-docs" repository; see below),
the manpage (see below), and listed in the shell completion file
(src/tuxpaint-completion.bash), as appropriate.
Preparing
---------
Do these things _prior_ to cutting a release -- that is, prior to
tagging in the source code repository, running "make release" to roll
a .tar.gz source tarball, and making the tarball available for download.
* Update version # and release dates
Places to make sure version # and release date gets updated,
* Makefile
* Build description files:
* tuxpaint.spec (Linux RPM package)
* macos/Info.plist (macOS build)
* win32/resources.rc (Windows mingw/msys build)
* Changelog
* docs/CHANGES.txt
* Other Documentation
NOTE: As of Tux Paint 0.9.26, most of the documentation
is now maintained in a separate source-code repository,
"tuxpaint-docs". Updates should be made there, and
then copied over to the "tuxpaint" repository.
Here, be sure to run "make" in "docs/", to produce plaintext
alternatives of the HTML files.
* docs/en/html/README.html
* docs/en/html/FAQ.html
* docs/en/html/OPTIONS.html
* docs/en/html/EXTENDING.html
* docs/en/html/ADVANCED-STAMPS-HOWTO.html
* Manual page (manpage)
* src/manpage/tuxpaint.1
* Rebuild 'tuxpaint.desktop' by running "update-po.sh" in "src/po/"
* Don't forget to commit the changes! (git add ... / git commit / git push)
Time to release:
----------------
* Tag & roll a release tarball (example here was from 0.9.25):
$ git pull
$ make clean
$ git tag tuxpaint-0_9_25-2020-12-27
$ git push origin tuxpaint-0_9_25-2020-12-27 # or --tags
$ make release
* Upload each project's ".tar.gz" file from their "build/" subdirs
to ftp.tuxpaint.org.
* Place them in the appropriate subdirectories (source/, config/,
and stamps/) under "unix/x/tuxpaint/".
* Copy "docs/CHANGES.txt" from each project onto the FTP site
(Tux Paint's goes in the toplevel, the others go in config/ and
stamps/).
* Create a new PAD file (e.g. `pads/tuxpaint-0.9.25.xml`) on the
FTP site.
* Replace the "pads/tuxpaint-LATEST.xml" symlink on the FTP site with
a new one that points to the new PAD file.
* At SourceForge, go to "Files" and use "Add Folder" under each project
to create new release file subdirectories. (e.g., "0.9.25" under
https://sourceforge.net/projects/tuxpaint/files/tuxpaint/)
* Upload the files! Either from local copies, via a web browser,
or by SCP, Rsync, or SFTP (see
https://sourceforge.net/p/forge/documentation/Release%20Files%20for%20Download/#scp)
e.g.:
$ sftp wkendrick@frs.sourceforge.net
sftp> cd /home/frs/project/tuxpaint/
sftp> cd tuxpaint/0.9.25/
sftp> lcd source
sftp> put tuxpaint-0.9.25.tar.gz
sftp> cd ../..
sftp> lcd ..
[repeat for tuxpaint-config and tuxpaint-stamps]
* Copy latest release's documentation to the tuxpaint.org website.
Website updates
---------------
* List new features on http://www.tuxpaint.org/features/
* Add any new requirements to http://www.tuxpaint.org/requirements/
Announcements
-------------
* Managed by Tux Paint
+ Tux Paint website
- Site: http://www.tuxpaint.org/
- Submissions: [add announcement to /latest/]
+ Tux Paint on Facebook
- Site: https://www.facebook.com/TuxPaint
- Submissions: [currently managed by Bill K.]
+ Tux Paint on Twitter
- Site: https://www.facebook.com/TuxPaint
- Submissions: [currently managed by Bill K.]
* News sites & magazines
+ Linux Today
- Site: https://www.linuxtoday.com/
- Twitter: https://twitter.com/linuxtoday
- Submissions: https://www.linuxtoday.com/contribute.html
+ 9to5Linux
- Site: https://9to5linux.com/
- Twitter: https://twitter.com/9to5linux
- Submissions: https://9to5linux.com/contact-us
+ Fossbytes
- Site: https://fossbytes.com/
- Twitter: https://twitter.com/Fossbytes14
- Submissions: admin [at] fossbytes.com
+ EdTech K12 Magazine
- Site: https://edtechmagazine.com/k12/
- Twitter: https://twitter.com/EdTech_K12
- Submissions: https://edtechmagazine.com/k12/contact-us (?)
* Software databases
+ MacUpdate
- Site: https://www.macupdate.com/
- Submissions: [currently managed by Bill K.]
* Linux repositories
+ Fedora -- process TBD
+ openSUSE -- process TBD
+ Debian -- process TBD
+ Ubuntu -- process TBD
+ Slackware -- process TBD
+ ...others?
* Paid promotions
+ Facebook boost
+ Newswire.com
|
