Updates on SVN to GitHub migration

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

Re: [llvm-dev] [lldb-dev] Updates on SVN to GitHub migration

Don Hinton via cfe-dev
I think Anton is referring to the SVN bridge -- where Git repositories
can be accessed through the Subversion API/protocol.
On Fri, Nov 9, 2018 at 6:27 PM Jean-Daniel via cfe-dev
<[hidden email]> wrote:

>
> Isn’t the checkout a local operation that should not involved GitHub ? Did you mean the clone operation ?
>
> And about sparse-checkout, I though they require a full clone of the repository anyway. Is there a way to do a partial clone only ?
>
> Note: If you don’t need the whole history local, you may perform a swallow clone (using —depth 1).
>
> Le 9 nov. 2018 à 01:02, Anton Korobeynikov via llvm-dev <[hidden email]> a écrit :
>
> No idea, the checkout just timed out. I tried to play with sparse
> checkouts, etc. and my current hypothesis that the large number of
> revisions makes it unhappy.
> On Fri, Nov 9, 2018 at 2:39 AM James Y Knight <[hidden email]> wrote:
>
>
> It'd be nice to know what about our repository is breaking it. Do they have any idea what that is?
>
> For example -- I think that we probably will want to archive+discard many of the random branches and tags currently in the repository. If the large number of branches and tags is breaking it, then maybe it just starts working after we do so.
>
> On Thu, Nov 8, 2018 at 3:53 PM Anton Korobeynikov <[hidden email]> wrote:
>
>
> Some status update wrt GitHub SVN bridge.
>
> It does not work for any non-trivial (= LLVM) repo. I filled the issue
> there, however, there is no ETA when it will be fixed. Even worse,
> there are no promises that the issue will be addressed at all. Though
> they are aware that this is the issue for us.
> On Thu, Nov 8, 2018 at 12:53 PM Nico Weber via llvm-dev
> <[hidden email]> wrote:
>
>
> What's the status here?
>
> Can someone keep https://llvm.org/docs/Proposals/GitHubMove.html updated with the current status of things?
>
> And once things are usable, probably update https://llvm.org/docs/GettingStarted.html#for-developers-to-work-with-a-git-monorepo as well.
>
> On Wed, Oct 24, 2018 at 4:57 AM Jacob Carlborg via lldb-dev <[hidden email]> wrote:
>
>
> On 2018-10-24 08:25, Whisperity via cfe-dev wrote:
>
> They are not shown in the project graph, but if you open the "branch"
> drop down it has a tab named 'Tags'.
>
>
> It shows some tags there, but not all of them. But clicking "releases"
> then "Tags" will show this page [1], which seems to include all of them.
>
> [1] https://github.com/llvm-git-prototype/llvm/tags
>
> --
> /Jacob Carlborg
>
> _______________________________________________
> lldb-dev mailing list
> [hidden email]
> http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
>
>
> _______________________________________________
> LLVM Developers mailing list
> [hidden email]
> http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev
>
>
>
>
> --
> With best regards, Anton Korobeynikov
> Department of Statistical Modelling, Saint Petersburg State University
>
>
>
>
> --
> With best regards, Anton Korobeynikov
> Department of Statistical Modelling, Saint Petersburg State University
> _______________________________________________
> LLVM Developers mailing list
> [hidden email]
> http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev
>
>
> _______________________________________________
> cfe-dev mailing list
> [hidden email]
> http://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev



--
Dean
_______________________________________________
cfe-dev mailing list
[hidden email]
http://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev
Reply | Threaded
Open this post in threaded view
|

Re: [llvm-dev] [lldb-dev] Updates on SVN to GitHub migration

Don Hinton via cfe-dev
Correct. One important part of the migration is the ability to keep
the various CIs and other integrations intact via switching to
svn-from-git bridge:
https://help.github.com/articles/support-for-subversion-clients/

Otherwise the things might be even more complicated for downstream users.
On Fri, Nov 9, 2018 at 10:56 AM Dean Michael Berris
<[hidden email]> wrote:

>
> I think Anton is referring to the SVN bridge -- where Git repositories
> can be accessed through the Subversion API/protocol.
> On Fri, Nov 9, 2018 at 6:27 PM Jean-Daniel via cfe-dev
> <[hidden email]> wrote:
> >
> > Isn’t the checkout a local operation that should not involved GitHub ? Did you mean the clone operation ?
> >
> > And about sparse-checkout, I though they require a full clone of the repository anyway. Is there a way to do a partial clone only ?
> >
> > Note: If you don’t need the whole history local, you may perform a swallow clone (using —depth 1).
> >
> > Le 9 nov. 2018 à 01:02, Anton Korobeynikov via llvm-dev <[hidden email]> a écrit :
> >
> > No idea, the checkout just timed out. I tried to play with sparse
> > checkouts, etc. and my current hypothesis that the large number of
> > revisions makes it unhappy.
> > On Fri, Nov 9, 2018 at 2:39 AM James Y Knight <[hidden email]> wrote:
> >
> >
> > It'd be nice to know what about our repository is breaking it. Do they have any idea what that is?
> >
> > For example -- I think that we probably will want to archive+discard many of the random branches and tags currently in the repository. If the large number of branches and tags is breaking it, then maybe it just starts working after we do so.
> >
> > On Thu, Nov 8, 2018 at 3:53 PM Anton Korobeynikov <[hidden email]> wrote:
> >
> >
> > Some status update wrt GitHub SVN bridge.
> >
> > It does not work for any non-trivial (= LLVM) repo. I filled the issue
> > there, however, there is no ETA when it will be fixed. Even worse,
> > there are no promises that the issue will be addressed at all. Though
> > they are aware that this is the issue for us.
> > On Thu, Nov 8, 2018 at 12:53 PM Nico Weber via llvm-dev
> > <[hidden email]> wrote:
> >
> >
> > What's the status here?
> >
> > Can someone keep https://llvm.org/docs/Proposals/GitHubMove.html updated with the current status of things?
> >
> > And once things are usable, probably update https://llvm.org/docs/GettingStarted.html#for-developers-to-work-with-a-git-monorepo as well.
> >
> > On Wed, Oct 24, 2018 at 4:57 AM Jacob Carlborg via lldb-dev <[hidden email]> wrote:
> >
> >
> > On 2018-10-24 08:25, Whisperity via cfe-dev wrote:
> >
> > They are not shown in the project graph, but if you open the "branch"
> > drop down it has a tab named 'Tags'.
> >
> >
> > It shows some tags there, but not all of them. But clicking "releases"
> > then "Tags" will show this page [1], which seems to include all of them.
> >
> > [1] https://github.com/llvm-git-prototype/llvm/tags
> >
> > --
> > /Jacob Carlborg
> >
> > _______________________________________________
> > lldb-dev mailing list
> > [hidden email]
> > http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
> >
> >
> > _______________________________________________
> > LLVM Developers mailing list
> > [hidden email]
> > http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev
> >
> >
> >
> >
> > --
> > With best regards, Anton Korobeynikov
> > Department of Statistical Modelling, Saint Petersburg State University
> >
> >
> >
> >
> > --
> > With best regards, Anton Korobeynikov
> > Department of Statistical Modelling, Saint Petersburg State University
> > _______________________________________________
> > LLVM Developers mailing list
> > [hidden email]
> > http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev
> >
> >
> > _______________________________________________
> > cfe-dev mailing list
> > [hidden email]
> > http://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev
>
>
>
> --
> Dean



--
With best regards, Anton Korobeynikov
Department of Statistical Modelling, Saint Petersburg State University
_______________________________________________
cfe-dev mailing list
[hidden email]
http://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev
Reply | Threaded
Open this post in threaded view
|

Re: [llvm-dev] [lldb-dev] Updates on SVN to GitHub migration

Don Hinton via cfe-dev


Le ven. 9 nov. 2018 à 01:33, Anton Korobeynikov via llvm-dev <[hidden email]> a écrit :
Correct. One important part of the migration is the ability to keep
the various CIs and other integrations intact via switching to
svn-from-git bridge:
https://help.github.com/articles/support-for-subversion-clients/

I am not convinced that it was seriously considered to preserve CI on SVN using the bridge, at least this is the first time I hear about this.
AFAIK, the transition plan is that bot owners have one year to switch from polling from SVN to using Git.

When I looked at the bridge, it was only in the context of individual developers who who try to work on a very small subset of the repo. To be honest, I have a hard time imagining anyone really preferring this over git though.

Note when I tried on the monorepo originally, it didn't work (always timed-out) and I exchanged with GitHub support about it. They did something on the repo I had push to my account and then it was working OK (I only did very basic testing).

-- 
Mehdi




Otherwise the things might be even more complicated for downstream users.
On Fri, Nov 9, 2018 at 10:56 AM Dean Michael Berris
<[hidden email]> wrote:
>
> I think Anton is referring to the SVN bridge -- where Git repositories
> can be accessed through the Subversion API/protocol.
> On Fri, Nov 9, 2018 at 6:27 PM Jean-Daniel via cfe-dev
> <[hidden email]> wrote:
> >
> > Isn’t the checkout a local operation that should not involved GitHub ? Did you mean the clone operation ?
> >
> > And about sparse-checkout, I though they require a full clone of the repository anyway. Is there a way to do a partial clone only ?
> >
> > Note: If you don’t need the whole history local, you may perform a swallow clone (using —depth 1).
> >
> > Le 9 nov. 2018 à 01:02, Anton Korobeynikov via llvm-dev <[hidden email]> a écrit :
> >
> > No idea, the checkout just timed out. I tried to play with sparse
> > checkouts, etc. and my current hypothesis that the large number of
> > revisions makes it unhappy.
> > On Fri, Nov 9, 2018 at 2:39 AM James Y Knight <[hidden email]> wrote:
> >
> >
> > It'd be nice to know what about our repository is breaking it. Do they have any idea what that is?
> >
> > For example -- I think that we probably will want to archive+discard many of the random branches and tags currently in the repository. If the large number of branches and tags is breaking it, then maybe it just starts working after we do so.
> >
> > On Thu, Nov 8, 2018 at 3:53 PM Anton Korobeynikov <[hidden email]> wrote:
> >
> >
> > Some status update wrt GitHub SVN bridge.
> >
> > It does not work for any non-trivial (= LLVM) repo. I filled the issue
> > there, however, there is no ETA when it will be fixed. Even worse,
> > there are no promises that the issue will be addressed at all. Though
> > they are aware that this is the issue for us.
> > On Thu, Nov 8, 2018 at 12:53 PM Nico Weber via llvm-dev
> > <[hidden email]> wrote:
> >
> >
> > What's the status here?
> >
> > Can someone keep https://llvm.org/docs/Proposals/GitHubMove.html updated with the current status of things?
> >
> > And once things are usable, probably update https://llvm.org/docs/GettingStarted.html#for-developers-to-work-with-a-git-monorepo as well.
> >
> > On Wed, Oct 24, 2018 at 4:57 AM Jacob Carlborg via lldb-dev <[hidden email]> wrote:
> >
> >
> > On 2018-10-24 08:25, Whisperity via cfe-dev wrote:
> >
> > They are not shown in the project graph, but if you open the "branch"
> > drop down it has a tab named 'Tags'.
> >
> >
> > It shows some tags there, but not all of them. But clicking "releases"
> > then "Tags" will show this page [1], which seems to include all of them.
> >
> > [1] https://github.com/llvm-git-prototype/llvm/tags
> >
> > --
> > /Jacob Carlborg
> >
> > _______________________________________________
> > lldb-dev mailing list
> > [hidden email]
> > http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
> >
> >
> > _______________________________________________
> > LLVM Developers mailing list
> > [hidden email]
> > http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev
> >
> >
> >
> >
> > --
> > With best regards, Anton Korobeynikov
> > Department of Statistical Modelling, Saint Petersburg State University
> >
> >
> >
> >
> > --
> > With best regards, Anton Korobeynikov
> > Department of Statistical Modelling, Saint Petersburg State University
> > _______________________________________________
> > LLVM Developers mailing list
> > [hidden email]
> > http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev
> >
> >
> > _______________________________________________
> > cfe-dev mailing list
> > [hidden email]
> > http://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev
>
>
>
> --
> Dean



--
With best regards, Anton Korobeynikov
Department of Statistical Modelling, Saint Petersburg State University
_______________________________________________
LLVM Developers mailing list
[hidden email]
http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev


_______________________________________________
cfe-dev mailing list
[hidden email]
http://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev
Reply | Threaded
Open this post in threaded view
|

Re: [llvm-dev] Updates on SVN to GitHub migration

Don Hinton via cfe-dev
In reply to this post by Don Hinton via cfe-dev
Here's another question about the current status of this. It's close to two months after the official monorepo was supposed to be published. Can someone give an update? Is this on hold indefinitely? Are there concrete issues that people are working on and this will happen as soon as those are resolved?

At the least, I'm assuming the "SVN will shut down 1 year from now" refers to 1 year from when the monorepo actually gets published, not 1 year relative to when the initial mail got sent?

Someone mentioned an issue with github's svn bridge, but it wasn't clear if that's blocking, and if it is if there's a plan for it.

Thanks
Nico

On Sat, Oct 20, 2018 at 4:10 AM Jonas Hahnfeld via cfe-dev <[hidden email]> wrote:
(+openmp-dev, they should know about this!)

Recapping the "Concerns"
(https://llvm.org/docs/Proposals/GitHubMove.html#id12) there is a
proposal of "single-subproject Git mirrors" for people who are only
contributing to standalone subprojects. I think this will be easy in the
transition period, we can just continue to move the current official git
mirrors. Will this "service" be continued after GitHub becomes the 'one
source of truth'? I'd strongly vote for yes, but I'm not sure how that's
going to work on a technical level.

Thanks,
Jonas

On 2018-10-20 03:14, Tom Stellard via llvm-dev wrote:
> On 10/19/2018 05:47 PM, Tom Stellard via lldb-dev wrote:
>> TLDR: Official monorepo repository will be published on
>> Tuesday, Oct 23, 2018.  After this date, you should modify
>> your workflows to use the monorepo ASAP.  Current workflows
>> will be supported for at most 1 more year.
>>
>> Hi,
>>
>> We had 2 round-tables this week at the Developer Meeting to
>> discuss the SVN to GitHub migration, and I wanted to update
>> the rest of the community on what we discussed.
>>
>> The most important outcome from that meeting is that we
>> now have a timeline for completing the transition which looks
>> like this:
>>
>
> Step 1:
>> Tues Oct 23, 2018:
>>
>> The latest monorepo prototype[1] will be moved over to the LLVM
>> organization github project[2] and will begin mirroring the current
>> SVN repository.  Commits will still be made to the SVN repository
>> just as they are today.
>>
>> All community members should begin migrating their workflows that
>> rely on SVN or the current git mirrors to use the new monorepo.
>>
>> For CI jobs or internal mirrors pulling from SVN or
>> http://llvm.org/git/*.git you should modify them to pull from
>> the new monorepo and also to deal with the new repository
>> layout.
>>
>> For Developers, you should begin using the new monorepo
>> for your development and using the provided scripts[3]
>> to commit your code.  These scripts will allow to commit
>> to SVN from the monorepo without using git-svn
>>
>>
>
> Sorry hit send before I was done.  Here is the rest of the mail:
>
> Step 2:
>
> Around the time of next year's developer meeting (1 year at the most),
> we will turn off commit access to the SVN server and enable commit
> access to the monorepo.  At this point the monorepo will become the
> 'one source of truth' for the project.  Community members *must* have
> updated their workflows by this date and are encouraged to begin
> updating workflows ASAP.
>
> A lot of people asked at the developer meeting about the future
> of bugzilla and phabricator and whether or not we will use
> github issues and pull requests.  These are important questions,
> but are unrelated to the migration of the code.
>
> We also came up with a TODO list for things we want to accomplish
> as a community in the next year and beyond related to github.  I
> am working on putting these into bugzilla so we can track progress
> better and I will send a follow-up email about this.
>
> -Tom
>
>>
>>
>>
>>
>> [1] https://github.com/llvm-git-prototype/llvm
>> [2] https://github.com/llvm/
>> [3]
>> https://llvm.org/docs/GettingStarted.html#for-developers-to-work-with-a-git-monorepo
>>
>>
>> _______________________________________________
>> lldb-dev mailing list
>> [hidden email]
>> http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
>>
>
> _______________________________________________
> LLVM Developers mailing list
> [hidden email]
> http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev
_______________________________________________
cfe-dev mailing list
[hidden email]
http://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev

_______________________________________________
cfe-dev mailing list
[hidden email]
http://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev
Reply | Threaded
Open this post in threaded view
|

Re: [llvm-dev] Updates on SVN to GitHub migration

Don Hinton via cfe-dev
On 12/10/2018 10:38 AM, Nico Weber wrote:
> Here's another question about the current status of this. It's close to two months after the official monorepo was supposed to be published. Can someone give an update? Is this on hold indefinitely? Are there concrete issues that people are working on and this will happen as soon as those are resolved?
>

There were some issues raised in the thread on llvm-dev:
"Dealing with out of tree changes and the LLVM git monorepo"  This migration
has been delayed while discussing these issues.  Discussion on that
thread has died down and it seems like the consensus is to move forward with
the original plan, but we are waiting to get some formal closure on that thread.

> At the least, I'm assuming the "SVN will shut down 1 year from now" refers to 1 year from when the monorepo actually gets published, not 1 year relative to when the initial mail got sent?
>

The deadline for SVN shutdown remains unchanged.  It's still going to be
around the 2019 LLVM Developers meeting.

> Someone mentioned an issue with github's svn bridge, but it wasn't clear if that's blocking, and if it is if there's a plan for it.
>

It's not a blocking issue and there haven't been any updates lately,
you can follow status on this bug:
https://bugs.llvm.org/show_bug.cgi?id=39396

-Tom

> Thanks
> Nico
>
> On Sat, Oct 20, 2018 at 4:10 AM Jonas Hahnfeld via cfe-dev <[hidden email] <mailto:[hidden email]>> wrote:
>
>     (+openmp-dev, they should know about this!)
>
>     Recapping the "Concerns"
>     (https://llvm.org/docs/Proposals/GitHubMove.html#id12) there is a
>     proposal of "single-subproject Git mirrors" for people who are only
>     contributing to standalone subprojects. I think this will be easy in the
>     transition period, we can just continue to move the current official git
>     mirrors. Will this "service" be continued after GitHub becomes the 'one
>     source of truth'? I'd strongly vote for yes, but I'm not sure how that's
>     going to work on a technical level.
>
>     Thanks,
>     Jonas
>
>     On 2018-10-20 03:14, Tom Stellard via llvm-dev wrote:
>     > On 10/19/2018 05:47 PM, Tom Stellard via lldb-dev wrote:
>     >> TLDR: Official monorepo repository will be published on
>     >> Tuesday, Oct 23, 2018.  After this date, you should modify
>     >> your workflows to use the monorepo ASAP.  Current workflows
>     >> will be supported for at most 1 more year.
>     >>
>     >> Hi,
>     >>
>     >> We had 2 round-tables this week at the Developer Meeting to
>     >> discuss the SVN to GitHub migration, and I wanted to update
>     >> the rest of the community on what we discussed.
>     >>
>     >> The most important outcome from that meeting is that we
>     >> now have a timeline for completing the transition which looks
>     >> like this:
>     >>
>     >
>     > Step 1:
>     >> Tues Oct 23, 2018:
>     >>
>     >> The latest monorepo prototype[1] will be moved over to the LLVM
>     >> organization github project[2] and will begin mirroring the current
>     >> SVN repository.  Commits will still be made to the SVN repository
>     >> just as they are today.
>     >>
>     >> All community members should begin migrating their workflows that
>     >> rely on SVN or the current git mirrors to use the new monorepo.
>     >>
>     >> For CI jobs or internal mirrors pulling from SVN or
>     >> http://llvm.org/git/*.git you should modify them to pull from
>     >> the new monorepo and also to deal with the new repository
>     >> layout.
>     >>
>     >> For Developers, you should begin using the new monorepo
>     >> for your development and using the provided scripts[3]
>     >> to commit your code.  These scripts will allow to commit
>     >> to SVN from the monorepo without using git-svn
>     >>
>     >>
>     >
>     > Sorry hit send before I was done.  Here is the rest of the mail:
>     >
>     > Step 2:
>     >
>     > Around the time of next year's developer meeting (1 year at the most),
>     > we will turn off commit access to the SVN server and enable commit
>     > access to the monorepo.  At this point the monorepo will become the
>     > 'one source of truth' for the project.  Community members *must* have
>     > updated their workflows by this date and are encouraged to begin
>     > updating workflows ASAP.
>     >
>     > A lot of people asked at the developer meeting about the future
>     > of bugzilla and phabricator and whether or not we will use
>     > github issues and pull requests.  These are important questions,
>     > but are unrelated to the migration of the code.
>     >
>     > We also came up with a TODO list for things we want to accomplish
>     > as a community in the next year and beyond related to github.  I
>     > am working on putting these into bugzilla so we can track progress
>     > better and I will send a follow-up email about this.
>     >
>     > -Tom
>     >
>     >>
>     >>
>     >>
>     >>
>     >> [1] https://github.com/llvm-git-prototype/llvm
>     >> [2] https://github.com/llvm/
>     >> [3]
>     >> https://llvm.org/docs/GettingStarted.html#for-developers-to-work-with-a-git-monorepo
>     >>
>     >>
>     >> _______________________________________________
>     >> lldb-dev mailing list
>     >> [hidden email] <mailto:[hidden email]>
>     >> http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
>     >>
>     >
>     > _______________________________________________
>     > LLVM Developers mailing list
>     > [hidden email] <mailto:[hidden email]>
>     > http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev
>     _______________________________________________
>     cfe-dev mailing list
>     [hidden email] <mailto:[hidden email]>
>     http://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev
>

_______________________________________________
cfe-dev mailing list
[hidden email]
http://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev
Reply | Threaded
Open this post in threaded view
|

Re: [llvm-dev] Updates on SVN to GitHub migration

Don Hinton via cfe-dev
Thanks for the update!

On Mon, Dec 10, 2018 at 1:55 PM Tom Stellard <[hidden email]> wrote:
On 12/10/2018 10:38 AM, Nico Weber wrote:
> Here's another question about the current status of this. It's close to two months after the official monorepo was supposed to be published. Can someone give an update? Is this on hold indefinitely? Are there concrete issues that people are working on and this will happen as soon as those are resolved?
>

There were some issues raised in the thread on llvm-dev:
"Dealing with out of tree changes and the LLVM  git monorepo"  This migration
has been delayed while discussing these issues.  Discussion on that
thread has died down and it seems like the consensus is to move forward with
the original plan, but we are waiting to get some formal closure on that thread.

> At the least, I'm assuming the "SVN will shut down 1 year from now" refers to 1 year from when the monorepo actually gets published, not 1 year relative to when the initial mail got sent?
>

The deadline for SVN shutdown remains unchanged.  It's still going to be
around the 2019 LLVM Developers meeting.

> Someone mentioned an issue with github's svn bridge, but it wasn't clear if that's blocking, and if it is if there's a plan for it.
>

It's not a blocking issue and there haven't been any updates lately,
you can follow status on this bug:
https://bugs.llvm.org/show_bug.cgi?id=39396

-Tom

> Thanks
> Nico
>
> On Sat, Oct 20, 2018 at 4:10 AM Jonas Hahnfeld via cfe-dev <[hidden email] <mailto:[hidden email]>> wrote:
>
>     (+openmp-dev, they should know about this!)
>
>     Recapping the "Concerns"
>     (https://llvm.org/docs/Proposals/GitHubMove.html#id12) there is a
>     proposal of "single-subproject Git mirrors" for people who are only
>     contributing to standalone subprojects. I think this will be easy in the
>     transition period, we can just continue to move the current official git
>     mirrors. Will this "service" be continued after GitHub becomes the 'one
>     source of truth'? I'd strongly vote for yes, but I'm not sure how that's
>     going to work on a technical level.
>
>     Thanks,
>     Jonas
>
>     On 2018-10-20 03:14, Tom Stellard via llvm-dev wrote:
>     > On 10/19/2018 05:47 PM, Tom Stellard via lldb-dev wrote:
>     >> TLDR: Official monorepo repository will be published on
>     >> Tuesday, Oct 23, 2018.  After this date, you should modify
>     >> your workflows to use the monorepo ASAP.  Current workflows
>     >> will be supported for at most 1 more year.
>     >>
>     >> Hi,
>     >>
>     >> We had 2 round-tables this week at the Developer Meeting to
>     >> discuss the SVN to GitHub migration, and I wanted to update
>     >> the rest of the community on what we discussed.
>     >>
>     >> The most important outcome from that meeting is that we
>     >> now have a timeline for completing the transition which looks
>     >> like this:
>     >>
>     >
>     > Step 1:
>     >> Tues Oct 23, 2018:
>     >>
>     >> The latest monorepo prototype[1] will be moved over to the LLVM
>     >> organization github project[2] and will begin mirroring the current
>     >> SVN repository.  Commits will still be made to the SVN repository
>     >> just as they are today.
>     >>
>     >> All community members should begin migrating their workflows that
>     >> rely on SVN or the current git mirrors to use the new monorepo.
>     >>
>     >> For CI jobs or internal mirrors pulling from SVN or
>     >> http://llvm.org/git/*.git you should modify them to pull from
>     >> the new monorepo and also to deal with the new repository
>     >> layout.
>     >>
>     >> For Developers, you should begin using the new monorepo
>     >> for your development and using the provided scripts[3]
>     >> to commit your code.  These scripts will allow to commit
>     >> to SVN from the monorepo without using git-svn
>     >>
>     >>
>     >
>     > Sorry hit send before I was done.  Here is the rest of the mail:
>     >
>     > Step 2:
>     >
>     > Around the time of next year's developer meeting (1 year at the most),
>     > we will turn off commit access to the SVN server and enable commit
>     > access to the monorepo.  At this point the monorepo will become the
>     > 'one source of truth' for the project.  Community members *must* have
>     > updated their workflows by this date and are encouraged to begin
>     > updating workflows ASAP.
>     >
>     > A lot of people asked at the developer meeting about the future
>     > of bugzilla and phabricator and whether or not we will use
>     > github issues and pull requests.  These are important questions,
>     > but are unrelated to the migration of the code.
>     >
>     > We also came up with a TODO list for things we want to accomplish
>     > as a community in the next year and beyond related to github.  I
>     > am working on putting these into bugzilla so we can track progress
>     > better and I will send a follow-up email about this.
>     >
>     > -Tom
>     >
>     >>
>     >>
>     >>
>     >>
>     >> [1] https://github.com/llvm-git-prototype/llvm
>     >> [2] https://github.com/llvm/
>     >> [3]
>     >> https://llvm.org/docs/GettingStarted.html#for-developers-to-work-with-a-git-monorepo
>     >>
>     >>
>     >> _______________________________________________
>     >> lldb-dev mailing list
>     >> [hidden email] <mailto:[hidden email]>
>     >> http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
>     >>
>     >
>     > _______________________________________________
>     > LLVM Developers mailing list
>     > [hidden email] <mailto:[hidden email]>
>     > http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev
>     _______________________________________________
>     cfe-dev mailing list
>     [hidden email] <mailto:[hidden email]>
>     http://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev
>


_______________________________________________
cfe-dev mailing list
[hidden email]
http://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev
Reply | Threaded
Open this post in threaded view
|

Re: [llvm-dev] Updates on SVN to GitHub migration

Don Hinton via cfe-dev
(I wanted to ask about another update, but it looks like there was one posted to llvm-dev today: http://lists.llvm.org/pipermail/llvm-dev/2019-January/128840.html Mentioning this for others who subscribe to cfe-dev or similar but not llvm-dev.)

On Mon, Dec 10, 2018 at 1:58 PM Nico Weber <[hidden email]> wrote:
Thanks for the update!

On Mon, Dec 10, 2018 at 1:55 PM Tom Stellard <[hidden email]> wrote:
On 12/10/2018 10:38 AM, Nico Weber wrote:
> Here's another question about the current status of this. It's close to two months after the official monorepo was supposed to be published. Can someone give an update? Is this on hold indefinitely? Are there concrete issues that people are working on and this will happen as soon as those are resolved?
>

There were some issues raised in the thread on llvm-dev:
"Dealing with out of tree changes and the LLVM  git monorepo"  This migration
has been delayed while discussing these issues.  Discussion on that
thread has died down and it seems like the consensus is to move forward with
the original plan, but we are waiting to get some formal closure on that thread.

> At the least, I'm assuming the "SVN will shut down 1 year from now" refers to 1 year from when the monorepo actually gets published, not 1 year relative to when the initial mail got sent?
>

The deadline for SVN shutdown remains unchanged.  It's still going to be
around the 2019 LLVM Developers meeting.

> Someone mentioned an issue with github's svn bridge, but it wasn't clear if that's blocking, and if it is if there's a plan for it.
>

It's not a blocking issue and there haven't been any updates lately,
you can follow status on this bug:
https://bugs.llvm.org/show_bug.cgi?id=39396

-Tom

> Thanks
> Nico
>
> On Sat, Oct 20, 2018 at 4:10 AM Jonas Hahnfeld via cfe-dev <[hidden email] <mailto:[hidden email]>> wrote:
>
>     (+openmp-dev, they should know about this!)
>
>     Recapping the "Concerns"
>     (https://llvm.org/docs/Proposals/GitHubMove.html#id12) there is a
>     proposal of "single-subproject Git mirrors" for people who are only
>     contributing to standalone subprojects. I think this will be easy in the
>     transition period, we can just continue to move the current official git
>     mirrors. Will this "service" be continued after GitHub becomes the 'one
>     source of truth'? I'd strongly vote for yes, but I'm not sure how that's
>     going to work on a technical level.
>
>     Thanks,
>     Jonas
>
>     On 2018-10-20 03:14, Tom Stellard via llvm-dev wrote:
>     > On 10/19/2018 05:47 PM, Tom Stellard via lldb-dev wrote:
>     >> TLDR: Official monorepo repository will be published on
>     >> Tuesday, Oct 23, 2018.  After this date, you should modify
>     >> your workflows to use the monorepo ASAP.  Current workflows
>     >> will be supported for at most 1 more year.
>     >>
>     >> Hi,
>     >>
>     >> We had 2 round-tables this week at the Developer Meeting to
>     >> discuss the SVN to GitHub migration, and I wanted to update
>     >> the rest of the community on what we discussed.
>     >>
>     >> The most important outcome from that meeting is that we
>     >> now have a timeline for completing the transition which looks
>     >> like this:
>     >>
>     >
>     > Step 1:
>     >> Tues Oct 23, 2018:
>     >>
>     >> The latest monorepo prototype[1] will be moved over to the LLVM
>     >> organization github project[2] and will begin mirroring the current
>     >> SVN repository.  Commits will still be made to the SVN repository
>     >> just as they are today.
>     >>
>     >> All community members should begin migrating their workflows that
>     >> rely on SVN or the current git mirrors to use the new monorepo.
>     >>
>     >> For CI jobs or internal mirrors pulling from SVN or
>     >> http://llvm.org/git/*.git you should modify them to pull from
>     >> the new monorepo and also to deal with the new repository
>     >> layout.
>     >>
>     >> For Developers, you should begin using the new monorepo
>     >> for your development and using the provided scripts[3]
>     >> to commit your code.  These scripts will allow to commit
>     >> to SVN from the monorepo without using git-svn
>     >>
>     >>
>     >
>     > Sorry hit send before I was done.  Here is the rest of the mail:
>     >
>     > Step 2:
>     >
>     > Around the time of next year's developer meeting (1 year at the most),
>     > we will turn off commit access to the SVN server and enable commit
>     > access to the monorepo.  At this point the monorepo will become the
>     > 'one source of truth' for the project.  Community members *must* have
>     > updated their workflows by this date and are encouraged to begin
>     > updating workflows ASAP.
>     >
>     > A lot of people asked at the developer meeting about the future
>     > of bugzilla and phabricator and whether or not we will use
>     > github issues and pull requests.  These are important questions,
>     > but are unrelated to the migration of the code.
>     >
>     > We also came up with a TODO list for things we want to accomplish
>     > as a community in the next year and beyond related to github.  I
>     > am working on putting these into bugzilla so we can track progress
>     > better and I will send a follow-up email about this.
>     >
>     > -Tom
>     >
>     >>
>     >>
>     >>
>     >>
>     >> [1] https://github.com/llvm-git-prototype/llvm
>     >> [2] https://github.com/llvm/
>     >> [3]
>     >> https://llvm.org/docs/GettingStarted.html#for-developers-to-work-with-a-git-monorepo
>     >>
>     >>
>     >> _______________________________________________
>     >> lldb-dev mailing list
>     >> [hidden email] <mailto:[hidden email]>
>     >> http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
>     >>
>     >
>     > _______________________________________________
>     > LLVM Developers mailing list
>     > [hidden email] <mailto:[hidden email]>
>     > http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev
>     _______________________________________________
>     cfe-dev mailing list
>     [hidden email] <mailto:[hidden email]>
>     http://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev
>


_______________________________________________
cfe-dev mailing list
[hidden email]
http://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev
12