These are chat archives for biojs/biojs

5th
Sep 2014
Tim Ruffles
@timruffles
Sep 05 2014 09:15
@greenify I think in future doing that isn't ideal. If ppl are worried about 30mb download they can use git clone --single-branch :)
if you look across all open-source projects, I'd say that's a v unusual move
Michiel Helvensteijn
@mhelvens
Sep 05 2014 10:28
@timruffles: What move are you referring to?
Sebastian Wilzbach
@wilzbach
Sep 05 2014 10:33
@mhelvens: moving biojs1 to a separe repo and doing a git push -f to biojs/biojs
Tim Ruffles
@timruffles
Sep 05 2014 10:50
yup
Michiel Helvensteijn
@mhelvens
Sep 05 2014 10:52
Right. Then I agree with Tim on this one. Different versions can stay in the same repo. That's what branching is for.
Sebastian Wilzbach
@wilzbach
Sep 05 2014 10:52
@timruffles: there was no common history and I wanted to make it clear that there are completely different
@timruffles @mhelvens scroll up for other reasons - however we still could push the biojs1 branch into the repo
Michiel Helvensteijn
@mhelvens
Sep 05 2014 10:53
It is tricky to decide when to switch the 'master' branch to the new version. (Or, perhaps that's not necessary at all?)
A 'master' branch (or 'trunk') is somewhat silly anyway. Only important by convention.
But having all development done in a branch (which never merges back) is sensible in a situation like this.
Tim Ruffles
@timruffles
Sep 05 2014 10:55
tags would help
Michiel Helvensteijn
@mhelvens
Sep 05 2014 10:55
Tags are snapshots, i.e., releases. How do they help in this scenario?
Tim Ruffles
@timruffles
Sep 05 2014 10:55
also it's unfair on old commiters
Sebastian Wilzbach
@wilzbach
Sep 05 2014 10:55
my opinion: branches only make sense if they origin from the same tree
Tim Ruffles
@timruffles
Sep 05 2014 10:55
will talk later
Michiel Helvensteijn
@mhelvens
Sep 05 2014 10:56
@greenify: They all come from the same root, i.e., the empty tree. ;-)
Sebastian Wilzbach
@wilzbach
Sep 05 2014 10:56
"it's unfair on old commiters": yes, my biggest concern.
Tim Ruffles
@timruffles
Sep 05 2014 12:03
hi guys, sorry that was so rushed earlier. Shall we arrange a catch up at some point next week?
up for doing another burst of work on registry
Michiel Helvensteijn
@mhelvens
Sep 05 2014 12:04
I'd like to help, but I'm pretty busy with ApiNATOMY. Probably won't have time to work on registry.
Tim Ruffles
@timruffles
Sep 05 2014 12:04
np - it's in a great place already
Sebastian Wilzbach
@wilzbach
Sep 05 2014 14:09
@timruffles great idea. In two weeks we have the ebi codefest which could give biojs another huge push :)