[RsR] synchronization with contributing packages
Ruckstuhl Andreas (rks)
rks at zhwin.ch
Wed Feb 1 19:23:10 CET 2006
I agree with the more pragmatic approach suggested by Martin and supported by Matias as well.
All the best
>> -----Ursprüngliche Nachricht-----
>> Von: r-sig-robust-bounces at r-project.org
>> [mailto:r-sig-robust-bounces at r-project.org] Im Auftrag von
>> Matias Salibian-Barrera
>> Gesendet: Mittwoch, 1. Februar 2006 16:08
>> An: r-sig-robust at stat.math.ethz.ch
>> Betreff: Re: [RsR] synchronization with contributing packages
>> I agree with the more pragmatic approach suggested by
>> Martin: one waits
>> for a reasonably stable robustbase version that includes the code in
>> question, and then the original package is made to depend on
>> (or cease to exist if it has been included completely).
>> On Tue, 31 Jan 2006, Martin Maechler wrote:
>> > >>>>> "ValenT" == Valentin Todorov <valentin.todorov at chello.at>
>> > >>>>> on Tue, 31 Jan 2006 00:26:14 +0100 writes:
>> > ValenT> When, at what stage of maturity of robustbase,
>> > ValenT> should the contributed code be removed from the
>> > ValenT> other packages and they have to rely on
>> > ValenT> 'Depends: robustbase'?
>> > In practice, I would aim for a more pragmatic solution;
>> > e.g., after the appearance of the new version of robustbase,
>> > wait for several weeks before stripping the functionality from
>> > your package. Well actually, as package author, you can do it
>> > immediately in your sources, but only release a new version of
>> > your package to CRAN after a certain amount of time.
>> > Martin
>> > And yes, as Valentin, I am very much interested to hear what
>> > others think...
>> > _______________________________________________
>> > R-SIG-Robust at r-project.org mailing list
>> > https://stat.ethz.ch/mailman/listinfo/r-sig-robust
>> R-SIG-Robust at r-project.org mailing list
More information about the R-SIG-Robust