File: release.Rmd

package info (click to toggle)
r-cran-ggplot2 1.0.0-1
  • links: PTS, VCS
  • area: main
  • in suites: jessie, jessie-kfreebsd
  • size: 4,412 kB
  • sloc: sh: 9; makefile: 1
file content (107 lines) | stat: -rw-r--r-- 3,128 bytes parent folder | download | duplicates (2)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
<!--
%\VignetteEngine{knitr::knitr}
%\VignetteIndexEntry{ggplot2 release process}
-->

```{r, echo = FALSE, message = FALSE}
knitr::opts_chunk$set(
  comment = "#>",
  error = FALSE,
  tidy = FALSE
)
library(ggplot2)
```

# Releasing a new version of ggplot2

## Release candidate phase

After issues resolved for a given release:

1.  Pass R CMD check.

1.  In DESCRIPTION and NEWS, remove the .99 version suffix and increment the
    version number. For example, 0.9.2.99 becomes 0.9.3.

1.  Do the same for any packages that ggplot2 depends on, such as scales and
    gtable.

1.  Update ggplot2's Import dependency versions to use the final release numbers
    of scales and gtable.

1.  Commit these changes to a branch with `ggplot2-<version>-rc`, and push the
    branch.
    
1.  Check packages that depend on ggplot2 with `devtools::revdep_check()` and
    run visual tests.

1.  Email ggplot2, ggplot2-dev, and bcc the maintainers of packages that depend 
    on ggplot2 (`revdep_maintainers("ggplot2")`).
    
    ```
    Hi all,
    
    We're very please to announce a release candidate for ggplot2 1.0.0! This
    release celebrates the ggplot2 community: all improvements have been 
    contributed via pull requests.
    
    We've made every effort to make sure that your existing ggplot2 graphics
    continue to work. ggplot2 1.0.0 has passed R CMD check, all our existing 
    visual tests, and R CMD check on all dependencies. But it's still possible 
    that some bugs may have crept in, so we'd really appreciate it if you'd 
    try it out. It's easy to install the development version: first install 
    devtools, then run `devtools::install_github("hadley/ggplot2@ggplot2-1.0.0-rc")`.
    
    We plan to submit ggplot2 to cran in two weeks, May 9. Please let us know if 
    you have any problems - your feedback is much appreciated. (If you're pretty
    sure you've discovered a new bug, please start a new thread or file
    an issue on github, otherwise it's a bit hard to track what's going on).
    
    Hadley & Winston
    ```

1.  Notify cran:

    ```
    Dear CRAN maintainers,
    
    ggplot2 1.0.0 has entered the release candidate phase and will be
    submitted to CRAN in two weeks.
    
    Included below is the email that I sent to the ggplot2 mailing and all
    maintainers of packages that depend on ggplot2.
    
    Regards,
    
    Hadley
    ```

If problems arise during the RC period, make fixes on the branch. Those fixes
later get merged back into master.

## Release

When the package is accepted on CRAN:

1.  Create a new release at https://github.com/hadley/ggplot2/releases.
    The tag name should be of the form `v1.0.0`.

1.  If any Check out the new branch, or merge it into master. (Need to get off the
    rc branch so it can be deleted):

    ```
    VERSION=1.0.0
    git checkout v$VERSION
    # Or
    git checkout master
    git merge v$VERSION
    ```

1.  Delete the `-rc` branch, with:

    ```
    git branch -d v$VERSION-rc
    git push origin :v$VERSION-rc
    ```

1.  Once you push the tag github, travis will automatically build the website.