Skip to content

Commit c66f017

Browse files
RELEASING: Bugzilla no longer needs updated
1 parent 717f0e0 commit c66f017

File tree

1 file changed

+9
-11
lines changed

1 file changed

+9
-11
lines changed

RELEASING

+9-11
Original file line numberDiff line numberDiff line change
@@ -161,7 +161,13 @@ Here are the steps to follow to create a new cairo release:
161161
If for some reason you lost this message, "make release-publish-message"
162162
prints it for you.
163163

164-
Upload the incremental ChangeLog generated by the above:
164+
Upload the incremental ChangeLog generated by the above. For
165+
minor stable releases, this is:
166+
167+
scp ChangeLog \
168+
cairographics.org:/srv/cairo.freedesktop.org/www/releases/ChangeLog.cairo-${THIS_RELEASE}
169+
170+
for micro and snapshot releases, the command is:
165171

166172
scp ChangeLog.cache-${LAST_RELEASE}.. \
167173
cairographics.org:/srv/cairo.freedesktop.org/www/releases/ChangeLog.cairo-${THIS_RELEASE}
@@ -193,13 +199,7 @@ Here are the steps to follow to create a new cairo release:
193199

194200
git commit cairo-version.h -m "Bump version for ${DEVEL_VERSION}"
195201

196-
10) Edit the cairo bugzilla product and add the new version numbers.
197-
198-
Note that you need to add two versions. One for the
199-
release/snapshot (with an even micro version), another with the
200-
post-release version (with an odd micro version).
201-
202-
11) Send out an announcement message.
202+
10) Send out an announcement message.
203203

204204
Send a message to [email protected] and CC
205205
@@ -210,8 +210,6 @@ Here are the steps to follow to create a new cairo release:
210210

211211
git shortlog ${LAST_RELEASE}...
212212

213-
12) Add the announcement to the website as a new entry in the news/
213+
11) Add the announcement to the website as a new entry in the news/
214214
dir. It will automatically get indexed onto the homepage when the
215215
site refreshes.
216-
217-

0 commit comments

Comments
 (0)