Hi Dan,
can't wait to walk this bridge. Could you tease us a bit on how it would
work? Will it use github's svn interface and leave developers transparently
use a plain github repo (possibly following some simple naming conventions)?
Many thanks.

Bests,
Renaud


On 26 September 2013 19:25, Dan Tenenbaum <dtenenba@fhcrc.org> wrote:

> Hi Renaud,
>
> We're working on a github-svn bridge for Bioconductor packages, but it's
> not ready yet. We will definitely announce it when it is ready.
> It will supersede the document you're looking at, though there is nothing
> to stop you from continuing to use that if you want to.
>
>
> Dan
>
>
> ----- Original Message -----
> > From: "Renaud Gaujoux" <renaud@mancala.cbio.uct.ac.za>
> > To: bioc-devel@r-project.org
> > Sent: Thursday, September 26, 2013 1:09:15 AM
> > Subject: [Bioc-devel] Clarifying/simplifying on the SVN-Github mirroring
> >
> > Hi,
> >
> > if I understood correctly the instructions on
> >
> https://github.com/Bioconductor/BiocGithubHelp/wiki/Managing-your-Bioc-code-on-hedgehog-and-github
> ,
> > it is recommend to work/branch out directly on the local git-svn
> > branch,
> > and merge into the github master branch to sync code on github.
> > Couple of
> > questions on this:
> >
> >   * what about feature branches? Should these branch out from the
> >   svn-bound
> > branch? In this case I believe they won't be pushed to github? Easy
> > branching is one of the nice feature of git, which I heavily use
> > (through
> > git-flow) so it is important that the different branches (devel,
> > release,
> > features) are sent back to github in order to really benefit from its
> > management tools (issues, network graph, etc..)
> >   * the workflow seems to be the opposite of what Cameron Bracken's
> >   post
> > suggests http://cameron.bracken.bz/git-with-r-forge , where one work
> > on the
> > github-bound master branch and merge back onto the svn-bound branch
> > once
> > happy, right?
> > I have experimented Cameron's workflow and faced many times lots of
> > conflict issues that are a hassle to solve on each merge. Does the
> > Bioconductor workflow have this issue?
> >
> > Overall, I wonder if it wouldn't be easier (from the developer point
> > of
> > view) if Bioconductor build farm allowed to point to an external SVN
> > repository? Since github provides such an interface that
> > transparently
> > serves github repos to SVN calls, this would just wave out the need
> > for
> > duplicated branches and git-svn integration trick. Possible? Que tal?
> > R-forge used to propose such option, which is apparently and sadly
> > not
> > working anymore. It really avoided lots of head ache.
> >
> > Thank you.
> >
> > Bests,
> > Renaud
> >
> >       [[alternative HTML version deleted]]
> >
> > _______________________________________________
> > Bioc-devel@r-project.org mailing list
> > https://stat.ethz.ch/mailman/listinfo/bioc-devel
> >
>
>

	[[alternative HTML version deleted]]

