Re: [Bodington-developers] bodington.properties defaults

[Sean M. <se...@sm...>]

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