[
https://issues.apache.org/jira/browse/SLING-7183?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Munteanu updated SLING-7183:
-----------------------------------
Description:
We had some long discussions on the dev@list ( see for instance [What to do
with
github.com/apache/sling|https://lists.apache.org/thread.html/3cd73a6b55423e07424fae54fead688e854f190ee8309257e13a1381@%3Cdev.sling.apache.org%3E]
and came to the conclusion that we can't delete the old sling github mirror.
If we do that, all links to commits and pull requests would be broken. A couple
of ideas were circulated:
- change the default branch to archived and add only a README file ( the branch
exists, but default was not changed -
https://github.com/apache/sling/tree/archived )
- delete the contents of the trunk branch and leave just a README ; also tag
the last state of trunk to keep the commits around ( this breaks links that
include 'trunk' though )
- rename the repo to sling-something-else ; git will generate redirects
For whatever we decided to do we need to decide first and then ask infra for
assistance - we can't change the git repo setup ourselves.
was:
We had some long discussions on the dev@list ( see for instance [What to do
with
github.com/apache/sling|https://lists.apache.org/thread.html/3cd73a6b55423e07424fae54fead688e854f190ee8309257e13a1381@%3Cdev.sling.apache.org%3E]
and came to the conclusion that we can't delete the old sling github mirror.
If we do that, all links to commits and pull requests would be broken. A couple
of ideas were circulated:
- change the default branch to archived and add only a README file
- delete the contents of the trunk branch and leave just a README ; also tag
the last state of trunk to keep the commits around ( this breaks links that
include 'trunk' though )
- rename the repo to sling-something-else ; git will generate redirects
> Update old 'sling' github mirror to reflect Git migration
> ---------------------------------------------------------
>
> Key: SLING-7183
> URL: https://issues.apache.org/jira/browse/SLING-7183
> Project: Sling
> Issue Type: Sub-task
> Components: Best practices
> Reporter: Robert Munteanu
>
> We had some long discussions on the dev@list ( see for instance [What to do
> with
> github.com/apache/sling|https://lists.apache.org/thread.html/3cd73a6b55423e07424fae54fead688e854f190ee8309257e13a1381@%3Cdev.sling.apache.org%3E]
> and came to the conclusion that we can't delete the old sling github mirror.
> If we do that, all links to commits and pull requests would be broken. A
> couple of ideas were circulated:
> - change the default branch to archived and add only a README file ( the
> branch exists, but default was not changed -
> https://github.com/apache/sling/tree/archived )
> - delete the contents of the trunk branch and leave just a README ; also tag
> the last state of trunk to keep the commits around ( this breaks links that
> include 'trunk' though )
> - rename the repo to sling-something-else ; git will generate redirects
> For whatever we decided to do we need to decide first and then ask infra for
> assistance - we can't change the git repo setup ourselves.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
