Hi peter,

OK I will fix this by the release.

Andy

On 05/11/2012 04:02 PM, Peter Keller wrote:
> Dear all (but mainly Andy, I guess):
>
> There is still GPL-ed code in dawn-fable. Is there any chance that this
> could be sorted out by 15 June? I have attached the last e-mail
> correspondence about this from the old DAWB mailing list on 7 Feb.
>
> Regards,
> Peter.
>
> On Thu, 2012-04-26 at 15:32 +0000, Alun Ashton wrote:
>> Don’t shoot the messenger.
>>
>>
>>
>> So after consideration and disscussion please find enclosed the
>> suggested revised release schedule for DAWN 1.0, let me know what you
>> think of if you want to discuss your individual timetables and how
>> they fit in. (Thanks to Andy, Matt and Mark for their help on drafting
>> this).
>>
>>
>>
>> 18th May:  1st Release candidate
>>
>> 8th June Release Candidate 2 –final?
>>
>> 15th of June: Release date.
>>
>>
>>
>> If I am honest I think that for release candidate 1 we should have all
>> the functionality and features in but between release candidate 1 and
>> the release date we should work on bug fixes and ‘branding’,
>> installation etc. I don’t think there is time to get that all done by
>> RC1.
>>
>>
>>
>> There are 5 components each of which should have its own sub release
>> schedule and can start its own thread on this mailing list, but in
>> summary:
>>
>> 1)     Plotting (this is referring to the ‘new’ plotting led by MattG,
>> any other changes to e.g. fable plotting or SDA plotting should adhere
>> to the same Release candidate and main release dates).
>>
>> a.      4th May ‘soft’ freeze on new functionality, all contributions
>> should be in by this date (Sandor/Gabor/Jonathon we should try and get
>> any contributions you wish to make in by this date), Matt has a list
>> of functionality if anybody needs it.
>>
>> b.     11th May ‘hard’ freeze on any new functionality.
>>
>> 2)     Workflow (led by Olof)
>>
>> a.      I will assume Olof will come up with a plan etc that will
>> correspond to the release dates.
>>
>> 3)     Python (led by Mark, he will start a separate thread with
>> details etc)
>>
>> a.      11th of May, ‘soft’ freeze on new functionality
>>
>> b.     18th of May, hard freeze.
>>
>> 4)     ICAT (led by Ghita, I have this as separate but we can decide
>> later if needs to be)
>>
>> a.      27th of April freeze on functionality and release of plugin.
>> Basically this is done for integration with ICAT 3*
>>
>> 5)     Product (including views and perspectives)
>>
>> This is where there is a bit of ‘flexibility’/unknown! This section
>> should include new and old views, existing perspective, new
>> perspectives, documentation including cheat sheets, logo!, welcome
>> screen, installation, packaging etc.
>>
>> a.      11th May: freeze for converting existing views and
>> incorporating new views.
>>
>> b.     17th May: freeze on testing and documentation and preparation
>> of build
>>
>> c.      18th May: Release candidate 1
>>
>> d.     8th of June: Release candidate 2 with all build, perspectives,
>> welcome screen, logo etc, its should be as close to the actual release
>> as possible.
>>
>>
>>
>> No doubt I will have missed some things out….
>>
>>
>>
>> Alun
>> ___________________________________________________________
>> Alun Ashton, [log in to unmask] Tel: +44 1235 778404
>> Scientific Software Team Leader,  http://www.diamond.ac.uk/
>> Diamond Light Source, Chilton, Didcot, Oxon, OX11 0DE, U.K.
>>
>>