[Roxygen-devel] roxygen3

[Hadley Wickham]

> May be it's time to revert to "roxygen" name?

Roxygen3 may well revert to roxygen2, but I don't currently want to
tie myself to non-breaking changes.  (e.g. I'm considering allow
markdown syntax in roxygen comments)

> Roxygen is not required by any other package; so no dependence
> problems. Also if user interface is not changed, and only internals are
> refactored, then there is no need for a new name, is it?

If there are breaking changes, and you have packages with old and new
systems, then you will still need both installed.

> Another option would be to release a new "old" package like
> "roxygen_old", "ggplot_old" etc. Then people can just use the old one
> with minimal inconvenience. The problem with this, is that there might
> be papers/books published with the old command interface, but people
> understand that, so not a big deal anyways.

But that doesn't resolve the problem of update.packages() breaking
code, which is the whole point of bumping the package name.

Hadley


-- 
Assistant Professor
Department of Statistics / Rice University
http://had.co.nz/