The couchdb model
changes<http://oss.openplans.org/melkjug/changeset?new=2312%40melk.model%2Ftrunk&old=2300%40melk.model%2Ftrunk>
and
sql model changes <http://oss.openplans.org/melkjug/changeset/2323>, along
with a couchdb 
migration<http://oss.openplans.org/melkjug/browser/melk.model/trunk/melk/model/couchdb/migrations/useruri.py>,
have been checked into trunk. I've been testing locally and things are
looking so far so good. Please let me know if you experience any problems.
--Josh


On Thu, May 28, 2009 at 6:07 PM, Joshua Bronson <[email protected]> wrote:

> just wanted to point this out to the dev list in request for your scrutiny
> and collaboration.
>
>
> ---------- Forwarded message ----------
> From: Melkjug Trac <[email protected]>
> Date: Thu, May 28, 2009 at 6:02 PM
> Subject: Re: [Melk Trac] #422: users should have uris which persist across
> registration
> To: [email protected], [email protected]
> Cc: [email protected]
>
>
> #422: users should have uris which persist across registration
>
> ---------------------+------------------------------------------------------
>  Reporter:  jab      |       Owner:  ltucker
>     Type:  defect   |      Status:  new
>  Priority:  none     |   Milestone:  0.6
> Component:  melkjug  |     Version:
>  Severity:  none     |    Keywords:
> Blockedby:           |    Blocking:
>  Related:           |
>
> ---------------------+------------------------------------------------------
>
> Comment(by jab):
>
>  i've got some work on this on github, see
>  http://github.com/jab/melkjug/tree/useruri and
>  http://github.com/jab/melk.model/tree/useruri. user smoke tests are
>  passing with the couchdb model, SQL model is still TODO. no migration yet.
>
> --
> Ticket URL: <http://oss.openplans.org/melkjug/ticket/422#comment:2>
> melkjug <http://www.melkjug.com>
>


--
Archive: 
http://www.coactivate.org/projects/melkjug/lists/melkjug-development-list/archive/2009/07/1246488787070
To unsubscribe send an email with subject "unsubscribe" to 
[email protected].  Please contact 
[email protected] for questions.

Reply via email to