Commit 588e6e83 authored by Richard Hughes's avatar Richard Hughes

Release version 2.91.5

parent 49a77165
Version 2.91.5
~~~~~~~~~~~~~~
Released: 2011-01-11
* Translations
- Added UG translation (Gheyret T.Kenji)
- Added Vietnamese translation (Nguyễn Thái Ngọc Duy)
- Updated Estonian translation (Ivar Smolin)
- Updated Italian translation (Francesco Groccia)
- Updated Norwegian bokmål translation (Torstein Adolf Winterseth
- Updated Punjabi translation (A S Alam)
- Updated Slovenian translation (Andrej Žnidaršič)
- Updated Swedish translation (Daniel Nylander)
- Updated Traditional Chinese translation(Hong Kong and Taiwan) (Chao-Hsiung Liao)
* Bugfix:
- Fix GTK3 API break; gdk_cursor_unref (Richard Hughes)
- Fix GTK3 API break; gdk_window_foreign_new_for_display() no longer exists (Richard Hughes)
- Fix GTK3 API break; gdk_x11_drawable_get_xid() no longer exists (Richard Hughes)
- GUdev now requires us to set G_UDEV_API_IS_SUBJECT_TO_CHANGE to be able to build (Richard Hughes)
Version 2.91.3
~~~~~~~~~~~~~~
Released: 2010-12-01
......
......@@ -2,9 +2,9 @@ PackageKit Release Notes
1. Write NEWS entries for gnome-color-manager in the same format as usual.
Version 2.91.4
Version 2.91.5
~~~~~~~~~~~~~~
Released: 2010-xx-xx
Released: 2011-xx-xx
* Translations
* New Features:
......@@ -14,8 +14,8 @@ git shortlog GNOME_COLOR_MANAGER_2_91_3.. | grep -i -v trivial | grep -v Merge |
3. Commit changes in gnome-color-manager git:
git commit -a -m "Release version 2.91.4"
git tag -s GNOME_COLOR_MANAGER_2_91_4 -m "==== Version 2.91.4 ===="
git commit -a -m "Release version 2.91.5"
git tag -s GNOME_COLOR_MANAGER_2_91_5 -m "==== Version 2.91.5 ===="
<enter password>
git push --tags
git push
......
......@@ -3,7 +3,7 @@ AC_PREREQ(2.63)
m4_define([gcm_major_version], [2])
m4_define([gcm_minor_version], [91])
m4_define([gcm_micro_version], [4])
m4_define([gcm_micro_version], [5])
m4_define([gcm_version],
[gcm_major_version.gcm_minor_version.gcm_micro_version])
......
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment