Den Wed, 21 Aug 2013 20:40:40 -0400
skrev Re: [pocl-devel] git?:

> On 2013-08-21, at 16:54 , Pekka Jääskeläinen
> <[email protected]> wrote:


> > Questions it boils down to:
> > 
> > 0) Should we move to git? From the previous discussions, I guess
> > the other active developers (who are affected mostly by the
> > transition) clearly vote for yes and I do not object.
> 
> Yes. Yes! Yes please!

Seems we have three ays, and two abstains, then :)

I have no preference between these two. Bzr has those nice running
numbers, but I am more familiar with git, so it evens out.

The only thing I have an objection against is pointless extra work. But
if the switch has some benefit for some, then the work is not exactly
pointless. And then we have a pretty good idea of who might volunteer to
do it ;) 


> > 1) Where to move the repository? It should have good issue/bug
> > tracking too. Is GitHub the best? The most active developers should
> > have the choice. I do not have an opinion on this.
> 
> GitHub is fine. Personally, I prefer BitBucket.

We already are hosted on sourceforge for wiki and maillist, but the
weight of that is pretty minor.

The minimum requirements for the hosting is the possibility of private
forks of the project for merge/pull requests (github, bb and lp all
have adequate functionality here), and a working bug tracker (which I
guess all the sites have).

Then there is the social aspect. Quite often when trying out new stuff
one finds something small to fix. The barrier to send in that fix is
considerably lower, when you already have an account on that site. So
which site is largest?

And finally. Commit hooks. For the buildbot. I might actually change my
vote to a weak 'yes' for the transition for this feature (that
I never found in launchpad) alone :) 

Eric, what makes BitBucket your preference?

> 
> Doesn't LaunchPad support git as well? However, I find its user
> interface confusing, and much prefer BitBucket (or GitHub).
> 
> > 2) How is the transition done? bzr-git can be used to preserve
> > version history? What about the bugs? Just move open ones manually
> > and leave the closed ones be?
> 
> Yes, version history should be preserved. Copying open bugs over
> should be fine -- I hope there are not too many?

14, presently.
Of which 4 might be closable if we switch to the LLVM-API version.
Only, the API version surely has more bugs than that right now, but
those would be reported at the new site :)

kalle

------------------------------------------------------------------------------
Introducing Performance Central, a new site from SourceForge and 
AppDynamics. Performance Central is your source for news, insights, 
analysis and resources for efficient Application Performance Management. 
Visit us today!
http://pubads.g.doubleclick.net/gampad/clk?id=48897511&iu=/4140/ostg.clktrk
_______________________________________________
pocl-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/pocl-devel

Reply via email to