[cairo-commit] cairo ChangeLog, 1.887, 1.888 NEWS, 1.23,
1.24 RELEASING, 1.17, 1.18 configure.in, 1.123, 1.124
Carl Worth
commit at pdx.freedesktop.org
Sat Aug 13 05:00:22 PDT 2005
Committed by: cworth
Update of /cvs/cairo/cairo
In directory gabe:/tmp/cvs-serv24598
Modified Files:
ChangeLog NEWS RELEASING configure.in
Log Message:
2005-08-13 Carl Worth <cworth at cworth.org>
* NEWS: Added notes for release 0.9.2.
* configure.in: Increment CAIRO_VERSION to 0.9.2 and libtool
versioning to 3:1:1.
* RELEASING: Remove some more 'snapshot' language. Make it more
clear that the libtool versioning numbers need to be updated.
Index: ChangeLog
===================================================================
RCS file: /cvs/cairo/cairo/ChangeLog,v
retrieving revision 1.887
retrieving revision 1.888
diff -u -d -r1.887 -r1.888
--- ChangeLog 13 Aug 2005 11:22:46 -0000 1.887
+++ ChangeLog 13 Aug 2005 12:00:20 -0000 1.888
@@ -1,5 +1,15 @@
2005-08-13 Carl Worth <cworth at cworth.org>
+ * NEWS: Added notes for release 0.9.2.
+
+ * configure.in: Increment CAIRO_VERSION to 0.9.2 and libtool
+ versioning to 3:1:1.
+
+ * RELEASING: Remove some more 'snapshot' language. Make it more
+ clear that the libtool versioning numbers need to be updated.
+
+2005-08-13 Carl Worth <cworth at cworth.org>
+
* src/cairo-pattern.c: Fix unterminated comment that eliminated
cairo_pattern_add_color_stop_rgba.
@@ -17,12 +27,6 @@
2005-08-13 Carl Worth <cworth at cworth.org>
- * NEWS:
- * src/cairo-pattern.c:
- * src/cairo.c:
-
-2005-08-13 Carl Worth <cworth at cworth.org>
-
* src/cairoint.h: Turn the mutex code back on. It looks like the
deadlocks have disappeared as of the cairo_scaled_font_map patch
from two days ago.
@@ -35,10 +39,6 @@
2005-08-13 Carl Worth <cworth at cworth.org>
- * src/cairoint.h:
-
-2005-08-13 Carl Worth <cworth at cworth.org>
-
Minor, cosmetic changes:
* src/cairo-ft-font.c: (_cairo_ft_unscaled_font_lock_face): Reowrd
Index: NEWS
===================================================================
RCS file: /cvs/cairo/cairo/NEWS,v
retrieving revision 1.23
retrieving revision 1.24
diff -u -d -r1.23 -r1.24
--- NEWS 13 Aug 2005 11:17:36 -0000 1.23
+++ NEWS 13 Aug 2005 12:00:20 -0000 1.24
@@ -1,3 +1,79 @@
+Release 0.9.2 (2005-08-13 Carl Worth <cworth at cworth.org>)
+=========================================================
+Release numbering
+-----------------
+ * You will notice that this release jumped from 0.9.0 to 0.9.2. We've
+ decided to use an odd micro version number (eg. 0.9.1) to indicate
+ in-progress development between releases. As soon as 0.9.2 is
+ tagged, the version will be incremented in CVS to 0.9.3 where it
+ will stay until just before 0.9.4 is built, uploaded, and tagged.
+
+ So, even-micro == a released version, odd-micro == something in-between.
+
+Libpixman dependency dropped
+----------------------------
+ * As of this release, the dependency on an internal libpixman has
+ been dropped. Instead, the code from libpixman needed for cairo has
+ been incorporated into the cairo source tree. The motivation for
+ this change is that while cairo's API is stable and ready to be
+ maintained after the 1.0 release, libpixman's API is not, so we do
+ not want to expose it at this time.
+
+ Also, the incorporation of libpixman into cairo also renames all
+ previously-public libpixman symbols in order to avoid any conflict
+ with a future release of libpixman
+
+API additions
+-------------
+ * Macros and functions have been added so that the version of cairo
+ can be queried at either compile-time or at run-time. The version
+ is made available as both a human-readable string and as a single
+ integer:
+
+ CAIRO_VERSION_STRING eg. "0.9.2"
+ CAIRO_VERSION eg. 000902
+
+ const char*
+ cairo_version_string (void); /* eg. "0.9.2" */
+
+ int
+ cairo_version (void); /* eg. 000902 */
+
+ A macro is provided to convert a three-part component version into
+ the encoded single-integer form:
+
+ CAIRO_VERSION_ENCODE(X,Y,Z)
+
+ For example, the CAIRO_VERSION value of 000902 is obtained as
+ CAIRO_VERSION_ENCODE(0,9,2). The intent is to make version
+ comparisons easy, either at compile-time:
+
+ #if CAIRO_VERSION >= CAIRO_VERSION_ENCODE(0,9,2)
+ ...
+ #endif
+
+ Or at run-time:
+
+ if (cairo_version() >= CAIRO_VERSION_ENCODE(0,9,2)) { /* ... */ }
+
+Thread safety
+-------------
+ * This release adds pthread-based locking (when available) to make
+ the caches used by cairo safe for threaded programs. Some may
+ remember a failed experiment with this locking between the 0.5.1
+ and 0.5.2 snapshots, (where even single-threaded programs that
+ linked with -lpthread would deadlock). We believe that that problem
+ has been fixed, so we are looking forward to testing and reports
+ from users with threaded applications.
+
+Bug fixes
+---------
+ * The XCB and Quartz backends failed to compiled in the 0.9.0 release
+ due to minor syntax errors. These have now been fixed.
+
+ * Various crashes in glitz and pixman due to size 0 glyphs have been
+ fixed.
+
Release 0.9.0 (2005-08-08 Carl Worth <cworth at cworth.org>)
=========================================================
Soname change
@@ -17,7 +93,7 @@
release series have distinct library versioning.
All future releases will use the library versioning to properly
- indicate comptaibility between releases. So, any application
+ indicate compatibility between releases. So, any application
re-compiled now to work with the 0.9.0 will not need to be
recompiled when a compatible 1.0 release of cairo is made in the
future.
@@ -80,7 +156,7 @@
Bug fixes
---------
* Fix the unbounded operators to actually produce a correct result,
- (previously the results were artificially restricited to the
+ (previously the results were artificially restricted to the
bounding box of whatever shape was being drawn rather than
extending out infinitely). The fixed operators are:
@@ -103,7 +179,7 @@
than NULL on error.
* cairo_set_font_face fixed to not crash if given a NULL font face,
- (which is the documented interface for restoring the defauly font
+ (which is the documented interface for restoring the default font
face).
* Fix xlib glyphset caching to not try to free a NULL glyph.
@@ -235,7 +311,7 @@
cairo_xlib_surface_set_drawable
- which allos the target drawable for an xlib cairo_surface_t to be
+ which allows the target drawable for an xlib cairo_surface_t to be
changed to another with the same format, screen, and display. This
is necessary in certain double-buffering techniques.
@@ -300,7 +376,7 @@
* Fix glyph caches to not eject entries that might be immediately
needed, (fixing intermittent crashes when rendering text).
-* Fix all memory leaks found by running "make check-valigrind".
+* Fix all memory leaks found by running "make check-valgrind".
ATSUI backend changes
---------------------
@@ -1242,7 +1318,7 @@
curve_to callback. Instead, all curved portions of the path will be
converted to line segments, (within the current tolerance value). This
can be handy for doing things like text-on-path without having to
-manually interpolate bezier splines.
+manually interpolate Bézier splines.
New XCB backend
---------------
Index: RELEASING
===================================================================
RCS file: /cvs/cairo/cairo/RELEASING,v
retrieving revision 1.17
retrieving revision 1.18
diff -u -d -r1.17 -r1.18
--- RELEASING 13 Aug 2005 07:20:45 -0000 1.17
+++ RELEASING 13 Aug 2005 12:00:20 -0000 1.18
@@ -1,9 +1,4 @@
-So far, cairo hasn't reached an initial release. But we can still form
-good habits now by practicing the release process with the current
-snapshots.
-
-A new snapshot is needed whenever significant new features or bug
-fixes are committed. Here are the steps to follow:
+Here are the steps to follow to create a new cairo release:
1) Ensure that there are no local, uncommitted modifications. The best
thing to do here may be to begin with a fresh checkout from CVS:
@@ -39,7 +34,8 @@
find src/ -name '*.h' -not -name '*-private.h' -not -name 'cairoint.h' | \
xargs cvs diff -r RELEASE_X_Y_Z
-4) Increment cairo_version_{minor|micro} in configure.in:
+4) Increment cairo_version_{minor|micro} and LT_{CURRENT|VERSION|AGE}
+ in configure.in:
If there are backward-incompatible changes in the API, stop
now and don't release. Go back and fix the API instead. Cairo
Index: configure.in
===================================================================
RCS file: /cvs/cairo/cairo/configure.in,v
retrieving revision 1.123
retrieving revision 1.124
diff -u -d -r1.123 -r1.124
--- configure.in 13 Aug 2005 10:26:18 -0000 1.123
+++ configure.in 13 Aug 2005 12:00:20 -0000 1.124
@@ -5,7 +5,7 @@
# An even micro number indicates a released version.
m4_define(cairo_version_major, 0)
m4_define(cairo_version_minor, 9)
-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,16 +19,16 @@
# libtool shared library version
# Increment if the interface has additions, changes, removals.
-LT_CURRENT=2
+LT_CURRENT=3
# Increment any time the source changes; set to
# 0 if you increment CURRENT
-LT_REVISION=0
+LT_REVISION=1
# 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=0
+LT_AGE=1
dnl ===========================================================================
More information about the cairo-commit
mailing list