[llvm-dev] New LLVM git repository conversion prototype

[Andrew Kelley via llvm-dev]

If we're reasonably confident that we would like to be using GitHub Issues
in the future, I think it would not be so bad to continue using Bugzilla
for the old reports, but have new bug reports disabled, with the
understanding that it is deprecated. It's messy, sure, but at the end of
the day, you're either getting an email from Bugzilla or from GitHub and
it's not all that important. In practice, after about one release cycle,
most of the activity would take place in the new system.

I take this approach in my code - refactoring and new/better patterns don't
have to be introduced all at once; there can be a gradual transition.

On Fri, Oct 12, 2018 at 12:35 PM Renato Golin <renato.golin at linaro.org>
wrote:

> On Fri, 12 Oct 2018 at 17:05, Andrew Kelley via llvm-dev
> <llvm-dev at lists.llvm.org> wrote:
> > I ask this earnestly, not as a disagreement -
> > Would the ~11,600 open bug reports get migrated, with the CC email lists
> preserved?
>
> (same as you, not against, just opining).
>
> This is the big question, and why originally we decided not to look
> into it until the repo migration was well over.
>
> Just moving the comments seem a bit pointless... Especially when not
> everyone that used out bugzilla for the past 10+ years has a Github
> account, or with the same email.
>
> Furthermore...
>  * Do we upload all attachments? Does Github want to have all that
> history? Do we?
>  * Do we migrate the emails? People have to register on bugzilla, so
> we'd need to find all their accounts on github?
>  * Do we create tags for all categories, new, old, deprecated? Do we
> map old into new?
>  * Do we move all SVN commit references to Git hashes from GitHub
> repositories?
>
> I'm sure there are a number of other questions that, adding to James'
> list, will be impossible to disentangle before 2050.
>
> I'll be very sad is 2020 passes and we're still using SVN... :(
>
> --renato
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20181012/49d8496c/attachment.html>