[
https://issues.apache.org/jira/browse/WW-5680?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lukasz Lenart updated WW-5680:
------------------------------
Fix Version/s: 7.4.0
> Document the milestone / release-candidate release process
> ----------------------------------------------------------
>
> Key: WW-5680
> URL: https://issues.apache.org/jira/browse/WW-5680
> Project: Struts 2
> Issue Type: Task
> Components: Documentation
> Reporter: Lukasz Lenart
> Priority: Major
> Fix For: 7.4.0
>
>
> The [release guidelines|https://struts.apache.org/release-guidelines.html]
> document a General Availability release. They do not describe how a milestone
> or release candidate differs, even though we make them - 7.0.0-M1 shipped,
> and release branches are named {{release/X.Y.Z-RC1}}.
> The old wiki page "Building Struts 2 - Fast track release"
> ([27834014|https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=27834014],
> last revised 2014) half-covered this, tangled together with a security
> fast-track procedure that is no longer followed. It has been replaced with a
> stub; the original content remains in the page's history.
> *Questions to settle*
> * Version and tag naming for a milestone ({{7.0.0-M1}} vs
> {{STRUTS\_7\_0\_0\_M1}}).
> * Whether a milestone gets the full 72 hour vote, and what quality
> designation it is voted to.
> * Whether milestone artifacts are promoted to {{dist/release}} and mirrored,
> or stay in {{dist/dev}}.
> * Whether milestones get an {{[ANN]}} mail, and to which lists.
> * Whether the Version Notes and site entries are created for milestones the
> same way as for GA.
> Once settled, add it to the release guidelines as a short section describing
> the deltas from the GA process rather than as a duplicate runbook - the two
> must not be able to drift apart.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
