Changes between Version 4 and Version 5 of ScrumPlugin


Ignore:
Timestamp:
Feb 13, 2007 1:43:13 PM (8 years ago)
Author:
masariello
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • ScrumPlugin

    v4 v5  
    1717 
    1818The upgrade procedure creates a column called 'started' in the milestone table, 
    19 some SQL views and functions, and some Trac reports. No external scripts are needed 
     19some SQL views and functions, and some Trac reports. No !external scripts are needed 
    2020to collect iteration statistics. Everything is done with SQL queries. 
    2121 
     
    3434}}} 
    3535 
    36 I did most of the development on Windows/Apache/Postgres 8.1.4. I really have no idea if the 
     36I did most of the development on Windows/Apache/Postgres 8.1.4/Trac 0.11. 
     37I really have no idea if the 
    3738SQL will work on any other backend, and I doubt I'll ever find the time to test with other 
    3839setups. 
    3940 
    40 I didn't find any way to make the Python setup utilities also build the Java applet, so I had 
    41 to use a trivial Makefile. As long as Python and javac are in your path, it should work. 
    42 I did try to run Cygwin GNU make 3.80 on it, and it seems the Java target build statements upset the shell. Couldn't figure out why :-( 
    43  
    44 I did all the development against Trac 0.11 and then backported to 0.10. The backport changes 
     41I then backported to Trac 0.10. The backport changes 
    4542are actually quite trivial. In fact I left the 0.11 code commented out and ready to kick in. 
    4643I just didn't feel like creating and maintaining two different branches. 
     44 
     45I couldn't find any way to make the Python setup utilities also build the Java applet, so I 
     46had to use a trivial Makefile. So, to build, you should just run {{{[n]make}}} in the plugin 
     47root directory. {{{make install}}} should deploy it. As long as Python and javac are in your path, it should work. 
     48I did try to run Cygwin GNU make 3.80 on it, and it seems the Java target build statements upset the shell. Couldn't figure out why :-( 
    4749 
    4850== Bugs/Feature Requests ==