Skip to content
This repository was archived by the owner on Apr 12, 2024. It is now read-only.

Can the Angular docs on the website be made to deault to the latest stable release? #9674

Closed
keirlawson opened this issue Oct 18, 2014 · 3 comments
Closed

Can the Angular docs on the website be made to deault to the latest stable release? #9674

keirlawson opened this issue Oct 18, 2014 · 3 comments
Labels
type: docs type: feature
Milestone
Ice Box

Comments

@keirlawson
Copy link

They seem to point to the latest git revision by default which is probably not what most people are using.
@Narretz Narretz added this to the Ice Box milestone Oct 18, 2014
@Narretz
Copy link
Contributor

Narretz commented Oct 18, 2014

Definitely a possibility.
But we shouldn't underestimate the number of people who use the latest release / snapshot. Angular is pretty stable (I'd say) and the releases have been very frequent.

@mikeborozdin
Copy link

+1

I've been caught in a situation when I'm reading a documentation of the latest pre-release, while still using an older, yet stable, version in production. Obviously, I couldn't follow the documentation word-by-word in this case.

@Narretz
Copy link
Contributor

Narretz commented Oct 14, 2016 •
edited
Loading

The main thing that needs to be done is:

  • create a build on Jenkins to push the latest release to a standard url such as code.angularjs.org/latest -> use the package.json distTag to figure out if the version is the latest stable
  • change the configuration of the angularjs.org web-server to point docs.angularjs.org to point that url
  • change the version dropdown so that master points to code.angularjs.org/snapshot

Narretz added a commit to Narretz/angular.js that referenced this issue Jul 11, 2017
@Narretz
chore: deploy docs|code .angularjs.org to Firebase via Travis
7b43332 
- code.angularjs.org and docs.angularjs.org are two separate Firebase projects
- both are automatically deployed via Travis config
- Travis is split up into 2 build stages: first, all tests are run, and if they pass, the deploy
stage runs a single job with both deployments (actual deployment depends on the state of the commit)
- docs. is deployed directly to Firebase hosting
- code. is uploaded to Firebase Google Cloud Storage and uses Firebase hosting rewrites to acces the
files
- jenkins builds still push the code builds to the code.angularjs.org Github repository

Closes angular#9674
@Narretz Narretz mentioned this issue Jul 11, 2017
Merged
Narretz added a commit to Narretz/angular.js that referenced this issue Jul 12, 2017
@Narretz
chore: deploy docs|code .angularjs.org to Firebase via Travis
b841696 
- code.angularjs.org and docs.angularjs.org are two separate Firebase projects
- both are automatically deployed via Travis config
- Travis is split up into 2 build stages: first, all tests are run, and if they pass, the deploy
stage runs a single job with both deployments (actual deployment depends on the state of the commit)
- docs. is deployed directly to Firebase hosting
- code. is uploaded to Firebase Google Cloud Storage and uses Firebase hosting rewrites to acces the
files
- jenkins builds still push the code builds to the code.angularjs.org Github repository

Closes angular#9674
Narretz added a commit to Narretz/angular.js that referenced this issue Jul 14, 2017
@Narretz
chore(*): deploy (docs|code) .angularjs.org to Firebase via Travis
f7e959a 
- code.angularjs.org and docs.angularjs.org are two separate Firebase projects
- both are automatically deployed via Travis config
- Travis is split up into 2 build stages: first, all tests are run, and if they pass, the deploy
stage runs a single job with both deployments (actual deployment depends on the state of the commit)
- docs. is deployed directly to Firebase hosting
- code. is uploaded to Firebase Google Cloud Storage and uses Firebase hosting rewrites to acces the
files
- jenkins builds still push the code builds to the code.angularjs.org Github repository

Closes angular#9674
Closes angular#16093
Narretz added a commit to Narretz/angular.js that referenced this issue Jul 14, 2017
@Narretz
chore(*): deploy (docs|code) .angularjs.org to Firebase via Travis
8cac484 
- code.angularjs.org and docs.angularjs.org are two separate Firebase projects
- both are automatically deployed via Travis config
- Travis is split up into 2 build stages: first, all tests are run, and if they pass, the deploy
stage runs a single job with both deployments (actual deployment depends on the state of the commit)
- docs. is deployed directly to Firebase hosting
- code. is uploaded to Firebase Google Cloud Storage and uses Firebase hosting rewrites to acces the
files
- jenkins builds still push the code builds to the code.angularjs.org Github repository

Closes angular#9674
Closes angular#16093
Narretz added a commit that referenced this issue Jul 14, 2017
@Narretz
chore(*): deploy (docs|code) .angularjs.org to Firebase via Travis
8b4d85c 
- code.angularjs.org and docs.angularjs.org are two separate Firebase projects
- both are automatically deployed via Travis config
- Travis is split up into 2 build stages: first, all tests are run, and if they pass, the deploy
stage runs a single job with both deployments (actual deployment depends on the state of the commit)
- docs. is deployed directly to Firebase hosting
- code. is uploaded to Firebase Google Cloud Storage and uses Firebase hosting rewrites to acces the
files
- jenkins builds still push the code builds to the code.angularjs.org Github repository

Closes #9674
Closes #16093
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
type: docs type: feature
Projects
None yet
Milestone
Ice Box
Development

No branches or pull requests
3 participants
@keirlawson @Narretz @mikeborozdin