[Bioc-devel] Pushing updates in the release branch

Obenchain, Valerie Valerie.Obenchain at roswellpark.org
Fri May 27 02:37:55 CEST 2016

Hi Charles,

Yes, the usual advice is that you touch release for bug fixes only but
can update as often as you like in devel. This is the same pattern
followed for our experimental data and annotation packages. Once we have
a release those data are frozen and for 6 months are considered the
'current release'.

Are the ENCODE files updated more frequently than every 6 months? I was
wondering if you could query for this information on-the-fly but a quick
look at encode_df makes me think the data are heavily curated and
real-time retrieval might not be possible.


On 05/22/2016 06:36 AM, Charles Joly wrote:
> Hello,
> I'm the maintainer of the ENCODExplorer package. We provide the metadatas
> of the ENCODE project files in the `data/` section of the package.
> The problem is that there are regularly new datasets and changes in the
> previous dataset. I was wondering if it is OK to push new versions of the
> metadatas even if the documentation mentions:
> "Only bug fixes should be back-ported to the release branch. This is so
> that users of the release branch have a stable environment in which to get
> their work done."
> Thanks!
> Charles Joly Beauparlant.
> 	[[alternative HTML version deleted]]
> _______________________________________________
> Bioc-devel at 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.

More information about the Bioc-devel mailing list