[
https://issues.apache.org/jira/browse/SLING-7935?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17087096#comment-17087096
]
Oliver Lietz commented on SLING-7935:
-------------------------------------
[~rombert], How does it answer my question?
{quote}We release the tests to capture the state of how Sling worked for that
certain release, [...]
{quote}
Is the above your point? With that approach you cover the state only for a
Sling Starter release – once for a period of one to two years.
If we release the modules when required we cover also the state between Starter
releases. That makes tracking of changes easier and the modules evolve
independently anyway.
Workflow:
# (Try to) Add a new version of a bundle to Starter
# Test breaks
# Fix test/support bundle
# Release test/support bundle
# Update test/support bundle in Starter
# Finally add the new version of bundle to Starter
With that workflow the committer who wants to update Starter is also
responsible for the integration tests. This means also no more snapshots in
Starter and effort for keeping ITs working is distributed between committers.
> Consolidate all 'launchpad-testing' modules into a single git repository
> ------------------------------------------------------------------------
>
> Key: SLING-7935
> URL: https://issues.apache.org/jira/browse/SLING-7935
> Project: Sling
> Issue Type: Task
> Components: Launchpad
> Reporter: Robert Munteanu
> Assignee: Robert Munteanu
> Priority: Major
> Fix For: Starter 12
>
>
> We currently have seven testing-related modules in Git:
> * org-apache-sling-launchpad-integration-tests
> * org-apache-sling-launchpad-test-bundles
> * org-apache-sling-launchpad-test-fragment
> * org-apache-sling-launchpad-testing
> * org-apache-sling-launchpad-testing-war
> * org-apache-sling-launchpad-test-services
> * org-apache-sling-launchpad-test-services-war
> All of these are related to testing the starter application and typically we
> only release them when the starter is also released. As such, it's a pain to
> manually keep versions in sync and release the modules one by one. This is
> one scenario where a single git repository would make sense.
> Whether this should be the actual starter repository or a starter-testing one
> is something that is not set in stone, but the current situation is not
> optimal.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
