Skip to content

Commit a724593

Browse files
committed
Update release guide site staging instructions
1 parent 69c949b commit a724593

1 file changed

Lines changed: 19 additions & 29 deletions

File tree

doc/release/release.howto.txt

Lines changed: 19 additions & 29 deletions
Original file line numberDiff line numberDiff line change
@@ -548,19 +548,7 @@ Create and upload the other distribution files to the Apache servers.
548548
to the "dist dev" area of the svn repository. However, for multi-module
549549
maven projects, the site is incomplete.]
550550

551-
As the web site staging area is shared among all commons components and therefore
552-
could be published before the vote ends, it is not recommended to use the standard
553-
staging area for the release candidate. So you will just archive the site and
554-
transfer it to your apache personal area for review.
555-
Here is how to do this using "lftp" to initiate the sftp transfer. "lftp" supports
556-
a mirror command for recursive transfers; don't forget the -R flag for uploading
557-
instead of downloading the site.
558-
If you haven't setup your login on home.apache.org you will need to go to
559-
https://id.apache.org/
560-
login and copy the contents of your
561-
~/.ssh/id_rsa.pub
562-
file to "SSH Key (authorized_keys line)".
563-
Then run these commands:
551+
Generate the multi-module site for the web site staging area.
564552

565553
Note: Site generation requires Java 11 for the examples JPMS modules.
566554
With site generation the 'package' goal is required for the site report javadoc
@@ -575,26 +563,28 @@ Then run these commands:
575563
To ensure the javadocs are searchable from Java 8 requires a package-list. This
576564
can be created by copying the element-list. This is only required for the Java 8
577565
modules:
578-
579-
$ find target/staging/commons-rng-client-api \
580-
target/staging/commons-rng-core \
581-
target/staging/commons-rng-simple \
582-
target/staging/commons-rng-sampling \
583-
target/staging/commons-rng-docs \
584-
-name element-list -execdir cp {} package-list \;
566+
567+
$ find target/staging -name element-list -execdir cp {} package-list \;
585568

586569
$ cd target
587570
$ mv staging commons-rng-1.6-RC1-site
588-
$ lftp sftp://__Your_apache_login__@home.apache.org
589-
lftp you@home.apache.org:~> mkdir public_html
590-
lftp you@home.apache.org:~> cd public_html
591-
lftp you@home.apache.org:~/public_html> mirror -R commons-rng-1.6-RC1-site
592-
lftp you@home.apache.org:~/public_html> bye
593571

594-
If lftp fails with 'Fatal error: Host key verification failed.' then the host
595-
key for home.apache.org may have changed. Try to ssh to the server. This will be
596-
refused as only ftp connections are allowed but the error message should
597-
describe how to update the SSH known hosts to remove the error.
572+
Checkout the dev staging area. This assumes that the site folder was removed in
573+
validation steps performed in step (12):
574+
575+
$ svn checkout https://dist.apache.org/repos/dist/dev/commons/rng --depth immediates
576+
$ cd rng/1.6-RC1
577+
578+
Update the site folder:
579+
580+
$ cp -pR [path/to/]commons-rng-1.6-RC1-site site
581+
$ svn add site
582+
$ svn commit -m "Site files for Commons RNG v1.6 (RC1)."
583+
584+
Wait for the files to sync and validate the site at:
585+
586+
https://dist.apache.org/repos/dist/dev/commons/rng/1.6-RC1/site
587+
598588

599589
(14)
600590
[NOTE: The "Commons release-plugin" can generate the text for the "[VOTE]"

0 commit comments

Comments
 (0)