You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* Copy the previous announcement and modify with release-specific information
59
-
* The "Known Issues", "Bug", and "Improvement" sections are generated by JIRA. Click on the specific version of the [C++ Driver Project](https://jira.mongodb.org/browse/CXX/?selectedTab=com.atlassian.jira.jira-projects-plugin:versions-panel) and on the version Summary page there is a link for "Release Notes" where you can copy the HTML and paste it into the GitHub Release Notes markdown.
60
-
* Draft and publish a new release against the tag you just pushed
72
+
* Go to the [GitHub releases page](https://github.com/mongodb/mongo-cxx-driver/releases).
73
+
* Copy the previous announcement text for reuse.
74
+
* Click "Draft a New Release" and set the title and tag. Check the
75
+
"This is a pre-release" checkbox if appropriate.
76
+
* Paste the previous announcement and modify with release-specific information
77
+
* Go back to the "Release Notes" page in Jira; copy the HTML and paste it into
78
+
the GitHub Release Notes markdown. Delete the "Task" section and any
79
+
other information that doesn't need to be in the release notes.
* Close all the the Resolved tickets via a [bulk transition](https://confluence.atlassian.com/jira/modifying-multiple-bulk-issues-185729606.html)
67
87
* Click the cog next to the version you are about to release and select "Release"
68
88
* Follow the dialogs/wizards and whatnot, setting the release date to the current date
69
89
@@ -106,14 +126,14 @@ and pushed.
106
126
`hugo-deploy` and `doxygen-deploy` targets. The doxygen build will take
107
127
a long time.
108
128
109
-
*Check out the "gh-pages" branch and `git pull` the deployed docs.
110
-
111
-
* Update the api/mongocxx-v3 symlink to point to the newly released
112
-
version. If a major version bump has occurred, revise the symlink
113
-
structure as needed. Make sure 'current' always points to a *symlink*
114
-
tracking the latest release branch.
115
-
116
-
* Commit and push the symlink change.
129
+
*If the release was *not* a release-candidate, update symlinks
130
+
* Check out the "gh-pages" branch and `git pull` the deployed docs.
131
+
* If the release was *not* a release-candidate, update the
132
+
api/mongocxx-v3 symlink to point to the newly released version. If a
133
+
major version bump has occurred, revise the symlink structure as
134
+
needed. Make sure 'current' always points to a *symlink* tracking
135
+
the latest release branch.
136
+
* Commit and push the symlink change.
117
137
118
138
`git commit -am "Update symlink for r3.0.3"`
119
139
@@ -136,16 +156,65 @@ git push origin master
136
156
## Email Google Groups
137
157
138
158
* Send it to mongodb-announce@googlegroups.com AND mongodb-user@googlegroups.com
139
-
* Template:
140
-
141
-
> The MongoDB C++ Driver Team is very excited to announce the availability of version X.Y.Z of the new MongoDB C++11 driver.
142
-
> We are not promising API or ABI stability until the 3.1.0 release so that we can meaningfully incorporate user feedback after the 3.0.0 GA. We will make every effort to minimize API changes. The new driver is incompatible with the prior legacy, 26compat, and server C++ drivers.
143
-
>
144
-
> You can obtain the source for the new driver from GitHub, either under the rX.Y.Z tag or from the releases page. General documentation for the new driver is available on the github wiki. Doxygen API documentation is also available.
145
-
>
146
-
> Please feel free to post any questions to the mongodb-user mailing list. Bug reports should be filed against the CXX project in the MongoDB JIRA. If you are interested in participating in the development of the C++11 driver, questions should be sent to the mongodb-dev mailing list. Github pull requests are welcome, and should be issued against the master branch of the repository, where the C++11 driver is developed.
147
-
> We look forward to hearing from you. Happy C++11’ing!
0 commit comments