On 01/18/2017 08:55 AM, Dirk Eddelbuettel wrote:
On 18 January 2017 at 13:49, Thierry Onkelinx wrote:
| Another solution is to start a new package. This is what Hadley did with
| the ggplot package (https://cran.r-project.org/src/contrib/Archive/ggplot/).
| The new version (ggplot2) would brea
On 18 January 2017 at 13:49, Thierry Onkelinx wrote:
| Another solution is to start a new package. This is what Hadley did with
| the ggplot package (https://cran.r-project.org/src/contrib/Archive/ggplot/).
| The new version (ggplot2) would break existing code. Users were informed
| that the old p
Another solution is to start a new package. This is what Hadley did with
the ggplot package (https://cran.r-project.org/src/contrib/Archive/ggplot/).
The new version (ggplot2) would break existing code. Users were informed
that the old package is not longer maintained. So the user has the choice
be
On 18/01/2017 5:31 AM, Berry Boessenkool wrote:
What's good practice to inform users about an API change?
The package in question is extremeStat. Apparently, people actually use it.
I don't have a userbase like Hadley, but I do receive emails with feature
requests and code change suggestions
What's good practice to inform users about an API change?
The package in question is extremeStat. Apparently, people actually use it.
I don't have a userbase like Hadley, but I do receive emails with feature
requests and code change suggestions.
Since the change is rather big (going from vers
