Provide release candidate for 0.3.0 series #552
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Status
For discussion
Description of Changes
Reverts changes from #550
Fixes #540
Proposes a new naming scheme for release candidates, as we cannot use
~
Testing
update_version.sh
work as expected:./update_version.sh 0.2.4.next.rc2
increments and proper sdist naming for tarball and source location, and the package builds usingmake dom0-rpm
./update_version.sh 0.3.0
increments the version correctly, and package builds usingmake dom0-rpm
0.2.4.next.rc1
>0.2.4.
: Create two rpms and observe the output ofdnf install $RPM
and observe the upgrade/downgrade message at the confirmation prompt../securedrop-admin --apply
)