[cairo-commit] 5 commits - configure.in Makefile.am NEWS RELEASING
test/Makefile.am
Carl Worth
cworth at kemper.freedesktop.org
Tue Apr 25 09:17:29 PDT 2006
Makefile.am | 6 +-
NEWS | 113 +++++++++++++++++++++++++++++++++++++++++++++++++++++++
RELEASING | 9 ++--
configure.in | 6 +-
test/Makefile.am | 7 ---
5 files changed, 125 insertions(+), 16 deletions(-)
New commits:
diff-tree d5dd5e6ebc43db103071b8b86284f4e38572b053 (from e89de1030eae71da469c9c4c7176d0fdfe0df595)
Author: Carl Worth <cworth at cworth.org>
Date: Tue Apr 25 09:12:30 2006 -0700
Remove from EXTRA_DIST reference images which don't exist
diff --git a/test/Makefile.am b/test/Makefile.am
index d348ab2..e4ca68e 100644
--- a/test/Makefile.am
+++ b/test/Makefile.am
@@ -112,7 +112,6 @@ endif
EXTRA_DIST = \
a8-mask-ref.png \
a8-mask-rgb24-ref.png \
-caps-joins-ps-rgb24-ref.png \
caps-joins-ref.png \
caps-joins-rgb24-ref.png \
caps-joins-alpha-ref.png \
@@ -123,12 +122,10 @@ clip-all-ref.png \
clip-all-rgb24-ref.png \
clip-fill-rule-ref.png \
clip-fill-rule-pixel-aligned-ref.png \
-clip-nesting-ps-rgb24-ref.png \
clip-nesting-ref.png \
clip-nesting-rgb24-ref.png \
clip-operator-ref.png \
clip-operator-rgb24-ref.png \
-clip-twice-ps-rgb24-ref.png \
clip-twice-ref.png \
clip-twice-rgb24-ref.png \
composite-integer-translate-over-ref.png \
@@ -145,11 +142,8 @@ dash-caps-joins-ref.png \
dash-caps-joins-rgb24-ref.png \
dash-offset-negative-ref.png \
dash-offset-negative-rgb24-ref.png \
-dash-offset-negative-ps-rgb24-ref.png \
dash-zero-length-ref.png \
dash-zero-length-rgb24-ref.png \
-extend-reflect-ref.png \
-extend-reflect-rgb24-ref.png \
fill-and-stroke-ref.png \
fill-and-stroke-rgb24-ref.png \
fill-rule-ref.png \
@@ -226,7 +220,6 @@ translate-show-surface-ref.png \
translate-show-surface-rgb24-ref.png \
trap-clip-ref.png \
trap-clip-rgb24-ref.png \
-unantialiased-shapes-ps-rgb24-ref.png \
unantialiased-shapes-ref.png \
unantialiased-shapes-rgb24-ref.png \
unbounded-operator-ref.png \
diff-tree e89de1030eae71da469c9c4c7176d0fdfe0df595 (from 3d6cdc996f3a3f4d54d0d8926daa3973d69e4dc2)
Author: Carl Worth <cworth at cworth.org>
Date: Tue Apr 25 08:56:23 2006 -0700
Change release targets as appropriate for a snapshot, not a release.
The big change here is to change the upload directory to be the snapshots directory
rather than the releases directory. We also use make dist rather than make distcheck
since there are currently a few tests still failing.
diff --git a/Makefile.am b/Makefile.am
index 165f9c3..6ff72e7 100644
--- a/Makefile.am
+++ b/Makefile.am
@@ -66,8 +66,8 @@ $(srcdir)/ChangeLog:
RELEASE_UPLOAD_HOST = cairographics.org
RELEASE_UPLOAD_BASE = /srv/cairo.freedesktop.org/www
-RELEASE_UPLOAD_DIR = $(RELEASE_UPLOAD_BASE)/releases
-RELEASE_URL_BASE = http://cairographics.org/releases
+RELEASE_UPLOAD_DIR = $(RELEASE_UPLOAD_BASE)/snapshots
+RELEASE_URL_BASE = http://cairographics.org/snapshots
RELEASE_ANNOUNCE_LIST = cairo-announce at cairographics.org (and CC gnome-announce-list at gnome.org)
MANUAL_DATED = cairo-manual-`date +%Y%m%d`
@@ -136,7 +136,7 @@ release-remove-old:
release-cleanup-group-sticky:
find . -type f | xargs chmod g-s
-release-check: release-verify-soname-major release-verify-even-micro release-verify-newer release-remove-old release-cleanup-group-sticky distcheck
+release-check: release-verify-soname-major release-verify-even-micro release-verify-newer release-remove-old release-cleanup-group-sticky dist
release-upload: release-check $(tar_file) $(sha1_file) $(gpg_file)
mkdir -p releases
diff-tree 3d6cdc996f3a3f4d54d0d8926daa3973d69e4dc2 (from 68c5382b6cdc442f3057b8e4eed2dfe7084ef7f1)
Author: Carl Worth <cworth at cworth.org>
Date: Tue Apr 25 08:54:59 2006 -0700
Add release vs. snapshot distinction to version increment instructions
diff --git a/RELEASING b/RELEASING
index e0693df..896694b 100644
--- a/RELEASING
+++ b/RELEASING
@@ -44,8 +44,9 @@ Here are the steps to follow to create a
So cairo_version_major will not be incremented unless we come
up with a new versioning scheme to take advantage of it.
- If there are API additions, then increment
- cairo_version_minor and reset cairo_version_micro to 0.
+ If there are API additions, then increment cairo_version_minor
+ and reset cairo_version_micro to 0. NOTE: The minor version is
+ only incremented for releases, not for snapshots.
Otherwise, (ie. there are only bug fixes), increment
cairo_version_micro to the next larger (even) number.
diff-tree 68c5382b6cdc442f3057b8e4eed2dfe7084ef7f1 (from 3002c6cc8b4722a324de27a20f04ae810b6dc573)
Author: Carl Worth <cworth at cworth.org>
Date: Tue Apr 25 08:51:08 2006 -0700
Increment CAIRO_VERSION to 1.1.2 and libtool versioning to 6:0:4
diff --git a/configure.in b/configure.in
index 1435ed8..d4970c3 100644
--- a/configure.in
+++ b/configure.in
@@ -5,7 +5,7 @@ AC_PREREQ(2.54)
# An even micro number indicates a released version.
m4_define(cairo_version_major, 1)
m4_define(cairo_version_minor, 1)
-m4_define(cairo_version_micro, 1)
+m4_define(cairo_version_micro, 2)
AC_INIT([cairo],
cairo_version_major.cairo_version_minor.cairo_version_micro,
@@ -19,7 +19,7 @@ dnl ====================================
# libtool shared library version
# Increment if the interface has additions, changes, removals.
-LT_CURRENT=5
+LT_CURRENT=6
# Increment any time the source changes; set to
# 0 if you increment CURRENT
@@ -28,7 +28,7 @@ LT_REVISION=0
# Increment if any interfaces have been added; set to 0
# if any interfaces have been removed. removal has
# precedence over adding, so set to 0 if both happened.
-LT_AGE=3
+LT_AGE=4
dnl ===========================================================================
diff-tree 3002c6cc8b4722a324de27a20f04ae810b6dc573 (from a0df6fa696d44533adec1ecec7398e851b2eb37a)
Author: Carl Worth <cworth at cworth.org>
Date: Tue Apr 25 08:44:45 2006 -0700
Add some notes for the 1.1.2 snapshot
diff --git a/NEWS b/NEWS
index 5f552a7..8504d5b 100644
--- a/NEWS
+++ b/NEWS
@@ -1,3 +1,116 @@
+Snapshot 1.1.2 (2006-04-25 Carl Worth <cworth at cworth.org>)
+==========================================================
+This is the first in a series of snapshots working toward the upcoming
+1.2 release of cairo. (Subsequent snapshot will use sucessive even
+numbers for the third digit, 1.1.4, 1.1.6, etc.) This snapshot is
+backwards-compatible with the 1.0 series---it makes a few API
+additions but does not remove any API.
+
+PostScript and PDF backends are no longer "experimental"
+--------------------------------------------------------
+The major theme of the 1.2 release is improved PostScript and PDF
+backends for cairo. Unlike the 1.0 series, in the 1.2 series these
+backends will not be marked as experimental and will be enabled by
+default. We encourage people to test this snapshot and the PS/PDF
+backends in particular as much as possible.
+
+The PostScript and PDF output is not yet ideal.
+
+ * One major problem with the PostScript output is that image
+ fallbacks are used more often than strictly necessary, and the
+ image fallbacks are at a lower resolution than desired, (the
+ cairo_ps_surface_set_dpi call is ignored).
+
+ * The major drawback of the current PDF backend implementation is
+ its text support. Every glyph is represented by a filled path in
+ the PDF file. The causes file sizes to be much larger and
+ rendering to be much slower than desired.
+
+It is anticipated that both of these shortcomings will see some
+improvements before the final 1.2 release.
+
+In spite of those shortcomings, we hope that the PS and PDF backends
+will yield faithful results for pretty much any cairo operations you
+can throw at them. Please let us know if you are getting obviously
+"different" results from the PS/PDF backends than from the image or
+xlib backends.
+
+Other new experimental backends
+-------------------------------
+This snapshot includes three new backends that did not exist in the
+1.0 series:
+
+ * beos backend
+
+ * directfb backend
+
+ * svg backend
+
+These are all currently marked "experimental" and are disabled by
+default. But the SVG backend in particular has seen a lot of recent
+development and is very close to passing the entire cairo test
+suite. It is possible that this backend will become a fully supported
+backend by the time of the cairo 1.2 release.
+
+Public API additions
+--------------------
+There have been a few new API functions added to cairo, including:
+
+New get_type functions for querying sub-types of object:
+
+ cairo_surface_get_type
+ cairo_pattern_get_type
+ cairo_font_face_get_type
+ cairo_scaled_font_get_type
+
+More convenience in working with cairo_scaled_font_t with new getter
+functions:
+
+ cairo_scaled_font_get_font_face
+ cairo_scaled_font_get_font_matrix
+ cairo_scaled_font_get_ctm
+ cairo_scaled_font_get_font_options
+
+As well as a convenience function for setting a scaled font into a
+cairo context:
+
+ cairo_set_scaled_font
+
+and a function to allow text extents to be queried directly from a
+scaled font, (without requiring a cairo_surface_t or a cairo_t):
+
+ cairo_scaled_font_text_extents
+
+These new scaled font functions were motivated by the needs of the
+pango library.
+
+Finally, a new path-construction function was added which clears the
+current point in preparation for a new sub path. This makes cairo_arc
+easier to use in some situations:
+
+ cairo_new_sub_path
+
+Before the 1.2 release is final we do still plan a few more API
+additions specifically motivated by the needs of Mozilla/Firefox.
+
+Optimizations and bug fixes
+---------------------------
+Shortly after the 1.0 maintenance series branched off the mainline
+there was a major rework of the cairo font internals. This should
+provide some good performance benefits, but it's also another area
+people should look at closely for potential regressions.
+
+There has not yet been any widespread, systematic optimization of
+cairo, but various performance improvements have been made, (and some
+of them are fairly significant). So if some things seem faster than
+1.0 then things are good. If there are any performance regressions
+compared to 1.0 then there is a real problem and we would like to hear
+about that.
+
+There has been a huge number of bug fixes---too many to mention in
+detail. Again, things should be better, and never worse compared to
+1.0. Please let us know if your testing shows otherwise.
+
Release 1.0.2 (2005-10-03 Carl Worth <cworth at cworth.org>)
=========================================================
For each bug number XXXX below, see:
diff --git a/RELEASING b/RELEASING
index 49dd82c..e0693df 100644
--- a/RELEASING
+++ b/RELEASING
@@ -1,7 +1,9 @@
Here are the steps to follow to create a new cairo release:
1) Ensure that there are no local, uncommitted modifications.
- It's probably good enough if "git diff" doesn't output anything.
+ It's probably good enough if "git diff HEAD" doesn't output
+ anything and your "master" and "origin" branchs are at the current
+ revision.
2) Verify that the code passes "make distcheck"
More information about the cairo-commit
mailing list