Thread: [Bodington-developers] bodington.properties defaults

SourceForge Headquarters 225 Broadway Suite 1600 San Diego, CA 92101 +1 (858) 422-6466

any chance of shipping a sparse bodington.properties in the war file  
with language stuff in it? no time to modify the installer

Alistair

Alistair Young wrote:
> any chance of shipping a sparse bodington.properties in the war file  
> with language stuff in it? no time to modify the installer

Talking of time I don't think all the stuff that is going to go in is 
going to make it for the end of July. We have a long list of stuff here 
that is supposed to go in after the i18n work but work on merging most 
of it hasn't started.

What are we going to do?
Delay the release?
Release without the stuff?

-- 
+--Matthew Buckett-----------------------------------------+
| VLE Developer, Learning Technologies Group               |
| Tel: +44 (0) 1865 283660 http://www.oucs.ox.ac.uk/       |
+------------Computing Services, University of Oxford------+

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

I'm very, very keen that we have MVN running by late September in Oxford
Paul

Paul Davis
01865 283414

-----Original Message-----
From: bod...@li...
[mailto:bod...@li...] On Behalf Of
Matthew Buckett
Sent: 19 July 2005 17:23
To: bod...@li...
Subject: Re: [Bodington-developers] bodington.properties defaults

Alistair Young wrote:
> any chance of shipping a sparse bodington.properties in the war file  
> with language stuff in it? no time to modify the installer

Talking of time I don't think all the stuff that is going to go in is 
going to make it for the end of July. We have a long list of stuff here 
that is supposed to go in after the i18n work but work on merging most 
of it hasn't started.

What are we going to do?
Delay the release?
Release without the stuff?

-- 
+--Matthew Buckett-----------------------------------------+
| VLE Developer, Learning Technologies Group               |
| Tel: +44 (0) 1865 283660 http://www.oucs.ox.ac.uk/       |
+------------Computing Services, University of Oxford------+

-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
_______________________________________________
Bodington-developers mailing list
Bod...@li...
https://lists.sourceforge.net/lists/listinfo/bodington-developers

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 far as I know, stuff that isn't in includes:

HSQLDB
Timed Resources
RSS
Textblocks/Announcements
ACL
HTML Widget
Edit Discussion Room Posts
QuickLinks
Resource Search
EasyBuilder

And as Sean mentioned earlier today we still havn't done any work on 
migration of 2.4 to 2.6.

-- 
+--Matthew Buckett-----------------------------------------+
| VLE Developer, Learning Technologies Group               |
| Tel: +44 (0) 1865 283660 http://www.oucs.ox.ac.uk/       |
+------------Computing Services, University of Oxford------+

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.

-- 
+--Matthew Buckett-----------------------------------------+
| VLE Developer, Learning Technologies Group               |
| Tel: +44 (0) 1865 283660 http://www.oucs.ox.ac.uk/       |
+------------Computing Services, University of Oxford------+

On you go Mathew. I committed the Leeds stuff today - I can't remember th=
e
state of the ones I did after the changes to res. I think Alexis may have
updated the ones in default - Alexis?

If that's the case then i18n is finished (at last)

Alistair

--=20
Alistair Young
Senior Software Engineer
UHI@Sabhal M=F2r Ostaig
Isle of Skye
Scotland

> 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 tha=
t
> 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 finishe=
d?
>
>> 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.
>
> --
> +--Matthew Buckett-----------------------------------------+
> | VLE Developer, Learning Technologies Group               |
> | Tel: +44 (0) 1865 283660 http://www.oucs.ox.ac.uk/       |
> +------------Computing Services, University of Oxford------+
>
>
> -------------------------------------------------------
> SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
> from IBM. Find simple to follow Roadmaps, straightforward articles,
> informative Webcasts and more! Get everything you need to get up to
> speed, fast. http://ads.osdn.com/?ad_id=3D7477&alloc_id=3D16492&op=3Dcl=
ick
> _______________________________________________
> Bodington-developers mailing list
> Bod...@li...
> https://lists.sourceforge.net/lists/listinfo/bodington-developers
>

Alistair Young wrote:
> On you go Mathew. I committed the Leeds stuff today - I can't remember the
> state of the ones I did after the changes to res. I think Alexis may have
> updated the ones in default - Alexis?
> 
> If that's the case then i18n is finished (at last)
> 
> Alistair
> 
> 

Yup, I have commited the i18n stuff for style_default/messagingroom and 
modified the ones in style_default/default to 'Tatham' format.

Alexis

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.
> 

I'm seeing this from a marketing perspective.  At the last Buzz we promised
2.6 in late July (and 16 establishments signed up for notification of a new
release), and the next Buzz is 22 August.  What do we give away then?  It's
not worth doing new Bodix CDs for 2.1 or whatever the current CD is.  2.6
has quickstart war, easybuilder, ACL, wysiwyg widget etc - lots of user
functions.  We showed that now is a good time to get academically-related
people's attention. From a marketing perspective I think we should release
asap if at all possible, even if it means losing some functionality in the
short term.

Paul

Paul Davis
01865 283414

-----Original Message-----
From: bod...@li...
[mailto:bod...@li...] On Behalf Of Colin
Tatham
Sent: 20 July 2005 09:27
To: bod...@li...
Subject: Re: [Bodington-developers] bodington.properties defaults

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.
> 

-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
_______________________________________________
Bodington-developers mailing list
Bod...@li...
https://lists.sourceforge.net/lists/listinfo/bodington-developers

<fc>
I agree with Paul here. For many reasons, we need to present the  
correct image here. 2.6 must come out at the end of the month. I  
think that we are pursuing timebox constraints here.
+/- a few days, we ship 2.6 at the end of the month.

We need a 2.6 CD at the next buzz.

surely there are no bugs! and if they are, squash them in 2.6.1!-)
On that note, what would make life easy for people to update to 2.6.1  
when released?....
</fc>

s

On 20 Jul 2005, at 09:41, Paul Davis wrote:

> I'm seeing this from a marketing perspective.  At the last Buzz we  
> promised
> 2.6 in late July (and 16 establishments signed up for notification  
> of a new
> release), and the next Buzz is 22 August.  What do we give away  
> then?  It's
> not worth doing new Bodix CDs for 2.1 or whatever the current CD  
> is.  2.6
> has quickstart war, easybuilder, ACL, wysiwyg widget etc - lots of  
> user
> functions.  We showed that now is a good time to get academically- 
> related
> people's attention. From a marketing perspective I think we should  
> release
> asap if at all possible, even if it means losing some functionality  
> in the
> short term.
>
> Paul
>
> Paul Davis
> 01865 283414
>
>
>
> -----Original Message-----
> From: bod...@li...
> [mailto:bod...@li...] On Behalf  
> Of Colin
> Tatham
> Sent: 20 July 2005 09:27
> To: bod...@li...
> Subject: Re: [Bodington-developers] bodington.properties defaults
>
>
> 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.
>>
>>
>
>
> -------------------------------------------------------
> SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
> from IBM. Find simple to follow Roadmaps, straightforward articles,
> informative Webcasts and more! Get everything you need to get up to
> speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
> _______________________________________________
> Bodington-developers mailing list
> Bod...@li...
> https://lists.sourceforge.net/lists/listinfo/bodington-developers
>
>
>
>
> -------------------------------------------------------
> SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
> from IBM. Find simple to follow Roadmaps, straightforward articles,
> informative Webcasts and more! Get everything you need to get up to
> speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
> _______________________________________________
> Bodington-developers mailing list
> Bod...@li...
> https://lists.sourceforge.net/lists/listinfo/bodington-developers
>
>

 > For many reasons, we need to present the
 > correct image here.

My worry is that we bung stuff in that's not properly finished/tested, 
and that's worse than not delivering on time, especially with the Boddix 
CD where the state of the build is set in stone. I think we need to 
prioritise/cut down what the most important components are if we are 
going to stick to the original deadline.

Colin

Sean Mehan wrote:
> <fc>
> I agree with Paul here. For many reasons, we need to present the  
> correct image here. 2.6 must come out at the end of the month. I  think 
> that we are pursuing timebox constraints here.
> +/- a few days, we ship 2.6 at the end of the month.
> 
> We need a 2.6 CD at the next buzz.
> 
> surely there are no bugs! and if they are, squash them in 2.6.1!-)
> On that note, what would make life easy for people to update to 2.6.1  
> when released?....
> </fc>
> 
> s
> 
> 
> On 20 Jul 2005, at 09:41, Paul Davis wrote:
> 
>> I'm seeing this from a marketing perspective.  At the last Buzz we  
>> promised
>> 2.6 in late July (and 16 establishments signed up for notification  of 
>> a new
>> release), and the next Buzz is 22 August.  What do we give away  
>> then?  It's
>> not worth doing new Bodix CDs for 2.1 or whatever the current CD  is.  
>> 2.6
>> has quickstart war, easybuilder, ACL, wysiwyg widget etc - lots of  user
>> functions.  We showed that now is a good time to get academically- 
>> related
>> people's attention. From a marketing perspective I think we should  
>> release
>> asap if at all possible, even if it means losing some functionality  
>> in the
>> short term.
>>
>> Paul
>>
>> Paul Davis
>> 01865 283414
>>
>>
>>
>> -----Original Message-----
>> From: bod...@li...
>> [mailto:bod...@li...] On Behalf  
>> Of Colin
>> Tatham
>> Sent: 20 July 2005 09:27
>> To: bod...@li...
>> Subject: Re: [Bodington-developers] bodington.properties defaults
>>
>>
>> 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.
>>>
>>>
>>
>>
>> -------------------------------------------------------
>> SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
>> from IBM. Find simple to follow Roadmaps, straightforward articles,
>> informative Webcasts and more! Get everything you need to get up to
>> speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
>> _______________________________________________
>> Bodington-developers mailing list
>> Bod...@li...
>> https://lists.sourceforge.net/lists/listinfo/bodington-developers
>>
>>
>>
>>
>> -------------------------------------------------------
>> SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
>> from IBM. Find simple to follow Roadmaps, straightforward articles,
>> informative Webcasts and more! Get everything you need to get up to
>> speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
>> _______________________________________________
>> Bodington-developers mailing list
>> Bod...@li...
>> https://lists.sourceforge.net/lists/listinfo/bodington-developers
>>
>>
> 
> 
> 
> -------------------------------------------------------
> SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
> from IBM. Find simple to follow Roadmaps, straightforward articles,
> informative Webcasts and more! Get everything you need to get up to
> speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
> _______________________________________________
> Bodington-developers mailing list
> Bod...@li...
> https://lists.sourceforge.net/lists/listinfo/bodington-developers
> 

superb, Matthew.

so, may i prioritise?

as seen in another email forward in this thread, i18n is done, save  
some bugs on typing, etc.
Does everyone agree? Please!

1. HTML Widget - MB already sorting it!-)
2. RSS - estimated 1.5 days - for whom?
3. HSQLDB - estimated 3 days - MB? This is a must, as we have sold a  
lot of snake oil on this one!
3. EasyBuilder - ?days - whom? Is this quickstart? if so, tis a must  
as before.
4. Textblocks/Announcements - ?days? - AC/CT? I thought that this was  
already done(ish)
4. Quicklinks - as above
5. ACL - 1.5days - MB? As above, we have demo'd it!-) (this is  
without timed access support)

that leaves

Timed Resources
     perhaps we leave this off the list of 2.6 and push to 2.8? Tis  
the sort of thing that if gotten wrong is very bad.....
Resource Search
     How diff is this?

Edit Discussion Room Posts
     Is this not related to MVN stuff? If so, AC promised already to  
get one out for 2.7.0 next month, which Ox / UHI should be able to  
slap in asap. But why make a crap hack when the whole thing will  
change in a matter of weeks? I would drop it of the 2.6 and beta in  
2.7.x asap, publish in 2.8.

?
-s

On 19 Jul 2005, at 18:58, 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.
>
> -- 
> +--Matthew Buckett-----------------------------------------+
> | VLE Developer, Learning Technologies Group               |
> | Tel: +44 (0) 1865 283660 http://www.oucs.ox.ac.uk/       |
> +------------Computing Services, University of Oxford------+
>
>
> -------------------------------------------------------
> SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
> from IBM. Find simple to follow Roadmaps, straightforward articles,
> informative Webcasts and more! Get everything you need to get up to
> speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
> _______________________________________________
> Bodington-developers mailing list
> Bod...@li...
> https://lists.sourceforge.net/lists/listinfo/bodington-developers
>
>

Sean Mehan wrote:
> superb, Matthew.

The time esitmates were for the things I am down to do.

> as seen in another email forward in this thread, i18n is done, save  
> some bugs on typing, etc.
> Does everyone agree? Please!
> 
> 1. HTML Widget - MB already sorting it!-)

This is taking longer because my patch doesn't apply because we now have 
the new style creation templates.

> 2. RSS - estimated 1.5 days - for whom?

I'm down for doing this.

> 3. HSQLDB - estimated 3 days - MB? This is a must, as we have sold a  
> lot of snake oil on this one!

This is probably one of the hardest things as it touches lots of code. 
Things it touches I forgot to mention include the Installer....

> 3. EasyBuilder - ?days - whom? Is this quickstart? if so, tis a must  as 
> before.

Colin I think.

> 4. Textblocks/Announcements - ?days? - AC/CT? I thought that this was  
> already done(ish)

Colin again.

> 4. Quicklinks - as above

Colin again.

> 5. ACL - 1.5days - MB? As above, we have demo'd it!-) (this is  without 
> timed access support)

This touches quite a bit of code and again a large number of template 
which have now changed to UHI look and feel which makes my job harder. 
This may be more than 1.5days.

-- 
+--Matthew Buckett-----------------------------------------+
| VLE Developer, Learning Technologies Group               |
| Tel: +44 (0) 1865 283660 http://www.oucs.ox.ac.uk/       |
+------------Computing Services, University of Oxford------+

>> 3. EasyBuilder - ?days - whom? Is this quickstart? if so, tis a must  
>> as before. 
> Colin I think.

Yes. Not connected with quickstart. Just need to commit and initial test 
with Bod head, 2 days.

> 
>> 4. Textblocks/Announcements - ?days? - AC/CT? I thought that this was  
>> already done(ish)
> Colin again.

I'm going to put the TextBlock in, we decided (in the vid conference) 
not to merge Announcements in at this stage. Commit and test, 1 day.

>> 4. Quicklinks - as above
> Colin again.

Not sure about this one. We wanted to make some changes before 
committing it (and it's likely to be Alexis).
If we make changes, we need to spend more time testing. Also Alexis will 
need some time to familiarise himself with the code that Ant wrote. 
Would be nice to add it to 2.6 though...

 > Timed Resources
 > perhaps we leave this off the list of 2.6 and push to 2.8? Tis  the
 > sort of thing that if gotten wrong is very bad.....

I think it's good as-is. Alexis is working on it now.

 > Resource Search
 >     How diff is this?

Ideally needs lots of tidying of existing metadata handling code, but 
adding keyword search is basically done.

 > Edit Discussion Room Posts
 >     Is this not related to MVN stuff?

Not MVN, allows editing posts in Bod discussion room. Small fix, has 
worked fine at Oxford so far.

Colin

Sean Mehan wrote:
> 1. HTML Widget - MB already sorting it!-)

This is now in.

> 2. RSS - estimated 1.5 days - for whom?

> 3. HSQLDB - estimated 3 days - MB? This is a must, as we have sold a  
> lot of snake oil on this one!

I'll probably tackle this one next. Buy the way I really like the new 
colour schema, it makes Bodington a pleasure to look at.

-- 
+--Matthew Buckett-----------------------------------------+
| VLE Developer, Learning Technologies Group               |
| Tel: +44 (0) 1865 283660 http://www.oucs.ox.ac.uk/       |
+------------Computing Services, University of Oxford------+

On 20 Jul 2005, at 17:45, Matthew Buckett wrote:

> Sean Mehan wrote:
>
>> 1. HTML Widget - MB already sorting it!-)
>>
>
> This is now in.
>

ta

>
>> 2. RSS - estimated 1.5 days - for whom?
>>
>
>
>> 3. HSQLDB - estimated 3 days - MB? This is a must, as we have sold  
>> a  lot of snake oil on this one!
>>
>
> I'll probably tackle this one next. Buy the way I really like the  
> new colour schema, it makes Bodington a pleasure to look at.

amazing. roll necks do have uses!-)

s

>
> -- 
> +--Matthew Buckett-----------------------------------------+
> | VLE Developer, Learning Technologies Group               |
> | Tel: +44 (0) 1865 283660 http://www.oucs.ox.ac.uk/       |
> +------------Computing Services, University of Oxford------+
>
>
> -------------------------------------------------------
> SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
> from IBM. Find simple to follow Roadmaps, straightforward articles,
> informative Webcasts and more! Get everything you need to get up to
> speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
> _______________________________________________
> Bodington-developers mailing list
> Bod...@li...
> https://lists.sourceforge.net/lists/listinfo/bodington-developers
>
>

<fc mode>
That depends. Can you guestimate what portion of stuff would miss an  
end of month release? Can you list what wouldn't make it, with  
probabilities? Of that remaining list, can you guestimate the time  
required (in dev days) to get it into head?

With such an analysis, we could make sensible decisions about how to  
proceed....

</fc mode>
s

On 19 Jul 2005, at 17:23, Matthew Buckett wrote:

> Alistair Young wrote:
>
>> any chance of shipping a sparse bodington.properties in the war  
>> file  with language stuff in it? no time to modify the installer
>>
>
> Talking of time I don't think all the stuff that is going to go in  
> is going to make it for the end of July. We have a long list of  
> stuff here that is supposed to go in after the i18n work but work  
> on merging most of it hasn't started.
>
> What are we going to do?
> Delay the release?
> Release without the stuff?
>
> -- 
> +--Matthew Buckett-----------------------------------------+
> | VLE Developer, Learning Technologies Group               |
> | Tel: +44 (0) 1865 283660 http://www.oucs.ox.ac.uk/       |
> +------------Computing Services, University of Oxford------+
>
>
> -------------------------------------------------------
> SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
> from IBM. Find simple to follow Roadmaps, straightforward articles,
> informative Webcasts and more! Get everything you need to get up to
> speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
> _______________________________________________
> Bodington-developers mailing list
> Bod...@li...
> https://lists.sourceforge.net/lists/listinfo/bodington-developers
>
>

Could we release 2.5 instead? 

After all what is 2.5 if not an untested 2.6! 

And have we tested 2.6? 

Hell no.

adam

-----Original Message-----
From: bod...@li...
[mailto:bod...@li...] On Behalf Of
Matthew Buckett
Sent: 19 July 2005 17:23
To: bod...@li...
Subject: Re: [Bodington-developers] bodington.properties defaults

Alistair Young wrote:
> any chance of shipping a sparse bodington.properties in the war file  
> with language stuff in it? no time to modify the installer

Talking of time I don't think all the stuff that is going to go in is 
going to make it for the end of July. We have a long list of stuff here 
that is supposed to go in after the i18n work but work on merging most 
of it hasn't started.

What are we going to do?
Delay the release?
Release without the stuff?

-- 
+--Matthew Buckett-----------------------------------------+
| VLE Developer, Learning Technologies Group               |
| Tel: +44 (0) 1865 283660 http://www.oucs.ox.ac.uk/       |
+------------Computing Services, University of Oxford------+

-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
_______________________________________________
Bodington-developers mailing list
Bod...@li...
https://lists.sourceforge.net/lists/listinfo/bodington-developers

Alistair Young wrote:
> any chance of shipping a sparse bodington.properties in the war file  
> with language stuff in it? no time to modify the installer

At the moment there is a bodington.properties from Anotony in there.

I think it would be good to ship a bodington-sample.properties file in 
the WAR that contains a fully commented bodington.properties file. I 
think Antony and I had a bit of a discussion about this (off list).

BTW: I modified BuildingServer so it no longer barfed when the default 
language wasn't set.

-- 
+--Matthew Buckett-----------------------------------------+
| VLE Developer, Learning Technologies Group               |
| Tel: +44 (0) 1865 283660 http://www.oucs.ox.ac.uk/       |
+------------Computing Services, University of Oxford------+