Re: [Bioc-devel] best way to transition users to new version of package

2015-05-28 Thread Robert M. Flight
Thanks Martin. I've already been working on the new version as a separate package, although branched from the previous code base because I was planning on merging it back in. After some thought, I do think the best way to do it will be to deprecate the original package, including the name of the

Re: [Bioc-devel] best way to transition users to new version of package

2015-05-28 Thread Robert M. Flight
Thanks for the feedback Wolfgang. I never thought to look at how many packages in Bioconductor have a baseName and baseName2 to see how often this is done. I assume based on the existence of Roxygen2 and ggplot2 that there were initial versions of those named Roxygen and ggplot. This also seems

Re: [Bioc-devel] best way to transition users to new version of package

2015-05-28 Thread Martin Morgan
On 05/28/2015 06:32 AM, Robert M. Flight wrote: Thanks for the feedback Wolfgang. I never thought to look at how many packages in Bioconductor have a baseName and baseName2 to see how often this is done. I assume based on the existence of Roxygen2 and ggplot2 that there were initial versions of

[Bioc-devel] best way to transition users to new version of package

2015-05-27 Thread Robert M. Flight
I am the author and maintainer of the categoryCompare package on Bioconductor. As I and others have used it over the years, I am seeing that there are a lot of design mistakes in the code, and that it was not extensible in it's current form. Therefore, I decided to do a complete rewrite starting

Re: [Bioc-devel] best way to transition users to new version of package

2015-05-27 Thread Wolfgang Huber
Robert with the packages cellHTS, cellHTS2 and DESeq, DESeq2 (and with the functions vsn, vsn2 in the vsn package) I three times chose route 1, and am generally happy about it. In due time, you can deprecate and then defunct the old one. Option 2 seems needlessly disruptive (potentially). A