Yes, that's what the API freeze means. The goal is to prevent last
minute changes in chimeraviz from breaking downstream packages that
depend on chimeraviz. By the way, the API freeze was Friday, April 7.
Valerie
On 04/21/2017 03:21 AM, Stian Lågstad wrote:
I've added a new function to my package chimeraviz (so far it's in a
separate branch and not commited to Bioconductor). Does the API freeze
mean that I have to wait until the Bioconductor release before I
commit it to the devel branch?
On Fri, Apr 7, 2017 at 2:38 AM, Valerie Obenchain <voben...@gmail.com
<mailto:voben...@gmail.com>> wrote:
Hi,
Some recent activity has caused some (red) ripples across the
builds and the El Capitan Mac builds are still unsettled. To
accommodate, we're extending the deadline to pass R CMD build and
check with no errors to next Friday
(http://www.bioconductor.org/developers/release-schedule/
<http://www.bioconductor.org/developers/release-schedule/>).
Thanks to everyone for cleaning up their packages and
communicating problems (and solutions!) on the lists.
Key deadlines for April 7 are
- No new packages added to the 3.5 roster
- No more API changes
- Current release 3.4 builds will stop
- Annotation packages (both internal and contributed) posted to
the 3.5 repo
Valerie
_______________________________________________
Bioc-devel@r-project.org <mailto:Bioc-devel@r-project.org> mailing
list
https://stat.ethz.ch/mailman/listinfo/bioc-devel
<https://stat.ethz.ch/mailman/listinfo/bioc-devel>
--
Stian Lågstad
+47 41 80 80 25
_______________________________________________
Bioc-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/bioc-devel
