infra-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Greg Stein (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (INFRA-16104) Remove tags from Subversion repository
Date Mon, 26 Feb 2018 22:34:00 GMT

     [ https://issues.apache.org/jira/browse/INFRA-16104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Greg Stein updated INFRA-16104:
-------------------------------
    Status: Waiting for Infra  (was: Closed)

Alrighty. My concern here is "make work" for the Infra team that doesn't really accomplish
anything useful. But it seems your PMC feels otherwise, and I've figured out a middle ground.

Provide one user ID, and we'll give *that* person write access to the svn repository. That
person can perform any necessary cleanup or other actions as necessary on the historical svn
repository.

(having just one person is safer against accidental changes, relative to (say) providing the
whole PMC with write access; two or three IDs is the same amount of work for us, as adding
one; talk amongst yourselves)

> Remove tags from Subversion repository
> --------------------------------------
>
>                 Key: INFRA-16104
>                 URL: https://issues.apache.org/jira/browse/INFRA-16104
>             Project: Infrastructure
>          Issue Type: Task
>          Components: Subversion
>            Reporter: Oliver Lietz
>            Priority: Minor
>
> Following tags should be removed from [Subversion repository|https://svn.apache.org/repos/asf/sling/tags/]
(read-only), see SLING-7486:
> * org.apache.sling.bgservlets-1.0.0
> * org.apache.sling.bgservlets-1.0.2
> * org.apache.sling.commons.johnzon-1.0.2
> * org.apache.sling.commons.metrics-0.0.2
> * org.apache.sling.crankstart.api.fragment-1.0.0
> * org.apache.sling.discovery.base-2.0.2
> * org.apache.sling.discovery.commons-1.0.14
> * org.apache.sling.discovery.commons-1.0.22
> * org.apache.sling.discovery.oak-1.2.12
> * org.apache.sling.event-3.3.8
> * org.apache.sling.fsresource-1.2.0
> * org.apache.sling.hc.core-1.0.0
> * org.apache.sling.hc.core-1.0.2
> * org.apache.sling.i18n-2.3.0
> * org.apache.sling.i18n-2.4.0
> * org.apache.sling.installer.factory.configuration-1.0.6
> * org.apache.sling.jcr.base-2.0.8
> * org.apache.sling.jcr.oak.server-1.1.2
> * org.apache.sling.jcr.resource-2.4.0
> * org.apache.sling.junit.healthcheck-1.0.4
> * org.apache.sling.launchpad.test-services-2.0.4-incubator
> * org.apache.sling.launchpad.testing-6
> * org.apache.sling.launchpad.testing-war-6
> * org.apache.sling.performance.base-0.0.2
> * org.apache.sling.resourcemerger-1.2.2
> * org.apache.sling.resourceresolver-1.4.6
> * org.apache.sling.scripting.core-2.0.12
> * org.apache.sling.scripting.java-2.0.8
> * org.apache.sling.scripting.jsp-2.1.2
> * org.apache.sling.scripting.jsp.taglib-2.1.4
> * org.apache.sling.scripting.velocity-2.0.0
> * org.apache.sling.testing.tools-1.0.4
> * org.apache.sling.validation.reactor-1.0.0
> * sling-6-source-release
> * sling-archetype-parent-2
> * sling-archetype-parent-3
> * sling-initial-content-archetype-1.0.2



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message