Re: [Bodington-developers] bodington.properties defaults

[Colin T. <col...@co...>]

Luckily I was out yesterday and missed all those mails!

Apart from OSSWATCH wanting to get on with making a new Boddix CD, is 
there a deadline for the CD?

I think it would be preferable to delay 2.6. At Oxford we've decided 
that we will upgrade our live WebLearn server with our latest code at 
the end of the month whether 2.6 is complete or not. Is a 2.6 delay a 
problem at UHI? I guess so...

Colin


Matthew Buckett wrote:
> Matthew Buckett wrote:
> 
>>Paul Davis wrote:
>>
>>
>>>I'm inclined to get 2.6 out the door, and if necessary add stuff in
>>>for 2.7
>>>Until 2.6 goes we can't make new Bodix CDs
> 
> 
> As Sean suggested here are my guesses at getting the code into HEAD that
> I am due to be working on. This doesn't include any time for
> testing/problems.
> 
> Is it ok to start pushing this stuff in? Or is the I18N not yet finished?
> 
> 
>>As far as I know, stuff that isn't in includes:
>>
>>HSQLDB
> 
>  - Big One, includes refactoring of bodington.properties, ant stuff,
> SetupServlet. 3 days.
> 
> 
>>RSS
> 
>   - Should be reasonably easy. 1.5 days.
> 
> 
>>ACL
> 
>   - 1.5 days in it's current state (without timed access support).
> 
> 
>>HTML Widget
> 
>   - 1 day as I have been working on this today.
> 
> 
>>And as Sean mentioned earlier today we still havn't done any work on
>>migration of 2.4 to 2.6.
> 
>   - 3 days. Would be nice to have a dump of a clean 2.1 install and a
> 2.4 instal which we can then test the upgrade procedure against. The
> problem is that testing this probably shouldn't happen until all the
> other code is in.
>