[
https://issues.apache.org/jira/browse/DAFFODIL-2330?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Steve Lawrence updated DAFFODIL-2330:
-------------------------------------
Priority: Minor (was: Major)
> Release Container Updates
> -------------------------
>
> Key: DAFFODIL-2330
> URL: https://issues.apache.org/jira/browse/DAFFODIL-2330
> Project: Daffodil
> Issue Type: Improvement
> Components: Infrastructure
> Reporter: Olabusayo Kilo
> Priority: Minor
>
> We'd either like to create a new container or update the existing (with
> flags). Essentially we want to automate more steps of the release process. Up
> to date steps can be found
> [here|https://cwiki.apache.org/confluence/x/zgHgB]. But the gist of the
> updates can be found below
> Updating the Website
> * template page w/ release text
> * test and release
> Promote to Final Release
> * Moving release files
> {code:bash}
> svn mv -m "Release Apache Daffodil (incubating) 2.0.0" \
> https://dist.apache.org/repos/dist/dev/incubator/daffodil/2.0.0-rc1/ \
> https://dist.apache.org/repos/dist/release/incubator/daffodil/2.0.0/
> {code}
> * Creating, signing and pushing Git tag
> {code:bash}
> git clone [email protected]:apache/incubator-daffodil.git
> incubator-daffodil-2.0.0-rc1
> git tag -as -u KEYID -m "Release v2.0.0" v2.0.0 v2.0.0-rc1^{}
> git push asf v2.0.0
> {code}
> * Website modifications after mirrors have sycned
> * Archiving previous version in dist
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
