Skip to content

Commit e8a1cdf

Browse files
committed
[docs] Improve release process
1 parent 2eaa4dd commit e8a1cdf

File tree

1 file changed

+16
-22
lines changed
  • docs/docs-site/content/developer/development

1 file changed

+16
-22
lines changed

docs/docs-site/content/developer/development/_index.md

Lines changed: 16 additions & 22 deletions
Original file line numberDiff line numberDiff line change
@@ -827,10 +827,14 @@ Historically, the same thing used to be done with the `requires_hadoop` tag:
827827

828828
## Releasing
829829

830-
The checklist below details the steps. Then send the release notes to the [Forum](https://discourse.gethue.com/), [hue-user](https://groups.google.com/a/cloudera.org/forum/#!forum/hue-user), https://twitter.com/gethue !
830+
The checklist below details the steps. Then send the release notes to the [Forum](https://discourse.gethue.com/) and https://twitter.com/gethue!
831+
832+
Also update https://wikipedia.org/wiki/Hue_(Software).
831833

832834
### Version
833835

836+
Here is an example of [commit](https://github.com/cloudera/hue/commit/9de217d6b6).
837+
834838
Update the versions to the next release (current release +1):
835839

836840
:100644 100644 4db6d5f... f907d04... M VERSION
@@ -849,6 +853,8 @@ And add them and the authors to the release notes:
849853

850854
git log --pretty="%an" | sort | uniq | sed 's/^\(.*\)/* \1/' > authors.txt
851855

856+
### Git
857+
852858
Pushing the release branch:
853859

854860
git push origin HEAD:branch-4.8.0
@@ -858,6 +864,12 @@ Tagging the release:
858864
git tag -a release-4.8.0 -m "release-4.8.0"
859865
git push origin release-4.8.0
860866

867+
Draft a new release on https://github.com/cloudera/hue/releases.
868+
869+
Publish Github NPM package and Docker images at https://github.com/orgs/cloudera/packages?repo_name=hue.
870+
871+
### Gethue
872+
861873
Building the tarball release:
862874

863875
git checkout -b release-4.8.0 release-4.8.0
@@ -869,16 +881,9 @@ Push to the CDN:
869881

870882
scp hue-4.8.0.tgz [email protected]:/var/www/cdn.gethue.com/downloads
871883

872-
### Websites
884+
### Docker
873885

874-
Other things to update:
875-
876-
* In Jira, setting the [release as shipped](https://issues.cloudera.org/projects/HUE?selectedItem=com.atlassian.jira.jira-projects-plugin%3Arelease-page&status=all) and moving all non finished jiras to another target. Also archiving old releases.
877-
* Create the after next release tag in Jira and Blog
878-
* Update Docker image https://hub.docker.com/u/gethue/
879-
* Update release date on https://wikipedia.org/wiki/Hue_(Software)
880-
881-
Instructions:
886+
Docker image are at https://hub.docker.com/u/gethue/:
882887

883888
docker build https://github.com/cloudera/hue.git#release-4.8.0 -t gethue/hue:4.8.0 -f tools/docker/hue/Dockerfile
884889
docker tag gethue/hue:4.8.0 gethue/hue:latest
@@ -898,20 +903,9 @@ Documentation is currently being auto refreshed every morning of the week and ru
898903

899904
The manual process otherwise would be to [build it](#Documentation) and push it to the docs host.
900905

901-
### Release
902-
903-
904-
cd /var/www/docs.gethue.com
905-
mkdir 4.8.0
906-
rm latest; ln -s 4.8.0 latest
907-
908-
scp -r docs/docs-site/public/* [email protected]:/var/www/docs.gethue.com/4.8.0
909-
910-
scp -r hue-4.6/build/release/prod/hue-4.8.0.tgz [email protected]:/var/www/cdn.gethue.com/downloads/
911-
912906
### NPM registry
913907

914-
To publish gethue to NPM registry, the following command would have to be run. Kindly refrain from using `npm publish`.
908+
To publish gethue to the [NPM registry](https://www.npmjs.com/package/gethue), the following command would have to be run.
915909

916910
npm run publish-gethue
917911

0 commit comments

Comments
 (0)