[Bioc-devel] Maintaining package with already modified fork repository from github.

[Jean-Philippe Villemin]

I have a few questions about managing a bioconductor package. Of course I
have been through the doc for package maintenance here
<https://contributions.bioconductor.org/package-maintenance.html>.
I Just want to check that my forklow is ok.

We have a bioconductor package.
We want to move its github source account to our github account lab. I'm
not sure what should be my starting point.

One collaborator did somes changes on a fork from the github (not
bioconductor) in its github account . He shared access with us  (~100
commits without bumbling x.y.z+1 each commit). I want to reuse that but I
don't know if i still need to fetch also from Bioconductor (before/after)

1 - Access and modify BiocCredientials
<https://git.bioconductor.org/BiocCredentials/login/?next=/BiocCredentials/>
freely.
(I'm not a maintainer, a colleague is, so he will add me. I need that to
fetch from biocond right ?)
2 - On local, clone the fork from my colleague. (or bioconductor first ? )
3 - Should I fetch from Bioconductor ? (pretty sure this part will create
troubles)
4 - Create an empty remote with the same name as on bioconductor, push the
cloned repo

5 - Configure upstream bioconductor...
6 - git push to remote bioconductor.
7 - In April changes will be added to release.

Specific question for 3 : How do we handle the bumble version thing ?
For the push, it will be a major release . (S4 code refactoring) (so should
I push something like 2.0.0)

Thanks.



-- 
*Jean-Philippe Villemin   *- Bioinformatics, PhD -

Cancer Bioinformatics and Systems Biology

Institut de Recherche en Cancérologie de Montpellier

Inserm U1194


*jpvillemin using gmail.com <jpvillemin using gmail.com>*

	[[alternative HTML version deleted]]