[
https://issues.apache.org/jira/browse/WW-5679?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lukasz Lenart updated WW-5679:
------------------------------
Fix Version/s: 7.4.0
> Document how to release struts-master and struts-annotations
> ------------------------------------------------------------
>
> Key: WW-5679
> URL: https://issues.apache.org/jira/browse/WW-5679
> 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]
> now document the release process for the framework itself, on both
> maintenance lines. They do not cover the auxiliary Maven artifacts the
> framework builds on.
> The wiki pages that used to describe those - "Building Struts Master"
> ([27839549|https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=27839549],
> last revised 2012) and "Building Struts Annotations"
> ([27832965|https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=27832965],
> 2011) - described releasing from Subversion. Both projects live in git now
> ([apache/struts-master|https://github.com/apache/struts-master],
> [apache/struts-annotations|https://github.com/apache/struts-annotations]), so
> the commands on those pages no longer work. Both pages have been replaced
> with stubs stating that plainly; the original content remains in each page's
> history.
> This leaves a real gap: phase 1 of the release guidelines tells the release
> manager to confirm that {{struts-master}} and {{struts-annotations}} are
> released versions rather than snapshots, but if either needs a new release
> there is no longer any documented way to make one.
> _To do_
> * Establish the current process for each. They are ordinary Maven artifacts
> deployed to Nexus, but the tag naming, whether each needs its own release
> vote, and the quality designation should be confirmed against current ASF
> release policy rather than carried over from the 2012 pages.
> * Document it, either as a section of the release guidelines or as a page
> linked from them.
> * Verify it against an actual release rather than writing it from memory -
> the last two attempts to document this process both drifted out of date
> without anyone noticing.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
