The R Core Team has decided to aim for the release of 2.4.1 on Monday December 18. This involves a feature freeze on Monday the 4th and code freeze on Monday 11th. Automated builds of beta release and release candidate tarballs will be available from the 5th and the 12th, respectively. It is not expected that many changes will occur relative to the current R-patched version, but as always: ---> Bugs reported before the release have a better chance of getting fixed soon. <--- For this reason, and because of the risk of accidentally putting "infelicities" into the final release, please do try out the prereleases. Particularly so if your setup is not mainstream OS-wise or configuration-wise. -- O__ ---- Peter Dalgaard ?ster Farimagsgade 5, Entr.B c/ /'_ --- Dept. of Biostatistics PO Box 2099, 1014 Cph. K (*) \(*) -- University of Copenhagen Denmark Ph: (+45) 35327918 ~~~~~~~~~~ - (p.dalgaard at biostat.ku.dk) FAX: (+45) 35327907
On 1 December 2006 at 14:00, Peter Dalgaard wrote: | The R Core Team has decided to aim for the release of 2.4.1 on Monday | December 18. This involves a feature freeze on Monday the 4th and code | freeze on Monday 11th. Automated builds of beta release and release | candidate tarballs will be available from the 5th and the 12th, | respectively. | | It is not expected that many changes will occur relative to the current | R-patched version, but as always: | | ---> Bugs reported before the release have a better chance of getting | fixed soon. <--- FWIW, a R-patched snapshot (of Nov 25) is also in Debian unstable and provides an easy one-shot 'apt-get install' way to test a new-ish R. Following past practice, I also intend to release one or two release candidates for 2.4.1 prior to its release. Regards, Dirk -- I am sorry if I replied later than usually to your email, but for the last few days Comcast acted as an Internet NON-Service provider. -- Dirk
Hi! If I am not wrong issue described at http://thread.gmane.org/gmane.comp.lang.r.devel/9667/focus=9667 did not get any attention. Thought it is true that using names() instead of colnames() does not change mode of data.frame rownames. This issues are also "alive": http://thread.gmane.org/gmane.comp.lang.r.devel/9837/focus=9837 http://thread.gmane.org/gmane.comp.lang.r.devel/7540/focus=7540 http://thread.gmane.org/gmane.comp.lang.r.devel/8513/focus=8518 Thanks, Gregor
Gregor Gorjanc <gregor.gorjanc <at> bfro.uni-lj.si> writes:> > Hi! > > If I am not wrong issue described at > > http://thread.gmane.org/gmane.comp.lang.r.devel/9667/focus=9667 > > did not get any attention. Thought it is true that using names() instead of > colnames() does not change mode of data.frame rownames. > > This issues are also "alive": > > http://thread.gmane.org/gmane.comp.lang.r.devel/9837/focus=9837 > http://thread.gmane.org/gmane.comp.lang.r.devel/7540/focus=7540 > http://thread.gmane.org/gmane.comp.lang.r.devel/8513/focus=8518This one also: http://thread.gmane.org/gmane.comp.lang.r.devel/10723/focus=10723 Thanks! Gregor
And small typo in postscript man page
Index: src/library/grDevices/man/postscript.Rd
==================================================================---
src/library/grDevices/man/postscript.Rd (revision 40125)
+++ src/library/grDevices/man/postscript.Rd (working copy)
@@ -195,7 +195,7 @@
using the \code{encoding} argument the glyphs can be matched to
encoding in use. This suffices for European and Cyrillic languages,
but not for CJK languages. For the latter, composite CID fonts are
- used. These fonts are be useful for other languages: for example they
+ used. These fonts are useful for other languages: for example they
may contain Greek glyphs. (The rest of this section applies only when CID
fonts are not used.)
I will stop now;)
Gregor