[llvm-dev] [cfe-dev] Updates on SVN to GitHub migration
Tom Stellard via llvm-dev
llvm-dev at lists.llvm.org
Mon Dec 10 10:55:50 PST 2018
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:
> On Sat, Oct 20, 2018 at 4:10 AM Jonas Hahnfeld via cfe-dev <cfe-dev at lists.llvm.org <mailto:cfe-dev at lists.llvm.org>> 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.
> 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 will be moved over to the LLVM
> >> organization github project 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
> >> 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
> >>  https://github.com/llvm-git-prototype/llvm
> >>  https://github.com/llvm/
> >> 
> >> https://llvm.org/docs/GettingStarted.html#for-developers-to-work-with-a-git-monorepo
> >> _______________________________________________
> >> lldb-dev mailing list
> >> lldb-dev at lists.llvm.org <mailto:lldb-dev at lists.llvm.org>
> >> http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
> > _______________________________________________
> > LLVM Developers mailing list
> > llvm-dev at lists.llvm.org <mailto:llvm-dev at lists.llvm.org>
> > http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev
> cfe-dev mailing list
> cfe-dev at lists.llvm.org <mailto:cfe-dev at lists.llvm.org>
More information about the llvm-dev