On Tuesday 07 June 2016 15:10 Benedikt Ritter wrote:
> Hello Andrey,
> 
> right now I think it would be better to focus on the next release and do
> the migration afterwards.

My point was: I'm willing to help as far as I can (we need a solid BCEL release 
for FindBugs), but I'm not willing to use SVN. It is stone age.
It just incredible waste of my/others time, and none of us has lot of free time.
The SVN history, branching, *everything* feels so slow/not usable after working 
with Mercurial or Git, that it just wondered if it is time to switch.

But sure, if it is not an easy task, please focus resources on release.

> Benedikt
> 
> Andrey Loskutov <losku...@gmx.de> schrieb am Di., 7. Juni 2016 um 10:40 Uhr:
> 
> > Hi all,
> >
> > I'm not a BCEL developer, just a user, but may I trigger a discussion to
> > move BCEL development from SVN to Git?
> > I see there is already a Github mirror, so may be it is not that
> > complicated?
> >
> > The main resson is to simplify contributions. I've made few smaller
> > commits on BCEL trunk via Git clone (see [1]) but because I do not have
> > commit rights in SVN I'm forced to create patches. This is very cumbersome.
> > Given that there aren't much contributors, we schould lower the barrier for
> > new people, and having a possibility to create and manage Git pull requests
> > is definitely a time saver, not mentioning here all other benefits Git
> > offers over SVN.
> >
> > Comments?
> >
> > [1] https://github.com/iloveeclipse/commons-bcel/commits/trunk
> > --
> > Kind regards,
> > Andrey Loskutov
> >
> > http://google.com/+AndreyLoskutov
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> > For additional commands, e-mail: dev-h...@commons.apache.org
> >
> >

-- 
Kind regards,
google.com/+AndreyLoskutov

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org

Reply via email to