#138: when we switch from svn.perl.org to trac, consider using git
----------------------+-----------------------------------------------------
Reporter: Infinoid | Owner:
Type: feature | Status: new
Priority: normal | Milestone:
Component: website | Version:
Severity: medium | Keywords: git svn trac plugin
Lang: | Patch:
Platform: |
----------------------+-----------------------------------------------------
Comment(by Infinoid):
Replying to [comment:1 jkeenan]:
> On the other hand, count me opposed. We have had quite a few changes in
our infrastructure lately, forcing all of our developers to spend time
learning new tools. If git users can access our SVN repository, great.
But I oppose yet another version control system change just because git is
the shiny new toy.
Obviously my vote is +1 (otherwise I wouldn't have posted the ticket), but
not because it's the shiny new toy. I would like to see git on the server
side, because it will ease branch merges. Yes, svn 1.5 has improved this
somewhat, but we still run into problems (the recent "bcanno" branch merge
is one example I'm familiar with), and going through git-svn severely
limits how much it can help with that situation.
If possible, I'd like to see some kind of bidirectional gateway in place,
so that svn users can continue using svn without having to care. But I am
specifically requesting that git be used as the backend storage system,
independent of whatever user interface(s) are available to stick in front
of it.
--
Ticket URL: <https://trac.parrot.org/parrot/ticket/138#comment:2>
Parrot <https://trac.parrot.org/parrot/>
Parrot Development
_______________________________________________
parrot-tickets mailing list
[email protected]
http://lists.parrot.org/mailman/listinfo/parrot-tickets
