Lost SVN updates following conversion to Git

classic Classic list List threaded Threaded
6 messages Options
Reply | Threaded
Open this post in threaded view
|

Lost SVN updates following conversion to Git

sebb-2-2
Some updates have been made to the Commons 'proper' SVN repos since
they were converted to Git.

Such changes should not have been made, as they are not automatically
reflected in the Git repos.

I think we need to do the following:

- revert the spurious changes so SVN reflects the state at conversion
(I am working on a list of the updates that were made after conversion)

- create PRs/JIRAs for the changes that are still needed

- make it harder to accidentally update the SVN repos for Commons
proper components
The simplest way to stop further updates is probably to rename the SVN
directory from /proper to /_moved_to_git. This will still allow
updates by PMC members, but it's much more obvious that the SVN repo
should no longer be updated.

WDYT?
S.

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: Lost SVN updates following conversion to Git

Bruno P. Kinoshita-2
Sounds like a good plan to me.
+1

Sent from Yahoo Mail on Android
 
  On Sat, 25 May 2019 at 9:00, sebb<[hidden email]> wrote:   Some updates have been made to the Commons 'proper' SVN repos since
they were converted to Git.

Such changes should not have been made, as they are not automatically
reflected in the Git repos.

I think we need to do the following:

- revert the spurious changes so SVN reflects the state at conversion
(I am working on a list of the updates that were made after conversion)

- create PRs/JIRAs for the changes that are still needed

- make it harder to accidentally update the SVN repos for Commons
proper components
The simplest way to stop further updates is probably to rename the SVN
directory from /proper to /_moved_to_git. This will still allow
updates by PMC members, but it's much more obvious that the SVN repo
should no longer be updated.

WDYT?
S.

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

 
Reply | Threaded
Open this post in threaded view
|

Re: Lost SVN updates following conversion to Git

Emmanuel Bourg-3
In reply to this post by sebb-2-2
Le 24/05/2019 à 22:59, sebb a écrit :

> The simplest way to stop further updates is probably to rename the SVN
> directory from /proper to /_moved_to_git. This will still allow
> updates by PMC members, but it's much more obvious that the SVN repo
> should no longer be updated.

Couldn't we set the ACL on the /proper path to read-only instead? At
least it doesn't break the URLs pointing to the current path.

Emmanuel Bourg

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: Lost SVN updates following conversion to Git

sebb-2-2
On Fri, 24 May 2019 at 22:37, Emmanuel Bourg <[hidden email]> wrote:

>
> Le 24/05/2019 à 22:59, sebb a écrit :
>
> > The simplest way to stop further updates is probably to rename the SVN
> > directory from /proper to /_moved_to_git. This will still allow
> > updates by PMC members, but it's much more obvious that the SVN repo
> > should no longer be updated.
>
> Couldn't we set the ACL on the /proper path to read-only instead? At
> least it doesn't break the URLs pointing to the current path.

Yes, that would also be possible, but that can only be done by INFRA,
and can only be done when all the components have been fixed.
Also it might give a false impression of the state of the project.
I think it would be better to replace the tree with a readme pointing
to the new location.

> Emmanuel Bourg
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: Lost SVN updates following conversion to Git

garydgregory
I like the pointer idea.

Gary

On Fri, May 24, 2019, 18:35 sebb <[hidden email]> wrote:

> On Fri, 24 May 2019 at 22:37, Emmanuel Bourg <[hidden email]> wrote:
> >
> > Le 24/05/2019 à 22:59, sebb a écrit :
> >
> > > The simplest way to stop further updates is probably to rename the SVN
> > > directory from /proper to /_moved_to_git. This will still allow
> > > updates by PMC members, but it's much more obvious that the SVN repo
> > > should no longer be updated.
> >
> > Couldn't we set the ACL on the /proper path to read-only instead? At
> > least it doesn't break the URLs pointing to the current path.
>
> Yes, that would also be possible, but that can only be done by INFRA,
> and can only be done when all the components have been fixed.
> Also it might give a false impression of the state of the project.
> I think it would be better to replace the tree with a readme pointing
> to the new location.
>
> > Emmanuel Bourg
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [hidden email]
> > For additional commands, e-mail: [hidden email]
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>
>
Reply | Threaded
Open this post in threaded view
|

Re: Lost SVN updates following conversion to Git

sebb-2-2
On Sat, 25 May 2019 at 00:13, Gary Gregory <[hidden email]> wrote:
>
> I like the pointer idea.

This is an example of what we did for the original moves:

http://svn.apache.org/repos/asf/commons/proper/io/IoNowUsesGit.txt

> Gary
>
> On Fri, May 24, 2019, 18:35 sebb <[hidden email]> wrote:
>
> > On Fri, 24 May 2019 at 22:37, Emmanuel Bourg <[hidden email]> wrote:
> > >
> > > Le 24/05/2019 à 22:59, sebb a écrit :
> > >
> > > > The simplest way to stop further updates is probably to rename the SVN
> > > > directory from /proper to /_moved_to_git. This will still allow
> > > > updates by PMC members, but it's much more obvious that the SVN repo
> > > > should no longer be updated.
> > >
> > > Couldn't we set the ACL on the /proper path to read-only instead? At
> > > least it doesn't break the URLs pointing to the current path.
> >
> > Yes, that would also be possible, but that can only be done by INFRA,
> > and can only be done when all the components have been fixed.
> > Also it might give a false impression of the state of the project.
> > I think it would be better to replace the tree with a readme pointing
> > to the new location.
> >
> > > Emmanuel Bourg
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: [hidden email]
> > > For additional commands, e-mail: [hidden email]
> > >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [hidden email]
> > For additional commands, e-mail: [hidden email]
> >
> >

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]