-
Notifications
You must be signed in to change notification settings - Fork 0
Expand file tree
/
Copy pathDoingArelease.notes
More file actions
66 lines (50 loc) · 2.02 KB
/
DoingArelease.notes
File metadata and controls
66 lines (50 loc) · 2.02 KB
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
Notes on doing a release
- Have ChangeLog kept updated during development
- Also NEWS, THANKS, README and the doc/UrJTAG.txt
- Plus ../web/htdocs/index.html section 'Status'
So far the continues effort
The actual release
- Have or create awareness there is an upcoming release
- Version number is formatted as YYYY.MM
or as YYYY.MMpreN
- Update the version in configure.ac
- Put the same version number in NEWS
- ./autogen.sh
- make dist-xz # updates .po files
- git add po/*.po
- git commit -m 'po/*.po timestamps due `./autogen.sh`'
- git status
- Various `git add` on where needed
- Another `git commit`
- git tag
- git push
- git push --tags
- make dist-xz
- Some checksumming and signing
( there is tools/checksumming )
- Upload the .tar.xz and checksums to SoureForce
See https://sourceforge.net/p/forge/documentation/Files/ how
- update, build and commit web content, clue: ../web/Makefile
> If there are already some notes on doing a release,
> then please tell the mailinglist(archive) about it.
Hi,
work to do that already kept me from "simply releasing" a few times
because it takes a bit of time and diligence:
etc..
- (TBD) build binaries for download, especially for windows..
Do NOT make any last-minute functional/build/code changes. Just touch
documentation for the release.
The only overall change that I find worth considering at this moment
is maybe to separate all the handcrafted or compiled chip data
(urjtag/data content) from the actual UrJTAG code. Especially with the
"new" ability to read BSDL directly, the data/ lost its importance
somewhat. This question might be discussed especially by the
maintainers of urjtag packages for distribution?
Nb the "urjtag.com" and "urjtag.de" domain registration only lives
until the end of this year, but I'll continue to support
"urjtag.org". If the project is not moved somewhere else where there
is no webserver for the www. A record, as it is now configured with
sourceforge.. well, anyway, that is certainly not life-critical for
the project.
Regards,
Kolja