is a web application framework that assists with creating single-page applications that only require HTML, CSS, and JavaScript on the client side.
| RELEASE.md (angular.js-1.7.9) | : | RELEASE.md (angular.js-1.8.0) |
|---|
| | |
| skipping to change at line 34 | | skipping to change at line 34 |
|---|
| 4) Push the changes to your private github repo and review. | | 4) Push the changes to your private github repo and review. |
| 5) cherry-pick the release notes commit to the appropriate branches. | | 5) cherry-pick the release notes commit to the appropriate branches. |
| | |
| ## Pick a commit to release (for this version) | | ## Pick a commit to release (for this version) |
| | |
| Usually this will be the commit containing the release notes, but it may also be
in the past. | | Usually this will be the commit containing the release notes, but it may also be
in the past. |
| | |
| ## Run "release" script | | ## Run "release" script |
| | |
| ```bash | | ```bash |
|
| scripts/jenkins/release.sh --git-push-dryrun=false --commit-sha=8822a4f --vers
ion-number=1.7.6 --version-name=gravity-manipulation | | scripts/release/release.sh --git-push-dryrun=false --commit-sha=8822a4f --vers
ion-number=1.7.6 --version-name=gravity-manipulation |
| ``` | | ``` |
| | |
| 1) The SHA is of the commit to release (could be in the past). | | 1) The SHA is of the commit to release (could be in the past). |
| | |
| 2) The version number and code-name that should be released, not the next vers
ion number (e.g. to release 1.2.12 you enter 1.2.12 as release version and the c
ode-name that was picked for 1.2.12, cauliflower-eradication). | | 2) The version number and code-name that should be released, not the next vers
ion number (e.g. to release 1.2.12 you enter 1.2.12 as release version and the c
ode-name that was picked for 1.2.12, cauliflower-eradication). |
| | |
| 3) You will need to have write access to all the AngularJS github dist reposit
ories and publish rights for the AngularJS packages on npm. | | 3) You will need to have write access to all the AngularJS github dist reposit
ories and publish rights for the AngularJS packages on npm. |
| | |
| ## Update GitHub milestones | | ## Update GitHub milestones |
| | |
| | |
| skipping to change at line 61 | | skipping to change at line 61 |
|---|
| | |
| ## Push build artifacts to CDN | | ## Push build artifacts to CDN |
| | |
| Google CDNs are fed with data from google3 every day at 11:15am PT it takes only
few minutes for the import to propagate). | | Google CDNs are fed with data from google3 every day at 11:15am PT it takes only
few minutes for the import to propagate). |
| If we want to make our files available, we need submit our CLs before this time
on the day of the release. | | If we want to make our files available, we need submit our CLs before this time
on the day of the release. |
| | |
| ## Don't update the package.json (branchVersion) until the CDN has updated | | ## Don't update the package.json (branchVersion) until the CDN has updated |
| | |
| This is the version used to compute what version to link to in the CDN. If you u
pdate this too early then the CDN lookup fails and you end up with 'null, for th
e version, which breaks the docs. | | This is the version used to compute what version to link to in the CDN. If you u
pdate this too early then the CDN lookup fails and you end up with 'null, for th
e version, which breaks the docs. |
| | |
|
| ## Verify angularjs.org download modal has latest version (updates via Travis jo
b) | | ## Verify angularjs.org download modal has latest version (updates via CI job) |
| | |
|
| The versions in the modal are updated (based on the versions available on CDN) a | | The versions in the modal are updated (based on the versions available on CDN) a |
| s part of the Travis deploy stage: https://github.com/angular/angularjs.org/blob | | s part of the CI deploy stage. |
| /a4d25c5abcd39e8ce19d31cb1c78073d13c4c974/.travis.yml#L26 | | (You may need to explicitly trigger the CI job. e.g. re-running the last `deploy |
| (You may need to explicitly trigger the Travis job. e.g. re-running the last job | | ` job.) |
| .) | | |
| | |
| ## Announce the release (via official Google accounts) | | ## Announce the release (via official Google accounts) |
| | |
| Double check that angularjs.org is up to date with the new release version befor
e sharing. | | Double check that angularjs.org is up to date with the new release version befor
e sharing. |
| | |
| 1) Collect a list of contributors | | 1) Collect a list of contributors |
| | |
| use: `git log --format='%aN' v1.2.12..v1.2.13 | sort -u` | | use: `git log --format='%aN' v1.2.12..v1.2.13 | sort -u` |
| | |
| 2) Write a blog post (for minor releases, not patch releases) and publish it wit
h the "release" tag | | 2) Write a blog post (for minor releases, not patch releases) and publish it wit
h the "release" tag |
| | | |
| End of changes. 3 change blocks. |
|---|
| 7 lines changed or deleted | | 6 lines changed or added |
|---|
"Fossies" - the Fresh Open Source Software Archive 