[Bioc-devel] 答复: A little confuse about how to update accepted package

[Matthias Doering]

Dear Wenhao,

regarding your two points:


1. If you have incremented your version number and pushed to one of the 
Bioconductor servers (either upstream master or release), a build is 
automatically triggered. The build cycle is 24 hours if I remember 
correctly.

2.You don't need to have a local branch of the release. I guess it's 
just in the tutorial for convenience sake. For example, if you find 
there are more bugs to fix and you have to do some more edits of the 
release version, it's easier to keep track ..


Kind regards

  Matthias

On 11/11/18 9:43 AM, Tang, Wenhao wrote:
> Dear all,
>
>
> Currently, for both branches: master and RELEASE_3_8 in my github repository:
>
> https://github.com/WT215/bayNorm/tree/master
>
>
> have been updated with version number 1.0.2.
>
>
> However, in the latest build report:
>
> http://bioconductor.org/checkResults/3.8/bioc-LATEST/bayNorm/
>
>
> the version is still 1.0.0.
>
>
> I have the following two questions:
>
>
>    1.  Do I have to wait 24 hours to see whether the update in the release version success or not?
>    2.  Do I need to have two local repositories for Release and Developed versions bayNorm respectively? In the tutorial: http://bioconductor.org/developers/how-to/git/sync-existing-repositories/, it seems that only local (Release), Bioconductor (Release), and GitHub repositories (Release) can be synced.
>
> Thank you very much!
>
> Best wishes,
> Wenhao
>
>
>
>
>
>
>
>
> Thank you very much!
>
>
> Best wishes,
>
> Wenhao
>
> ________________________________
> 发件人: Martin Morgan <mtmorgan.bioc using gmail.com>
> 发送时间: 2018年11月10日 19:10:13
> 收件人: Tang, Wenhao; bioc-devel using r-project.org
> 主题: Re: [Bioc-devel] A little confuse about how to update accepted package
>
> The steps below are correct, but perhaps not sufficient for what you want to do.
>
> Bioconductor packages consist of release branches, which are meant to be stable for the end user, and the 'devel' branch where new features can be introduced.
>
> There is a version numbering scheme, outlined at
>
>    http://bioconductor.org/developers/how-to/version-numbering/
>
> to ensure that each published version of the package has a different version, that versions in release always increase, and that the devel version is always ahead of the release version. For your package, the release version is 1.0.0, and the devel version is 1.1.0.
>
> If you intended to make a change to the devel version of your package, because you were introducing a new feature or perhaps testing a bug fix, then you have been successful; you have pushed your changes to the devel ('master') branch, and incremented the version to 1.1.1.
>
> If you intend to make this change also in the release, then the extra steps in
>
>    http://bioconductor.org/developers/how-to/git/bug-fix-in-release-and-devel/
>
> are required -- check out the RELEASE_3_8 branch, port your changes from master, increment the release version to 1.0.1, and push.
>
> During the submission process packages are built immediately, but in the devel and release branches they are built nightly, approximately (I think that last night in particular there were issues with network connectivity that might severely limit the success of the build). The build reports are available from
>
>    http://bioconductor.org/checkResults/
>
> note the 'snapshot' time stamps and commit information for the overall build and for your individual package to see whether your commit was included in the nightly build.
>
> Martin
>
> On 11/10/18, 5:53 AM, "Bioc-devel on behalf of Tang, Wenhao" <bioc-devel-bounces using r-project.org on behalf of wenhao.tang15 using imperial.ac.uk> wrote:
>
>      Dear Bioconductor team,
>
>
>      My package bayNorm has recently been accepted, it now has version 1.0.0. Currently I would like to make some changes to it. I look through the tutorials online but I am still very confused. Below is what I have done:
>
>
>      My local repository has version 0.99.19. So I  did the following in my local repository:
>
>        1.  git remote add upstream git using git.bioconductor.org:packages/bayNorm
>        2.  git fetch --all
>        3.  git checkout master
>        4.  git merge origin/master
>        5.  git merge upstream/master
>
>      Now the local version is 1.1.0 rather than 0.99.19.
>
>
>      Then I just did a small change (in addition, I bump the version to 1.1.1) and then run the following command under the local repository:
>
>        1.  git push upstream master
>        2.  git push origin master
>
>      Is the above procedure correct? Will I see the package building report like what I have received during the submission process?
>
>      Your tutorials are very clear, and I am sorry if my question is too trivial.
>
>      Thank you very much!
>
>      Best wishes,
>      Wenhao
>
>           [[alternative HTML version deleted]]
>
>      _______________________________________________
>      Bioc-devel using r-project.org mailing list
>      https://stat.ethz.ch/mailman/listinfo/bioc-devel
>
>
> 	[[alternative HTML version deleted]]
>
> _______________________________________________
> Bioc-devel using r-project.org mailing list
> https://stat.ethz.ch/mailman/listinfo/bioc-devel