-
Notifications
You must be signed in to change notification settings - Fork 148
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Improve the version/release process to include docs in the tagged commit #406
Comments
nicksay
added a commit
to nicksay/spfjs
that referenced
this issue
May 25, 2016
This change updates `bower.json` to remove the following deprecated fields: - `version` (Ignored by Bower in favor of git tags) And, this change adds the following recommended fields: - `moduleType` (The type of module defined in the `main` file) Progress on youtube#406
nicksay
added a commit
to nicksay/spfjs
that referenced
this issue
May 25, 2016
This change allows the `gendocs.sh` script to update the generated documentation for SPF from the latest commit instead of only from an existing tag. This will allow updating the documentation for an upcoming release before it is tagged. Progress on youtube#406.
nicksay
added a commit
to nicksay/spfjs
that referenced
this issue
May 25, 2016
This change allows the `gendocs.sh` script to update the generated documentation for SPF from the latest commit instead of only from an existing tag. This will allow updating the documentation for an upcoming release before it is tagged. Progress on youtube#406
nicksay
added a commit
to nicksay/spfjs
that referenced
this issue
May 25, 2016
This change allows the `gendocs.sh` script to update the generated documentation for SPF from the latest commit instead of only from an existing tag. This will allow updating the documentation for an upcoming release before it is tagged. Progress on youtube#406.
nicksay
added a commit
to nicksay/spfjs
that referenced
this issue
May 25, 2016
This change adds a `version.sh` script that updates the version of SPF and then updates the generated documentation. Each update is recorded as a single commit, and when the branch is merged, the merge commit will be used as the release tag. This will mean that tagged releases will included the correct generated documentation for the version being released. Progess on youtube#406
nicksay
added a commit
to nicksay/spfjs
that referenced
this issue
May 25, 2016
This change adds a `version.sh` script that updates the version of SPF and then updates the generated documentation. Each update is recorded as a single commit, and when the branch is merged, the merge commit will be used as the release tag. This will mean that tagged releases will included the correct generated documentation for the version being released. Progess on youtube#406
nicksay
added a commit
to nicksay/spfjs
that referenced
this issue
May 25, 2016
This change adds a `version.sh` script that updates the version of SPF and then updates the generated documentation. Each update is recorded as a single commit, and when the branch is merged, the merge commit will be used as the release tag. This will mean that tagged releases will included the correct generated documentation for the version being released. Progess on youtube#406
nicksay
added a commit
to nicksay/spfjs
that referenced
this issue
May 25, 2016
This change allows the `gendocs.sh` script to update the generated documentation for SPF from the latest commit instead of only from an existing tag. This will allow updating the documentation for an upcoming release before it is tagged. Progress on youtube#406
nicksay
added a commit
to nicksay/spfjs
that referenced
this issue
May 25, 2016
This change allows the `gendocs.sh` script to update the generated documentation for SPF from the latest commit instead of only from an existing tag. This will allow updating the documentation for an upcoming release before it is tagged. Progress on youtube#406
nicksay
added a commit
to nicksay/spfjs
that referenced
this issue
May 25, 2016
This change adds a `version.sh` script that updates the version of SPF and then updates the generated documentation. Each update is recorded as a single commit, and when the branch is merged, the merge commit will be used as the release tag. This will mean that tagged releases will included the correct generated documentation for the version being released. Progess on youtube#406
nicksay
added a commit
to nicksay/spfjs
that referenced
this issue
Jun 1, 2016
nicksay
added a commit
to nicksay/spfjs
that referenced
this issue
Jun 1, 2016
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently, the tagged git commit for each version does not include the updated docs for that version. Improve the version/release process to fix that.
The text was updated successfully, but these errors were encountered: