[Bioc-devel] FEM package updation build frequence

Dan Tenenbaum dtenenba at fredhutch.org
Tue Mar 17 20:45:35 CET 2015


----- Original Message -----
> From: "Yinming Jiao" <20907099 at zju.edu.cn>
> To: "bioc-devel" <bioc-devel at r-project.org>
> Sent: Tuesday, March 17, 2015 7:52:20 AM
> Subject: [Bioc-devel] FEM package updation build frequence
> Hi Guys
> As a maintainer of FEM BioC package, a new FEM version(2.0.1,
> previous 1.1.0,  z in the version number x.y.z is also  bumped)  is
> submitted to our SVN server last Sunday.It was built once on Monday,
> but it has an error. Then I resubmitted it.
> In the following link http://bioconductor.org/checkResults/ ,so  how
> often are the packages built and checked.
> And, after the package passes the check test, When will it be
> published on bioconductor.org website?

It was published on the Bioconductor web site:


(The Mavericks version isn't updated yet because the Mavericks machine did not complete the build last night due to an unrelated issue).

You might have been expecting to see the update at 


But it's not there. Bioconductor has two branches, release and devel. devel is for active development of packages. The only commits you should make to release are bug fixes and documentation enhancements. 

The next release will be on April 17 and after that, devel will become release. 

Incidentally, you bumped to version 2.0.1 but according to our guidelines (http://bioconductor.org/developers/how-to/version-numbering/) it should be 2.1.0. That is, the y in the x.y.z version number should always be odd in devel and even in release.


> Thanks so much for your attention on our FEM package welcome to play
> with it.

> Really thanks for  your help.
> Kind Regards
> Yinming
> _______________________________________________
> Bioc-devel at r-project.org mailing list
> https://stat.ethz.ch/mailman/listinfo/bioc-devel

More information about the Bioc-devel mailing list