[Hadoop Wiki] Update of "HowToRelease" by MartonElek

2019-01-11 Thread Apache Wiki
Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Hadoop Wiki" for change 
notification.

The "HowToRelease" page has been changed by MartonElek:
https://wiki.apache.org/hadoop/HowToRelease?action=diff=100=101

Comment:
HADOOP-15205, dist profile is requierd to upload sources to the maven repo

   1. Push branch-X.Y.Z and the newly created tag to the remote repo.
   1. Deploy the maven artifacts, on your personal computer. Please be sure you 
have completed the prerequisite step of preparing the {{{settings.xml}}} file 
before the deployment. You might want to do this in private and clear your 
history file as your gpg-passphrase is in clear text.
   {{{
- mvn deploy -Psign -DskipTests -DskipShade
+ mvn deploy -Psign,dist -DskipTests -DskipShade
  }}}
   1. Copy release files to a public place and ensure they are readable. Note 
that {{{home.apache.org}}} only supports SFTP, so this may be easier with a 
graphical SFTP client like Nautilus, Konqueror, etc.
   {{{

-
To unsubscribe, e-mail: common-commits-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-commits-h...@hadoop.apache.org



[Hadoop Wiki] Update of "HowToRelease" by MartonElek

2018-10-31 Thread Apache Wiki
Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Hadoop Wiki" for change 
notification.

The "HowToRelease" page has been changed by MartonElek:
https://wiki.apache.org/hadoop/HowToRelease?action=diff=98=99

  mvn versions:set -DnewVersion=X.Y.Z
  }}}
  
- Note: Please also also update the hadoop.version property in the root pom.xml 
(see HADOOP-15369)
+ Note: Please also also update the hadoop.version property in the root pom.xml 
and hadoop.assemblies.version in hadoop-project/pom.xml (see HADOOP-15369)
+ 
+ {{{
+ mvn versions:set-property -Dproperty=hadoop.version -DnewVersion=X.Y.Z
+ 
+ mvn versions:set-property -Dproperty=hadoop.assemblies.version 
-DnewVersion=X.Y.Z
+ }}}
  
  Now, for any branches in {trunk, branch-X, branch-X.Y, branch-X.Y.Z} that 
have changed, push them to the remote repo taking care of any conflicts.


-
To unsubscribe, e-mail: common-commits-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-commits-h...@hadoop.apache.org



[Hadoop Wiki] Update of "HowToRelease" by MartonElek

2018-10-31 Thread Apache Wiki
Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Hadoop Wiki" for change 
notification.

The "HowToRelease" page has been changed by MartonElek:
https://wiki.apache.org/hadoop/HowToRelease?action=diff=97=98

Comment:
Reminder to change hadoop.version

  mvn versions:set -DnewVersion=X.Y.Z
  }}}
  
+ Note: Please also also update the hadoop.version property in the root pom.xml 
(see HADOOP-15369)
+ 
  Now, for any branches in {trunk, branch-X, branch-X.Y, branch-X.Y.Z} that 
have changed, push them to the remote repo taking care of any conflicts.
- 
+   
  {{{
  git push  
  }}}

-
To unsubscribe, e-mail: common-commits-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-commits-h...@hadoop.apache.org



[Hadoop Wiki] Update of "HowToRelease" by MartonElek

2018-10-26 Thread Apache Wiki
Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Hadoop Wiki" for change 
notification.

The "HowToRelease" page has been changed by MartonElek:
https://wiki.apache.org/hadoop/HowToRelease?action=diff=96=97

Comment:
Update site generation part.

1. effect the release of artifacts by selecting the staged repository and 
then clicking {{{Release}}}
1. If there were multiple RCs, simply drop the staging repositories 
corresponding to failed RCs.
   1. Wait 24 hours for release to propagate to mirrors.
-  1. Edit the website.
+  1. Edit the website (Generic docs about the new website generation can be 
found 
[[[https://cwiki.apache.org/confluence/display/HADOOP/How+to+generate+and+push+ASF+web+site+after+HADOOP-14163|here]])
1. Checkout the website if you haven't already
{{{
- svn co https://svn.apache.org/repos/asf/hadoop/common/site/main 
hadoop-common-site
+ git clone https://gitbox.apache.org/repos/asf/hadoop-site.git -b asf-site
- }}}
+   }}}
-   1. Update the documentation links in 
{{{author/src/documentation/content/xdocs/site.xml}}}.
-   1. Update the release news in 
{{{author/src/documentation/content/xdocs/releases.xml}}}.
-   1. Update the news on the home page 
{{{author/src/documentation/content/xdocs/index.xml}}}.
+   1. [[https://gohugo.io/getting-started/installing/|Install hugo]] if you 
haven't already ((tldr; apt-get install/pacman -S/brew install hugo)) 
+   1. Create the new release announcement
+   {{{
+ cat << EOF > src/release/${VERSION}.md
+ ---
+ title: Release ${VERSION} available
+ date: 201X-XX-XX
+ linked: true
+ ---
+ 
+ 
+ This is the first stable release of Apache Hadoop TODO line. It contains TODO 
bug fixes, improvements and enhancements since TODO.
+ 
+ Users are encouraged to read the [overview of major changes][1] since TODO.
+ For details of 435 bug fixes, improvements, and other enhancements since the 
previous TODO release, 
+ please check [release notes][2] and [changelog][3] 
+  detail the changes since TODO.
+ 
+ [1]: /docs/r${VERSION}/index.html
+ [2]: 
http://hadoop.apache.org/docs/r${VERSION}/hadoop-project-dist/hadoop-common/release/${VERSION}/RELEASENOTES.${VERSION}.html
+ [3]: 
http://hadoop.apache.org/docs/r${VERSION}/hadoop-project-dist/hadoop-common/release/${VERSION}/CHANGES.${VERSION}.html
+ 
+ EOF
+   }}} 
+   1. Note: update all the TODO + the date. '''Don't use date from the 
future''', it won't be rendered.
+   1. Remove the {{{linked: true}}} line from the previous release file, eg. 
from src/release/3.0.0.md. Docs/downloads of the releases with 
{{{linked:true}}} will be linked from the menu.
-   1. Copy the new release docs to svn and update the {{{docs/current}}} link, 
by doing the following:
+   1. add the docs and update the {{{content/docs/current}}} link, by doing 
the following:
{{{
- cd publish/docs
+ cd content/docs
  tar xvf /path/to/hadoop-${version}-site.tar.gz
  # Update current2, current, stable and stable2 as needed.
  # For example
@@ -191, +226 @@

  ln -s current2 current
  }}}
1. Similarly update the symlinks for stable if need be.
-   1. Add the documentation changes.
+   1. Check the rendering of the new site: {{{hugo serve && firefox 
http://localhost:1313}}}
+   1. Regenerate the site, review it, then commit it per the instructions in 
HowToCommit. (The generated HTML files also should be committed. Both src and 
the rendered site are in the same repo.)
{{{
+ hugo
+ git add .
+ git commit
+ git push
- svn add publish/docs/r${version}
- }}}
-   1. Regenerate the site, review it, then commit it per the instructions in 
HowToCommit.
-   {{{
- 
- 
- svn commit -m "Updated site for release X.Y.Z."
  }}}
   1. Send announcements to the user and developer lists once the site changes 
are visible.
   1. --(In JIRA, close issues resolved in the release.  Disable mail 
notifications for this bulk change.)-- Recommend '''not''' closing, since it 
prevents JIRAs from being edited and makes it more difficult to track backports.

-
To unsubscribe, e-mail: common-commits-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-commits-h...@hadoop.apache.org