You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jena.apache.org by GitBox <gi...@apache.org> on 2022/09/08 12:41:31 UTC
[GitHub] [jena-site] afs opened a new pull request, #119: Deploy website from branch 'publish'
afs opened a new pull request, #119:
URL: https://github.com/apache/jena-site/pull/119
We get changes for the website that are changes to go into the next release.
There are also changes that should go out immediately.
So there are two workflows. Currently, release-changes get held as approved PRs. This is workable but the approved PRs aren't checked against each other or for PRs-to-PRs.
An alternative is to have a branch for accumulated changes for the next release. We should make it the default branch because tooling tends to end up with PRs to the default branch. Keep `main` for this.
There is a `publish` is a new branch from which the currently deployed website.
On a release, merge `main` into `publish`.
The burden is than on website fixes. They need to go to `publish`. We can edit the target PRs through GH UI.
So with this change, we have two branches. And probably so friction if a PR goes to `main` instead of `publish`. We can cherry-pick but it is a different commit. `merge` when publishing the next version may get this right, or it may not.
This PR is the one-line `Jenkinsfile` change (untested).
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscribe@jena.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [jena-site] rvesse commented on pull request #119: Deploy website from branch 'publish'
Posted by GitBox <gi...@apache.org>.
rvesse commented on PR #119:
URL: https://github.com/apache/jena-site/pull/119#issuecomment-1240681284
Probably need to consider which branches we publish the staging site from as well?
Currently anything other than `main` goes to the Staging site, so maybe change that to have only `main` go to the Staging site. Downside of that is that you can't then preview a given PR on the staging site until it merges to `main`
WDYT?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscribe@jena.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [PR] Deploy website from branch 'publish' [jena-site]
Posted by "afs (via GitHub)" <gi...@apache.org>.
afs closed pull request #119: Deploy website from branch 'publish'
URL: https://github.com/apache/jena-site/pull/119
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscribe@jena.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [jena-site] afs commented on pull request #119: Deploy website from branch 'publish'
Posted by GitBox <gi...@apache.org>.
afs commented on PR #119:
URL: https://github.com/apache/jena-site/pull/119#issuecomment-1240694615
Good point - we can repurpose `asf-staging` so it does not have only one PR on it.
Maybe even align the names because `https://jena.staged.apache.org/` fools me every time!
Do we need (on a shared place) a per-PR preview?
local hugo is pretty good because gives a faster edit-preview cycle, at the cost of install hugo locally.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscribe@jena.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org