[cairo-commit] 5 commits - cairo-version.h NEWS RELEASING
Bryce Harrington
bryce at kemper.freedesktop.org
Fri Dec 11 00:54:55 PST 2015
NEWS | 95 ++++++++++++++++++++++++++++++++++++++++++++++++++++++--
RELEASING | 84 +++++++++++++++++++++++++++++++++----------------
cairo-version.h | 2 -
3 files changed, 150 insertions(+), 31 deletions(-)
New commits:
commit db8a7f1697c49ae4942d2aa49eed52dd73dd9c7a
Author: Bryce Harrington <bryce at osg.samsung.com>
Date: Fri Dec 11 00:45:02 2015 -0800
1.15.2 release
diff --git a/NEWS b/NEWS
index 41598d8..b320af6 100644
--- a/NEWS
+++ b/NEWS
@@ -1,3 +1,95 @@
+Release 1.15.2 (2015-12-10 Bryce Harrington <bryce at osg.samsung.com>)
+========================================================================
+This release is largely a rollup to include a variety of fixes that
+didn't make the cut for the stable 1.14.2 and 1.14.4 releases, as well
+as all the fixes from those releases. Notably this includes a highly
+requested new API for Win32 surfaces.
+
+For a complete log of changes since the last release, please see:
+
+ http://cairographics.org/releases/ChangeLog.1.15.2
+
+Features
+--------
+None
+
+API Changes
+-----------
+
+ cairo_win32_surface_create_with_format
+
+ Added a cairo API to set up Win32 surfaces for HDC with alpha channels.
+
+Dependency Changes
+------------------
+None
+
+Performance Optimizations
+-------------------------
+None
+
+Bug Fixes
+---------
+* All the bug fixes from 1.14.2, 1.14.4, and 14.6
+
+* Fix xcb/xlib compilation and calls. Make image boxes behave when SHM
+ is not available.
+
+* Fix various issues with printing and transparent images on Win32.
+
+* Fix thin lines that don't show up when printing in Inkscape due to
+ overly aggressive culling.
+ (Bug #77298)
+
+* Fix broken printing via pdf when glyph 0 is used for rendering,
+ resulting in missing spaces and letters.
+ (Bug #89082)
+
+* Fix crash for certain glyphs in opentype fonts.
+ (Bug #91902)
+
+* Fix incorrect rendering of SVG paths with more than one subpath. If
+ more than one trap is passed in then it's guaranteed that the returned
+ traps will have their left edge to the left of their right edge, but
+ if only one trap is passed in then the function always returns without
+ doing anything.
+ (Bug #90984)
+
+* Improve rendering with Quarts to better match pixman's blending and
+ filtering behavior.
+
+
+Release 1.14.6 (2015-12-09 Bryce Harrington <bryce at osg.samsung.com>)
+========================================================================
+Simple bugfix release to fix one Windows issue.
+
+For a complete log of changes since 1.14.4, please see:
+
+ http://cairographics.org/releases/ChangeLog.1.14.6
+
+Features
+--------
+None
+
+API Changes
+-----------
+None
+
+Dependency Changes
+------------------
+None
+
+Performance Optimizations
+-------------------------
+None
+
+Bug Fixes
+---------
+* Fix failure on Windows due to reference of the function
+ cairo_win32_surface_create_with_format(), which isn't included in the
+ 1.14.4 release. (Bug #92771)
+
+
Release 1.14.4 (2015-10-28 Bryce Harrington <bryce at osg.samsung.com>)
========================================================================
Just in time for Halloween we see another bug-fix release for Cairo.
@@ -17,8 +109,7 @@ None
API Changes
-----------
-* Add cairo_win32_surface_create_with_format() API to set up a Win32
- psurface for an HDX with an alpha channel.
+None
Dependency Changes
------------------
diff --git a/cairo-version.h b/cairo-version.h
index 57deff0..feedcc5 100644
--- a/cairo-version.h
+++ b/cairo-version.h
@@ -3,6 +3,6 @@
#define CAIRO_VERSION_MAJOR 1
#define CAIRO_VERSION_MINOR 15
-#define CAIRO_VERSION_MICRO 1
+#define CAIRO_VERSION_MICRO 2
#endif
commit 6cd5a188e3db142089020e3c50ef280195655fec
Author: Bryce Harrington <bryce at osg.samsung.com>
Date: Thu Dec 10 21:00:29 2015 -0800
RELEASING: Clarify snapshot numbering rules
diff --git a/RELEASING b/RELEASING
index 0954cf7..2d4f5fc 100644
--- a/RELEASING
+++ b/RELEASING
@@ -52,27 +52,30 @@ Here are the steps to follow to create a new cairo release:
development tree between Minor releases, as desired.
Cairo uses even numbers for official releases, and odd numbers
- for development snapshots. Thus, for a Minor release the
- version numbers should be:
+ for development snapshots. Thus, for a Minor release it would
+ be:
- LAST_RELEASE="X.Y.Z" # e.g. 1.14.4
- THIS_RELEASE="X.Y+2.0" # e.g. 1.16.0
+ LAST_RELEASE="X.Y.Z" # e.g. 1.12.0
+ THIS_RELEASE="X.Y+2.0" # e.g. 1.14.0
- While for a micro release it would be:
+ While for a Micro release the version numbers should be:
- LAST_RELEASE="X.Y.Z" # e.g. 1.16.0
- THIS_RELEASE="X.Y.Z+2" # e.g. 1.16.2
+ LAST_RELEASE="X.Y.Z" # e.g. 1.14.0
+ THIS_RELEASE="X.Y.Z+2" # e.g. 1.14.2
- Snapshots are similar but have odd minor versions, e.g.:
+ Snapshots are similar but have odd minor versions. Also, the
+ first snapshot release in a new series will be .2 rather than
+ .0, e.g.:
- LAST_RELEASE="X.Y.Z" # e.g. 1.16.2
- THIS_RELEASE="X.Y+1.0" # e.g. 1.17.0
+ LAST_RELEASE="X.Y.Z" # e.g. 1.14.0
+ THIS_RELEASE="X.Y+1.0" # e.g. 1.15.2
and subsequent snapshots in that series are just normal micro
releases:
- LAST_RELEASE="X.Y.Z" # e.g. 1.17.0
- THIS_RELEASE="X.Y.Z+2" # e.g. 1.17.2
+ LAST_RELEASE="X.Y.Z" # e.g. 1.15.2
+ THIS_RELEASE="X.Y.Z+2" # e.g. 1.15.4
+
4) Fill out an entry in the NEWS file
commit 2dc0149ddea214c925f4a38abc65169242e72432
Author: Bryce Harrington <bryce at osg.samsung.com>
Date: Wed Dec 9 16:25:20 2015 -0800
RELEASING: Drop inclusion of boilerplate in news messages
Looking back at past release announcements, it's been a long time since
we included the About Cairo bits. This info is easily located on the
website and elsewhere, no need for the redundant data in the
announcement too.
diff --git a/RELEASING b/RELEASING
index da5b7b0..0954cf7 100644
--- a/RELEASING
+++ b/RELEASING
@@ -181,14 +181,10 @@ Here are the steps to follow to create a new cairo release:
cairo at cairographics.org, gnome-announce-list at gnome.org and
ftp-release at lists.freedesktop.org (pr at 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
+ "make release-publish", adding the excerpt from NEWS and
the shortlog of all changes since last release, generated by:
git shortlog ${LAST_RELEASE}...
11) Add the announcement to the NEWS page and the front page.
- (just the parts before your signature).
-
commit 4ab379c744b2c0d5256692307770846eccd41dce
Author: Bryce Harrington <bryce at osg.samsung.com>
Date: Wed Dec 9 14:45:55 2015 -0800
RELEASING: Make X.Y.Z versions less ambiguous
The document uses X.Y.Z to sometimes mean the previous release version,
and in other places to mean the upcoming next release version. Identify
these more explicitly.
diff --git a/RELEASING b/RELEASING
index ee4a6e3..da5b7b0 100644
--- a/RELEASING
+++ b/RELEASING
@@ -43,14 +43,44 @@ Here are the steps to follow to create a new cairo release:
DISPLAY= CAIRO_TEST_TARGET=" "
-3) Fill out an entry in the NEWS file
+3) Decide what the new version number for the release will be.
+
+ There are three types of releases: Minor, Micro, and
+ Snapshot. Micro releases should be only bugfixes and no API
+ additions. If there are API additions consider making a Minor
+ release. Snapshot releases can be done of the current
+ development tree between Minor releases, as desired.
+
+ Cairo uses even numbers for official releases, and odd numbers
+ for development snapshots. Thus, for a Minor release the
+ version numbers should be:
+
+ LAST_RELEASE="X.Y.Z" # e.g. 1.14.4
+ THIS_RELEASE="X.Y+2.0" # e.g. 1.16.0
+
+ While for a micro release it would be:
+
+ LAST_RELEASE="X.Y.Z" # e.g. 1.16.0
+ THIS_RELEASE="X.Y.Z+2" # e.g. 1.16.2
+
+ Snapshots are similar but have odd minor versions, e.g.:
+
+ LAST_RELEASE="X.Y.Z" # e.g. 1.16.2
+ THIS_RELEASE="X.Y+1.0" # e.g. 1.17.0
+
+ and subsequent snapshots in that series are just normal micro
+ releases:
+
+ LAST_RELEASE="X.Y.Z" # e.g. 1.17.0
+ THIS_RELEASE="X.Y.Z+2" # e.g. 1.17.2
+
+
+4) Fill out an entry in the NEWS file
Sift through the logs since the last release. This is most
easily done with a command such as:
- git log --stat X.Y.Z..
-
- where X.Y.Z is the previous release version.
+ git log --stat ${LAST_RELEASE}..
Summarize major changes briefly in a style similar to other
entries in NEWS. Take special care to note any additions in
@@ -61,12 +91,12 @@ Here are the steps to follow to create a new cairo release:
find src/ -name '*.h' ! -name '*-private.h' \
! -name 'cairoint.h' ! -name 'cairo-*features*.h' | \
- xargs git diff X.Y.Z.. --
+ xargs git diff ${LAST_RELEASE}.. --
Include a link to the incremental ChangeLog for this release,
which we'll be uploading in a later step:
- http://cairographics.org/releases/ChangeLog.X.Y.Z
+ http://cairographics.org/releases/ChangeLog.${THIS_RELEASE}
4) Increment cairo_version_{minor|micro} in cairo-version.h:
@@ -102,11 +132,11 @@ Here are the steps to follow to create a new cairo release:
* Sign the sha1sum using your GPG setup (asks for your GPG password)
* scp the three files to appear on http://cairographics.org/releases
* Generate a versioned manual and upload it to appear as both:
- http://cairographics.org/manual-X.Y.Z
+ http://cairographics.org/manual-${THIS_RELEASE}
http://cairographics.org/manual
* Place local copies of the three files in the releases directory
* Create a LATEST-package-version file (after deleting any old one)
- * Tag the entire source tree with a tag of the form X.Y.Z, and sign
+ * Tag the entire source tree with a ${THIS_RELEASE} tag, and sign
the tag with your GPG key (asks for your GPG password, and you
may need to set GIT_COMMITTER_NAME and GIT_COMMITTER_EMAIL to match
your public-key's setting or this fails.)
@@ -117,26 +147,27 @@ Here are the steps to follow to create a new cairo release:
Upload the incremental ChangeLog generated by the above:
scp ChangeLog.cache-X.Y.Z-1.. \
- cairographics.org:/srv/cairo.freedesktop.org/www/releases/ChangeLog.cairo-X.Y.Z
+ cairographics.org:/srv/cairo.freedesktop.org/www/releases/ChangeLog.cairo-${THIS_RELEASE}
To undo a release-publish, before you've sent any emails or
pushed changes to master, delete the locally created tag (git
- tag -d X.Y.Z); then log into the webserver, repoint the manual
- and LATEST-cairo-X.Y.Z symlinks to the previous versions, remove
- manual-X.Y.Z and release/cairo-1.14.4.
+ tag -d ${THIS_RELEASE}); then log into the webserver, repoint
+ the manual and LATEST-cairo-${THIS_RELEASE} symlinks to the
+ previous versions, remove manual-${THIS_RELEASE} and
+ release/cairo-${THIS_RELEASE}.
7) Update trunk (or the stable branch) version number.
- For micro releases (X.Y.Z), increment cairo_version_micro to the next
- larger (odd) number in cairo-version.h, commit, and push.
+ For Micro releases (X.Y.Z), increment cairo_version_micro to the
+ next larger (odd) number in cairo-version.h, commit, and push.
- For minor releases (X.Y.0), increment cairo_version_minor to the next
- larger (odd) number, and set cairo_version_micro to 1. Then commit
- and push.
+ For Minor releases (X.Y.0), increment cairo_version_minor to the
+ next larger (odd) number, and set cairo_version_micro to 1. Then
+ commit and push.
8) Push the new tag out to the central tree with a command like:
- git push origin master X.Y.Z
+ git push origin master ${THIS_RELEASE}
9) Edit the cairo bugzilla product and add the new version numbers.
@@ -155,9 +186,7 @@ Here are the steps to follow to create a new cairo release:
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...
-
- where X.Y.Z is the last released version.
+ git shortlog ${LAST_RELEASE}...
11) Add the announcement to the NEWS page and the front page.
commit c7822e6107a207057ac4a6a4c2f2265c31c1a2b9
Author: Bryce Harrington <bryce at osg.samsung.com>
Date: Wed Dec 9 14:44:26 2015 -0800
RELEASING: Fix misspelling in last commit
diff --git a/RELEASING b/RELEASING
index 0d1bc34..ee4a6e3 100644
--- a/RELEASING
+++ b/RELEASING
@@ -146,14 +146,14 @@ Here are the steps to follow to create a new cairo release:
10) Send out an announcement message.
- Semd a message to cairo-announce at cairographics.org and CC
+ Send a message to cairo-announce at cairographics.org and CC
cairo at cairographics.org, gnome-announce-list at gnome.org and
ftp-release at lists.freedesktop.org (pr at 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:
+ 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...
More information about the cairo-commit
mailing list