[
https://issues.apache.org/jira/browse/YETUS-331?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15186427#comment-15186427
]
Allen Wittenauer edited comment on YETUS-331 at 3/9/16 3:43 AM:
----------------------------------------------------------------
{code}
$ svn co https://dist.apache.org/repos/dist/dev/yetus/ yetus-dist-dev
$ cd yetus-dist-dev
$ mkdir 0.2.0-RC1
$ cd 0.2.0-RC1
$ cp path/to/yetus/target/RELEASENOTES.md path/to/yetus/target/CHANGES.md
path/to/yetus/target/*.tar.gz .
{code}
Need to add 0.2.0-RC1 to the svn tree.
{code}
YETUS-XXX. tag Apache Yetus 0.2.0 release.
vote thread: http://s.apache.org/yetus-0.2.0-rc1-vote
results: http://s.apache.org/yetus-0.2.0-vote-passes
{code}
Do we need a sample results post? Do we need documentation on how to point to
the mail threads? Also, pointing to the results thread can take an incredibly
long time to show up in the archive. We should either drop that or warn folks.
{code}
$ cp path/to/yetus-dist-dev/0.2.0-RC1 0.2.0
$ svn commit -m "Publish Apache Yetus 0.2.0"
{code}
Need an svn add.
{code}
Publish website updates. After the 24 hour window needed for the release
artifacts to make their way to the variety of mirrors, you should render the
website and publish it using the instructions found in Maintaing the Yetus
Website.
{code}
Link for "maintaing" has a typo and doesn't work.
{code}
Remove old releases from distribution area. The ASF distribution area should
only contain the most recent release for actively developed branches If your
release is a maintenance release, delete the prior release. If your release
marks the end of maintanence for an earlier minor or major release line, you
should delete those versions from the distribution area.
{code}
We should probably remove this and instead write up an EOL doc since we don't
have a policy yet and there is a lot more work to do than just removing the dir
from dist. (Mistakes here are also annoying to fix... he says, having had to
do it.)
was (Author: aw):
{code}
$ svn co https://dist.apache.org/repos/dist/dev/yetus/ yetus-dist-dev
$ cd yetus-dist-dev
$ mkdir 0.2.0-RC1
$ cd 0.2.0-RC1
$ cp path/to/yetus/target/RELEASENOTES.md path/to/yetus/target/CHANGES.md
path/to/yetus/target/*.tar.gz .
{code}
Need to add 0.2.0-RC1 to the svn tree.
{code}
YETUS-XXX. tag Apache Yetus 0.2.0 release.
vote thread: http://s.apache.org/yetus-0.2.0-rc1-vote
results: http://s.apache.org/yetus-0.2.0-vote-passes
{code}
Do we need a sample results post? Do we need documentation on how to point to
the mail threads? Also, pointing to the results thread can take an incredibly
long time to show up in the archive. We should either drop that or warn folks.
{code}
$ cp path/to/yetus-dist-dev/0.2.0-RC1 0.2.0
$ svn commit -m "Publish Apache Yetus 0.2.0"
{code}
Need an svn add.
{code}
Publish website updates. After the 24 hour window needed for the release
artifacts to make their way to the variety of mirrors, you should render the
website and publish it using the instructions found in Maintaing the Yetus
Website.
{code}
Link for "maintaing" as a typo and doesn't work.
{code}
Remove old releases from distribution area. The ASF distribution area should
only contain the most recent release for actively developed branches If your
release is a maintenance release, delete the prior release. If your release
marks the end of maintanence for an earlier minor or major release line, you
should delete those versions from the distribution area.
{code}
We should probably remove this and instead write up an EOL doc since we don't
have a policy yet and there is a lot more work to do than just removing the dir
from dist. (Mistakes here are also annoying to fix... he says, having had to
do it.)
> post-r0.2.0 doc feedback
> ------------------------
>
> Key: YETUS-331
> URL: https://issues.apache.org/jira/browse/YETUS-331
> Project: Yetus
> Issue Type: Improvement
> Components: website and documentation
> Reporter: Allen Wittenauer
>
> Some observations of things to update/clarify/fix now that we've done a
> release with the shiny new documentation. Details are in YETUS-318, but see
> first comment in this issue for the important points.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
