[Biojava-dev] Cloning repositories in eclipse

[Spencer Bliven]

So did we reach a consensus on this issue? Should I rename devel to master?


On Thu, Apr 11, 2013 at 3:07 PM, Spencer Bliven <sbliven at ucsd.edu> wrote:

> I got a little behind on this thread.
>
>
> On Wed, Apr 10, 2013 at 4:10 PM, P. Troshin <to.petr at gmail.com> wrote:
>
>> So it would be nice to have things working out of the box. Alternatively
>> maybe it is worth looking for/trying alternative Git plugin?
>>
>
> Peter, Eclipse does work with git (the second set of instructions here<http://biojava.org/wiki/BioJava3_eclipse>do work, it just takes more steps than the old svn workflow. There is a
> JGit plugin for eclipse, but it doesn't seem to have a maven connector like
> EGit does.
>
>
> On Wed, Apr 10, 2013 at 4:53 PM, Hannes Brandstätter-Müller <
> biojava at hannes.oib.com> wrote:
>
>> It makes pull requests a bit complicated too, as the web UI defaults to
>> the release branch.
>>
>
> Hannes, I can see your point. My original thought was that Master should
> be default so that new users would get a stable checkout, whereas
> developers should know about git enough to figure it out. I was expecting
> the tools to make it a bit easier to choose branches.
>
> But moving devel -> master and making that the default sounds smart. Users
> who want stable releases are likely to use maven or download jars, so we
> should make git default to the latest code.
>
> I do like having a single release branch, rather than just a series of
> tags or a whole slew of release branches. We don't really do hotfixes, so
> the full git-flow layout is overkill.
>
> -Spencer
>
>