Dear Dan Your reply is really exiting. Here I change the version number 2.0.1 to 2.1.2. As you say, I have 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. Now z is bumped to 2 from 1 which is needed to be added to the repository.
Whether this means that the one with right version number will be built again and published on the Bioconductor web site tomorrow. So,after then, could FEM 2.2.0(which needed to be bumped in release) be included in the new BioC release on April 19. Thanks again for your help. Kind Regards Yinming > -----原始邮件----- > 发件人: "Dan Tenenbaum" <dtene...@fredhutch.org> > 发送时间: 2015年3月18日 星期三 > 收件人: "Yinming Jiao" <20907...@zju.edu.cn> > 抄送: bioc-devel <bioc-devel@r-project.org> > 主题: Re: [Bioc-devel] FEM package updation build frequence > > Hi, > > > > ----- Original Message ----- > > From: "Yinming Jiao" <20907...@zju.edu.cn> > > To: "bioc-devel" <bioc-devel@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? > > > > (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 > > http://bioconductor.org/packages/release/bioc/html/ > > 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. > > Dan > > > > > 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@r-project.org mailing list > > https://stat.ethz.ch/mailman/listinfo/bioc-devel > > -- CAS-MPG Partner Institute for Computational Biology 320 Yue Yang Road Shanghai 200031 China Email: 20907...@zju.edu.cn or jiaoyinm...@picb.ac.cn Mob: +86 1852139 6188 _______________________________________________ Bioc-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/bioc-devel
