infra-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (INFRA-16930) After migration to Git, still need write access to some SVN repositories
Date Tue, 21 Aug 2018 05:37:00 GMT

    [ https://issues.apache.org/jira/browse/INFRA-16930?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16586959#comment-16586959
] 

ASF subversion and git services commented on INFRA-16930:
---------------------------------------------------------

Commit f9aa5cff1f37e10c75e32d1617e45d03685affc2 in infrastructure-puppet's branch refs/heads/deployment
from [~cml]
[ https://gitbox.apache.org/repos/asf?p=infrastructure-puppet.git;h=f9aa5cf ]

INFRA-16930

per chair, return r/w access to /sis repos. access limited to PMC


> After migration to Git, still need write access to some SVN repositories
> ------------------------------------------------------------------------
>
>                 Key: INFRA-16930
>                 URL: https://issues.apache.org/jira/browse/INFRA-16930
>             Project: Infrastructure
>          Issue Type: Task
>          Components: Subversion
>            Reporter: Martin Desruisseaux
>            Assignee: Chris Lambertus
>            Priority: Major
>              Labels: pull-request-available
>
> INFRA-16577 migrated the SVN repository of Apache SIS to gitbox (thanks!). Following
this migration, most repositories in https://svn.apache.org/repos/asf/sis/ have been made
read only. However we still need write access to the following repositories:
> * https://svn.apache.org/repos/asf/sis/data/
> * https://svn.apache.org/repos/asf/sis/ip-review/
> * https://svn.apache.org/repos/asf/sis/presentations/
> * https://svn.apache.org/repos/asf/sis/release-test/
> * https://svn.apache.org/repos/asf/sis/site/
> (actually everything except trunk, branches and tags).
> In addition, if this is acceptable regarding ASF policies, we could like temporary write
access to trunk, branches and tags for replacing the files by a README pointing to SVN history.
More details on the proposed cleanup, together with a link on the discussion on the mailing
list, is there:
> https://issues.apache.org/jira/browse/SIS-422?focusedCommentId=16529821&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-16529821



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

Mime
View raw message