[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Why does workflow change require environment upgrade?

From: Cooke, Mark <mark.cooke_at_siemens.com>
Date: Thu, 13 Jan 2011 13:00:07 -0000

Folks,

I've split this out from previous thread
(http://groups.google.com/group/trac-users/browse_thread/thread/f836f93b
25b8b275) as a more specific question:

Why should changing the workflow in 0.11.7 require an environment
upgrade?

Background from the other thread: each env inherits a shared conf that
then inherits a shared workflow file (using 'file = xxx' in the
[inherit] section). I am investigating why the workflow is not working
in any env when I broke all my trac sites producing:

<project-name>: Error
(The Trac Environment needs to be upgraded. Run "trac-admin
<project-path> upgrade")

...and the trac.log error:

2011-01-13 10:23:10,038 Trac[env] WARNING: Component
<trac.ticket.default_workflow.ConfigurableTicketWorkflow object at
0x02B7AD50> requires environment upgrade

AFAIK the workflow is self-contained I the ini file and should not
affect the environment or database?

I appreciate any insight you can offer,

~ mark c

P.S. I will upgrade to 0.12, as soon as I have time to validate it,
promise...
Received on 2011-01-13 14:00:51 CET

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.