The release schedule has now been set with a release date on April 18.
The detailed procedure can be found at http://developer.r-project.org/
(it is not quite there yet, but will appear after a short propagation
delay.)
The main point for non-developers is that we start making alpha
tarballs on March 21 and beta tarballs on April 4. Only very simple
and/or critical bugs are fixed in the last week before release.
As usual, we encourage users to build and test the pre-release, and
help us find and fix bugs before rather than immediately after the
release.
For the R Core Team
Peter Dalgaard
--
O__ ---- Peter Dalgaard Blegdamsvej 3
c/ /'_ --- Dept. of Biostatistics 2200 Cph. N
(*) \(*) -- University of Copenhagen Denmark Ph: (+45) 35327918
~~~~~~~~~~ - (p.dalgaard@biostat.ku.dk) FAX: (+45) 35327907
Jan T. Kim
2005-Mar-03 14:08 UTC
[Rd] Connection Programming API (was: R 2.1.0 scheduled for April 18)
On Wed, Mar 02, 2005 at 10:35:51PM +0100, Peter Dalgaard wrote:> The release schedule has now been set with a release date on April 18. > > The detailed procedure can be found at http://developer.r-project.org/ > (it is not quite there yet, but will appear after a short propagation > delay.)Are there any plans on providing an API that would allow packages to create and handle connections, before the "grand feature freeze"? The reason I ask is that I recently submitted a patch that adds filtering data through pipes to the core code. I had to write this as a patch because connection handling is done in a static array in src/main/connections.c and there is no API allowing packages to operate on that array. Will R 2.1.0 include filtering? And perhaps also forking, while we're at this? Best regards, Jan -- +- Jan T. Kim -------------------------------------------------------+ | *NEW* email: jtk@cmp.uea.ac.uk | | *NEW* WWW: http://www.cmp.uea.ac.uk/people/jtk | *-----=< hierarchical systems are for files, not for humans >=-----*