Forum: developers
Monitor Forum | 
Start New Thread
| RE: Version numbers - patch levels [ Reply ] By: Arne Henningsen on 2008-09-25 10:08 | [forum:858] |
|
Ott Toomet wrote: > I would stick to this procedure and increase the patch level again. Yes, I also think that this is the safest. Arne |
|
| RE: Version numbers - patch levels [ Reply ] By: Ott Toomet on 2008-09-25 10:03 | [forum:857] |
|
I think this is the best solution. One issue: if the cran people discover a minor issue soon after uploading? I would stick to this procedure and increase the patch level again. I.e. we essentially drop the number of the problematic version. It should be the safest way although a little bit overkill. Ideas? Ott |
|
| Version numbers - patch levels [ Reply ] By: Arne Henningsen on 2008-09-25 09:24 | [forum:856] |
|
Hi! Ott suggested that we always increase the patch level *after* releasing a new version on CRAN. This avoids the problem of having two different versions (released version on CRAN + development version in the SVN repository) with the same version number (including patch level). I think that this is a great idea -- particularly since the development version is available for download on R-Forge now. Hence, I suggest the following procedure for releasing the package on CRAN: 1) run "R CMD check" on the package In case of any warnings or errors, correct these bugs and commit them to the SVN repository 2) increase patch level to an even number and update the date in the DESCRIPTION file (in case of major changes, increase version number and set patch level to zero) and commit these changes to the SVN repository 3) build package 4) upload the package to CRAN 5) increase patch level to an odd number and commit this change to the SVN repository What do you think? Arne |
|
