Notes |
|
(0021118)
|
Pol M
|
2020-01-25 12:49
|
|
Yep, the SRB2 crash specially justify a minor release. Let's do it!
(No, I'm not dead XD, I've been a little occupied with uni) |
|
|
(0021119)
|
Blzut3
|
2020-01-25 18:28
|
|
Added version 1.3.1 to this tracker. |
|
|
|
Sure, I guess I'll adjust the tracker's issues accordingly. |
|
|
(0021124)
|
Zalewa
|
2020-01-27 21:40
|
|
DONE:
1. Tagged 1.3.1
2. 1.3.1 release for Windows already uploaded to the beta channel.
3. Stable channel has the packages prepared but not enabled yet. All that needs to be done here is to rename the already uploaded "update-info_win32_stable_1.3.1.js" file to "update-info_win32_stable.js".
4. Website's code updated and pushed to the repo but not deployed to the server yet.
TODO:
1. Release Ubuntu & Mac binary packages - Blzut3
2. Build the signed ".tar.xz" source package for Doomseeker 1.3.1 and upload it to /files on the server - Blzut3
3. Rename the stable auto-update .js file - Zalewa/Blzut3
4. Deploy the website to the server - Zalewa/Blzut3
5. Forums announcement - Zalewa
I'll bring back the SRB2 plugin in the 1.3 Windows package to its original state after 1.3.1 release is complete (0003734).
This release is simpler because there were no changes to the Plugin API and Wadseeker had no notable changes, therefore steps that involved these can be skipped.
I'll prepare the release notification for the forums in a separate comment. |
|
|
|
Since this was categorized as "epic" and "Follow it as outlined in the previous release 1.3", I reported the relevant child issues. I hope they'll be useful to track what's going on with the release process, to keep this epic issue clean or meta.
Hoping this continues to be useful. |
|
|
|
Meta: It'd be a tiny bit "nicer" to release the source code tarball in /files before binary builds (in this case before Windows ZIP that went out), to avoid the most trivial error with license compliance. I understand that task would've been blocked by another person having to prepare the source tarball first (with signature) before others could've published binaries, if we would've done that. |
|
|
(0021132)
|
Zalewa
|
2020-01-28 18:06
|
|
Draft of the release announcement prepared as a private comment in 0003739. |
|
|
(0021135)
|
Blzut3
|
2020-01-29 05:44
|
|
WubTheCaptain, usually the time difference isn't this long but since I was out of town when the decision to do 1.3.1 came up it had to wait (well technically it didn't HAVE to wait, but it's easier for me this way). Was planning to do the packages today, but had a little too much going on so will have to push to tomorrow.
That said I'm fairly sure the GPL doesn't specify that the source must be provided in a tarball form so technically the tag in the repository is compliance. |
|
|
(0021146)
|
Zalewa
|
2020-01-30 07:26
|
|
|
|
|
Windows users: Please test 0003706 to be resolved.
Webmasters: 0003747.
Zalewa: 0003734.
Beyond that, 1.3.1 releases are out. |
|
|
(0021165)
|
Pol M
|
2020-01-30 16:07
|
|
|
|
|
Quote from Pol M AUR updated :P
Thanks for reminding. I'll track that as an issue, so I'll remember to track it for the next release too. |
|
|
|
Please test and resolve 0003706, to resolve this and close child issues... |
|