Upgrading to trunk

1 view
Skip to first unread message

Chad Maine

unread,
Apr 1, 2009, 1:30:17 PM4/1/09
to Agilito development
Our team has been using Agilito for a few months now, thanks for the
great project. I always appreciate an open-source project (in Django,
no less) that does one thing, and does it well. We have been running
for some time on an old checkout (r10 or so) and I'm looking at
upgrading our running instance to the latest in trunk.

Aside from the db schema changes, how would you suggest we go about
the upgrade?

-Chad

Emiliano Heyns

unread,
Apr 1, 2009, 2:41:42 PM4/1/09
to Agilito development
Test before comitting to production. I have done the same gradual
updates in essence, and I haven't found issues so far. But better safe
than sorry; copy your production database, and test the trunk version
against that. I'm using postgresql, and there's a bit of straight SQL
in the code that wasn't there in r10; it is simple enough SQL, but not
tested against mysql. The query in question is:

update agilito_userstory set rank = rank - 1 where project_id=%s
and rank > %s

which looks to be non-db specific to me. The other bit is:

select distinct
p.id, p.name
from agilito_project p
join agilito_project_project_members pm on pm.project_id =
p.id and pm.user_id = %(me)d
join agilito_iteration i on i.project_id = p.id
where i.start_date <= '%(today)s' and i.end_date >= '%
(last_end)s'
order by p.id

where the dates are in '%Y-%m-%d' format. I think pretty much any
database supports this date format.

Let me know how it goes.

Emile

Chad Maine

unread,
Apr 1, 2009, 4:24:14 PM4/1/09
to Agilito development
We are using Postgres as well, but point taken re: testing against
another copy of the database instance.


BTW, sorry to clutter the dev mailing list with this, but I thought it
would be good to let you know people *are* using Agilito. :)

Thanks,
Chad

Emiliano Heyns

unread,
Apr 1, 2009, 4:40:00 PM4/1/09
to Agilito development
On Apr 1, 10:24 pm, Chad Maine <chad.ma...@gmail.com> wrote:
> BTW, sorry to clutter the dev mailing list with this, but I thought it
> would be good to let you know people *are* using Agilito.  :)

1. We only have one mailinglist at the moment, so that's all the
choice we've provided. I see no value in creating a second list (yet),
because
2. Given the current state and real-world use of Agilito, we *are* in
dev mode.

Not that I want to scare you away ;)

Emile
Reply all
Reply to author
Forward
0 new messages