diff options
author | mh0310.choi <mh0310.choi@samsung.com> | 2015-07-28 10:46:57 +0900 |
---|---|---|
committer | mh0310.choi <mh0310.choi@samsung.com> | 2015-07-28 13:08:12 +0900 |
commit | 5e67a6f721eaedda61300baf0799199c7771ebd0 (patch) | |
tree | 6cd50b52498aab50e79b966cdccc2a137db316d9 /RELEASING | |
parent | d3aeffba37161d2b76b29c4ea13369bd67a47a8e (diff) | |
download | cairo-5e67a6f721eaedda61300baf0799199c7771ebd0.tar.gz cairo-5e67a6f721eaedda61300baf0799199c7771ebd0.tar.bz2 cairo-5e67a6f721eaedda61300baf0799199c7771ebd0.zip |
Cairo version Upgrade for Tizen3.0submit/tizen_tv/20150728.091927submit/tizen_mobile/20150728.091912submit/tizen_common/20150728.091859accepted/tizen/tv/20150729.011254accepted/tizen/mobile/20150729.011230
- from 1.12.14 to 1.14.2
Change-Id: I3b62d212041b337bbb926d579f9ce74f42a45c3b
Diffstat (limited to 'RELEASING')
-rw-r--r--[-rwxr-xr-x] | RELEASING | 24 |
1 files changed, 11 insertions, 13 deletions
diff --git a/RELEASING b/RELEASING index a1edceba9..641ac1fc4 100755..100644 --- a/RELEASING +++ b/RELEASING @@ -2,7 +2,9 @@ Here are the steps to follow to create a new cairo release: 1) Ensure that there are no local, uncommitted/unpushed modifications. You're probably in a good state if both "git diff - HEAD" and "git log master..origin/master" give no output. + HEAD" and "git log master..origin/master" give no output. Also make + sure you have libglib2.0-doc installed (else you'll get excessive + gtk-doc cross reference warnings in the next step). 2) Verify that the code passes "make distcheck" @@ -111,7 +113,7 @@ Here are the steps to follow to create a new cairo release: 8) Push the newly created tag out to the central tree with a command something like: - git push cairo X.Y.Z + git push origin master X.Y.Z 9) Edit the cairo bugzilla product and add the new version numbers. Note that you need to add two versions. One for the release/snapshot (with @@ -119,12 +121,13 @@ Here are the steps to follow to create a new cairo release: odd micro version). 10) Send a message to cairo-announce@cairographics.org and CC - gnome-announce-list@gnome.org and ftp-release@lists.freedesktop.org - (pr@lwn.net as well for major releases) to announce the new release - using the text provided from "make release-publish", adding the excerpt - from NEWS, your signature, followed by the standard "What is cairo" and - "Where to get more information about cairo" blurbs from README, and - finally the shortlog of all changes since last release, generated by: + cairo@cairographics.org, gnome-announce-list@gnome.org and + ftp-release@lists.freedesktop.org (pr@lwn.net as well for major + releases) to announce the new release using the text provided from + "make release-publish", adding the excerpt from NEWS, your + signature, followed by the standard "What is cairo" and "Where to + get more information about cairo" blurbs from README, and finally + the shortlog of all changes since last release, generated by: git shortlog X.Y.Z... @@ -133,8 +136,3 @@ Here are the steps to follow to create a new cairo release: 11) Edit the cairo wiki to add the announcement to the NEWS page and the front page. (just the parts before your signature). -12) For minor releases (no X.Y change), notify desktop-devel-list@gnome.org - or update the ExternalDependencies page for the current cycle if you - know where it is. Currently it's: - - http://live.gnome.org/TwoPointNineteen/ExternalDependencies |