[Bioc-devel] verification on configuration
Shepherd, Lori
Lor|@Shepherd @end|ng |rom Ro@we||P@rk@org
Fri Jun 7 18:48:34 CEST 2019
The instructions on
https://bioconductor.org/developers/how-to/git/maintain-github-bioc/
will not necessarily update the git.bioconductor.org version of the package. Please also see
https://bioconductor.org/developers/how-to/git/push-to-github-bioc/
If the remotes are set up as follows (you can check with git remote -v)
origin git using github.com:<developer>/ChIPSeqSpike.git (fetch)
origin git using github.com:<developer>/ChIPSeqSpike.git (push)
upstream git using git.bioconductor.org:packages/ChIPSeqSpike.git (fetch)
upstream git using git.bioconductor.org:packages/ChIPSeqSpike.git (push)
We will recognize changes when there is a successful push to the upstream remote
git push upstream master
The "deployed only if bump" is still valid. The build system will only recognize a new version of a package with a version bump in the DESCRIPTION. So the NEWS file change will not be visible on the package landing page until there is a version bump.
You can create branches and push them to your own git repository. Bioconductor does not allow additional branches created by maintainers. We create a release branch for each new release of a package. Any change will have to be merged into the master branch (for devel version of bioconductor) or the current release branch (right now RELEASE_3_9) and a push to upstream in order for changes to take effect.
Hope this helps and don't hesitate to ask more questions here on the mailing list bioc-devel using r-project.org if you have any difficulties.
Cheers,
Lori Shepherd
Bioconductor Core Team
Roswell Park Cancer Institute
Department of Biostatistics & Bioinformatics
Elm & Carlton Streets
Buffalo, New York 14263
________________________________
From: Bioc-devel <bioc-devel-bounces using r-project.org> on behalf of Nicolas Descostes <nicolas.descostes using gmail.com>
Sent: Friday, June 7, 2019 12:22:19 PM
To: bioc-devel using r-project.org
Subject: [Bioc-devel] verification on configuration
Hi,
I am coming back to my package ChIPSeqSpike after a long break. I have
followed the instructions here:
https://bioconductor.org/developers/how-to/git/maintain-github-bioc/
I have imported my project in eclipse and did a push after modifying the
NEWS file. Will this be visible on the dev page knowing that I did not bump
the version?
Can you confirm that following the instructions above will modify the dev
branch?
I see that it is now possible to create branches, I think it was not
possible before. Will the modifications on a particular branch pushed to
upstream only when merging it?
Is the rule "deployed only if bump" still valid?
Sorry for not having followed all modifications, just coming back to it.
Best,
Nicolas
[[alternative HTML version deleted]]
_______________________________________________
Bioc-devel using r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/bioc-devel
This email message may contain legally privileged and/or confidential information. If you are not the intended recipient(s), or the employee or agent responsible for the delivery of this message to the intended recipient(s), you are hereby notified that any disclosure, copying, distribution, or use of this email message is prohibited. If you have received this message in error, please notify the sender immediately by e-mail and delete this email message from your computer. Thank you.
[[alternative HTML version deleted]]
More information about the Bioc-devel
mailing list