Details
-
Type: Sub-task
-
Status: Done/Fixed
-
Priority: Minor
-
Resolution: Fixed/Completed
-
Affects Version/s: Unscheduled
-
Fix Version/s: 4.7
-
Component/s: CiviCRM.org Website, Core CiviCRM
-
Labels:None
-
Documentation Required?:None
Description
Ideally
the releaser script should
- Prompt user to ask if this is a security release
- Prompt user to ask the status of this majorVersion (answer should be one of "lts" "eol" "stable" or "testing")
- Append new release to versions.json file
- Alter status of majorVersion if needed
- If we are releasing a brand new stable majorVersion, offer an option to change the status of the old one (versions.json shouldn't contain two majorVersions marked stable)