You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@beam.apache.org by "Davor Bonaci (JIRA)" <ji...@apache.org> on 2017/01/26 18:58:24 UTC
[jira] [Comment Edited] (BEAM-1317) Strategy around snippet
versioning
[ https://issues.apache.org/jira/browse/BEAM-1317?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15840219#comment-15840219 ]
Davor Bonaci edited comment on BEAM-1317 at 1/26/17 6:57 PM:
-------------------------------------------------------------
I think policy is the solution -- take snippets from a released version tag only (e.g., 'v1.2.3' tag), and grab the tag from where to pull from the top-level configuration file. (And slightly adjusted for features that are not yet released -- they should read from a HEAD for a branch they live in.)
No new post-commits needed, I think.
was (Author: davor):
I think policy is the solution -- take snippets from a released version tag only (e.g., 'v1.2.3' tag), and grab the tag from where to pull from the top-level configuration file.
No new post-commits needed, I think.
> Strategy around snippet versioning
> ----------------------------------
>
> Key: BEAM-1317
> URL: https://issues.apache.org/jira/browse/BEAM-1317
> Project: Beam
> Issue Type: Improvement
> Components: website
> Reporter: Daniel Halperin
> Assignee: Davor Bonaci
> Fix For: Not applicable
>
>
> Now that the website has the ability to import snippets from code, presumably some of these are pulled in from {{master}}. Do we need a postcommit to regenerate the website automatically in case master changes? Should we have a policy to never link to or get snippets from master?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)