[R-pkg-team] When working on r-* packages in new please work First-in-First-Out (Was: r-cran-stanheaders_2.17.2-1_amd64.changes is NEW)
Andreas Tille
tille at debian.org
Fri May 18 10:24:48 BST 2018
Hi Chris,
On Thu, May 17, 2018 at 08:34:37AM +0100, Chris Lamb wrote:
> > Bug #852925 is a good example why this makes a difference. Despite I
> > mailed ftpmaster about the fact that r-cran-aer needs to be accepted
> > before r-cran-zelig this information somehow slipped through
>
> I understand but I fear you may be underestimating how much mail the
> ftpmaster@ email inbox gets
Most probably ...
> as well as the mental overhead of having
> to store state about R-specific packages. :)
>
> The odd bug (which has a known solution & one that's additionally
> being publically documented) doesn't seem too bad of a trade-off..
OK. So if it is not helpful what I assumed to be my contribution to
help avoiding this kind of bugs I'll stop doing this.
Thanks for the clarification and your work as ftpmaster in general
Andreas.
PS: What about hints about low hanging fruits like r-cran-bh? Is
at least this helpful or another kind of noise?
--
http://fam-tille.de
More information about the R-pkg-team
mailing list