EES-5656 Rename Admin 'Legacy releases' to 'Release order' #5442
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…g.robot following rename of Legacy releases page to Release order
mmyoungman
reviewed
Dec 9, 2024
… page to Release order
mmyoungman
approved these changes
Dec 9, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This PR renames the Admin 'Legacy releases' page to 'Release order'.
This is being done to make it more obvious that this page allows reordering releases which will become more commonly required when 'Release labelling' is made available by EES-5626.
When release labelling is introduced, we will allow a publication to contain multiple releases with the same year and time identifier.
Our traditional way of ordering releases within a publication in reverse chronological order by year and then by time period will no longer work after we lose this time period uniqueness. There will be no secondary sorting by label and analysts will decide which release should appear first or last.
The same possibility applies to the 'latest' release for a publication which is currently determined automatically by the first release in the reverse chronological order. In future analysts will be able to decide which release it should be by ordering that release as the top entry on this page.
This change to the title is being made separately ahead of other changes to the page as part of EES-5656.
Before:
After:
UI test result