desktopcouch 0.3

karmic feature freeze.

Milestone information

Project:
desktopcouch
Series:
trunk
Version:
0.3
Released:
 
Registrant:
Elliot Murphy
Release registered:
Active:
No. Drivers cannot 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 desktopcouch-0.3.tar.gz (md5, sig) desktopcouch 0.3, really. 18
last downloaded 45 weeks ago
Total downloads: 18

Release notes 

In this version, we add a replication daemon, but there is nothing that supports it at release time. The pairing tool does not write configuration information, Ubuntu One servers do not yet support cloud replication, and couchdb is locked to localhost addresses for security reasons. To keep misunderstanding to a minimum, the pairing tool does not let a user try to pair local addresses.

desktopcouch creates two-legged oauth token, for replication purposes (although compulsory oauth is not enabled).

Also new is contacts picker, a utility UI widget suggested for general use for deskcouch-using apps.

Another new UI widget is couchgrid, which aims to make editing arbitrary couch databases easy for apps.

desktopcouch will now automatically create databases and design documents for you on startup by inspecting the filesystem, meaning that you do not need to check in your application whether your views exist. See the README for further details.

Additionally, code to discover the port the desktopcouch server is running on is simplified and should run on any Unix.

Changelog 

This release does not have a changelog.

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.