On Mon, 2017-10-23 at 23:38 +0200, Robert Munteanu wrote: > On Mon, 2017-10-23 at 18:40 +0100, Ian Boston wrote: > > > So that would mean that all link to trunk would result in a 404 > > > Not > > > Found, as I have tried it with [1]. > > > So we either > > > a) break all links to the 'trunk' branch, or > > > b) leave the 'trunk' branch alive, with the added disadvantage > > > that > > > navigating from a 'trunk' link leaves the impression that the > > > branch/repo are still in use. > > > Did I get this right or is there something else? > > > > yes. a) isnt very friendly. > > > > If we choose b) we could rename the repository to sling-svn-ending- > > 2017-10 > > or something like that. GitHub will redirect all traffic. > > > > https://help.github.com/articles/renaming-a-repository/ > > That's pretty cool. I would assume that we won't be able to reclaim > the > old 'sling' name, otherwise the redirects would not work, but this > should make it even clearer. > > Robert
I tried to summarize the current discussion at https://issues.apache.org/jira/browse/SLING-7183 I won't be able to look into this for the next two weeks, so if anyone has the time to push this to its conclusion, feel free to do so. Thanks, Robert
