Do

Do 0.95 "Classical Analysis"

Clean up some of the remaining technical problems with core - particularly, make core more resilient in the face of misbehaving plugins.

Milestone information

Project:
Do
Series:
trunk
Version:
0.95
Code name:
Classical Analysis
Released:
2013-12-29  
Registrant:
Chris Halse Rogers
Release registered:
2013-12-29
Active:
Yes. Drivers can target bugs and blueprints to this milestone.  

Download RDF metadata

Activities

Assigned to you:
No blueprints or bugs assigned to you.
Assignees:
No users assigned to blueprints and bugs.
Blueprints:
No blueprints are targeted to this milestone.
Bugs:
No bugs are targeted to this milestone.

Download files for this release

After you've downloaded a file, you can verify its authenticity using its MD5 sum or signature. (How do I verify a download?)

File Description Downloads
download icon gnome-do-0.95.tar.gz (md5, sig) release tarball 348
last downloaded today
Total downloads: 348

Release notes 

Drop use of deprecated gnome-sharp libraries.

Now builds with Mono 3.0!

Compatibility with various GTK+ 3.0 file paths.

Major clean up of the Cairo code - resolved hundreds of deprecation warnings, and many many places where we were abusing the GC.

The next release should see a transition to GTK# 3.0.

Changelog 

View the full changelog

* Drop use of deprecated gnome-sharp libraries
 * Switch to GIO#
 * Now builds with Mono 3.0
 * Prevent users from setting known-broken keybindings
 * Allow regular plugins to trigger their own refresh cycle
 * Search in, and prefer, various GTK+ 3.0 locations
 * Clean up hundreds of deprecation warnings in the Cairo code
 * Clean up many, many instances where we relied on the finaliser
   to handle cleanup of Cairo objects. The GC should love us much
   more now!
 * Add a DebugItem action when debugging is enabled, to dump a bunch
   of useful information about an Item to Do's log

0 blueprints and 0 bugs targeted

There are no feature specifications or bug tasks targeted to this milestone. The project's maintainer, driver, or bug supervisor can target specifications and bug tasks to this milestone to track the things that are expected to be completed for the release.

This milestone contains Public information
Everyone can see this information.