You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@camel.apache.org by GitBox <gi...@apache.org> on 2021/02/12 09:05:17 UTC

[GitHub] [camel-website] nicolaferraro commented on pull request #537: release: publish ui-bundle to let other projects reference it

nicolaferraro commented on pull request #537:
URL: https://github.com/apache/camel-website/pull/537#issuecomment-778070556


   > The new Antora based Asciidoctor docs site UI, at GitHub, has some tasks and actions to release a new version on each UI commit. That way you can be sure you know what you are getting. Dan has been saying for years the use of snapshots for the default UI is very ill-advised and finally did something about it for the Asciidoctor docs site. https://github.com/asciidoctor/asciidoctor-docs-ui.git <https://github.com/asciidoctor/asciidoctor-docs-ui.git> gulp.d/tasks/release.js .github/workflows/release.yml David Jencks
   > […](#)
   > On Feb 11, 2021, at 2:22 PM, github-actions[bot] ***@***.***> wrote:  Preview for [c74dbfd](https://github.com/apache/camel-website/commit/c74dbfd0ca73a629f9e54f4fe758b129f9ba7b05) <[c74dbfd](https://github.com/apache/camel-website/commit/c74dbfd0ca73a629f9e54f4fe758b129f9ba7b05)> is available at https://pr-537--camel.netlify.app <https://pr-537--camel.netlify.app/> — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <[#537 (comment)](https://github.com/apache/camel-website/pull/537#issuecomment-777831775)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAELDXUUKXDMUKC5KQ75TLLS6RKBNANCNFSM4XPSSOYA>.
   
   Hi, are you suggesting we should start releasing tags of the website at each (or specific commits) and attach the UI to each release? That would complicate a bit the workflow in subprojects that need to align, but we can think to it if it's worth.
   
   I can understand why Dan thinks that using snapshots for the default UI is a bad thing, an error there can break thousands of external projects that use it in "production". It's not exactly our context, where we want this only to have a preview of the subproject, because they don't live on their own.
   
   Personally I'd use both approaches here, so I can use snapshot in the subprojects until it breaks. 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.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org