View Issue Details

IDProjectCategoryView StatusLast Update
0006120unrealircdpublic2022-06-05 08:30
Reportersyzop Assigned Tosyzop  
PrioritynormalSeverityfeatureReproducibilityN/A
Status resolvedResolutionfixed 
Product Version6.0.4-rc1 
Summary0006120: Ability to ./unrealircd upgrade to release candidate
DescriptionObviously don't upgrade to an RC if a user just types "./unrealircd upgrade"
But when the user explicitly requests it, eg via "./unrealircd upgrade --rc" or something like that. May also help with more testing of RC's.

TagsNo tags attached.
3rd party modules

Activities

Valware

2022-05-31 18:54

reporter   ~0022544

hello Syzop thanks for your bug report
FWIW: I think it's a good idea, I would certainly make use of it, lets see what Syzop thinks

=]

have a great day!

syzop

2022-06-05 08:28

administrator   ~0022550

Last edited: 2022-06-05 08:30

Yeah, great idea! Implemented now.

"./unrealircd upgrade" will now detect if you are using an RC, and if so it would upgrade you the very latest version.. whether it is a stable or an RC version.
This means 6.0.4-rc1 upgrades to 6.0.4-rc2, and when stable is out it will upgrade to 6.0.4.

"./unrealircd upgrade --rc" can be used to go from a stable to a RC. Such as 6.0.3 to 6.0.4-rc2.

Caveats (things that happen but that I don't care about at all at the moment because it is no issue)
* if you eg end up from 6.0.4-rc1 to 6.0.4-rc2 and then to stable 6.0.4, you are then considered on 'stable', so a next "./unrealircd upgrade" without --rc would not upgrade you to a 6.0.5-rc1, you need to use explicit pass --rc then to go from a stable to rc. In other words: we don't have a concept of a "release" channel and a "beta" channel as some other projects have.
* I did not bother for the case when there would be RC's on both branches, it assumes RC's only exist in 6.x at the moment.

This change is in the stage2 upgrade script which is fetched online (along with its GPG signature) so there is no commit for it in the unrealircd repo. It should work for 5.0.9+ or 5.2.0+ at least.

Issue History

Date Modified Username Field Change
2022-05-31 18:35 syzop New Issue
2022-05-31 18:35 syzop Assigned To => syzop
2022-05-31 18:35 syzop Status new => confirmed
2022-05-31 18:35 syzop Description Updated
2022-05-31 18:54 Valware Note Added: 0022544
2022-06-05 08:28 syzop Status confirmed => resolved
2022-06-05 08:28 syzop Resolution open => fixed
2022-06-05 08:28 syzop Note Added: 0022550
2022-06-05 08:29 syzop Note Edited: 0022550
2022-06-05 08:30 syzop Note Edited: 0022550