[
https://issues.apache.org/jira/browse/SLING-7913?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16610835#comment-16610835
]
Eric Norman commented on SLING-7913:
------------------------------------
Hmm... I'm still not convinced. Do you mean enforced at release-time only? A
ban at build time doesn't really work unless a lot more work is done everywhere
that the starter is referenced whenever you want to do integration testing of a
snapshot.
For example, I believe the starter snapshot is used for launchpad-testing and
other places:
[https://github.com/apache/sling-org-apache-sling-launchpad-testing/blob/0b750515f80db769976231bf0da05ab4f92f3342/src/main/provisioning/model.txt]
Aren't we just trading one problem for another for the convenience of the
person doing the release?
> Ban snapshots in the Sling starter
> ----------------------------------
>
> Key: SLING-7913
> URL: https://issues.apache.org/jira/browse/SLING-7913
> Project: Sling
> Issue Type: Bug
> Components: Starter
> Reporter: Robert Munteanu
> Priority: Major
> Fix For: Starter 11
>
>
> We have agreed to keep only releases in the Sling starter to make it easier
> to release and to make builds reproducible.
> We should enforce this policy to make it impossible to mistakenly add
> SNAPSHOT versions to the project.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
