From hb at biostat.ucsf.edu  Sat Mar  9 22:00:42 2013
From: hb at biostat.ucsf.edu (Henrik Bengtsson)
Date: Sat, 9 Mar 2013 13:00:42 -0800
Subject: [Rd] question on why Rigroup package moved to Archive on CRAN
In-Reply-To: <BLU0-SMTP1663AF8838B6E599BDF19787E70@phx.gbl>
References: <BLU0-SMTP1663AF8838B6E599BDF19787E70@phx.gbl>
Message-ID: <CAFDcVCSpBzh0hm0_C=SfYTVekrZ7iSckuDg5wFwd5f2N0bGbSA@mail.gmail.com>

On Sat, Mar 9, 2013 at 12:25 PM, Kevin Hendricks
<kevin.hendricks at sympatico.ca> wrote:
> Hi,
>
> Who should I ask about my package Rigroup_0.83 being moved to Archive status on CRAN and no longer available via install.package?  I have no problems with the move if this was simply because of low demand.  However, if there was a build issue with the newest releases that caused problems, I would be happy to address it.  I'll just ask my students to install it from my own locally hosted source archive.

Most likely yourself; from the 'CRAN Repository Policy'
[http://cran.r-project.org/web/packages/policies.html]:

"Packages will not normally be removed from CRAN: however, they may be
archived, including at the maintainer's request.

Packages for which R CMD check gives an ?ERROR? when a new R x.y.0
version is released will be archived (or in exceptional circumstances
updated by the CRAN team) unless the maintainer has set a firm
deadline for an upcoming update (and keeps to it).

Maintainers will be asked to update packages which show any warnings
or significant notes, especially at around the time of a new x.y.0
release. Packages which are not updated are liable to be archived."

/Henrik

>
> Thanks,
>
> Kevin
> ______________________________________________
> R-devel at r-project.org mailing list
> https://stat.ethz.ch/mailman/listinfo/r-devel



[Rd] question on why Rigroup package moved to Archive on CRAN
Henrik Bengtsson