[BlueBream] BlueBream 1.0b3 released!

[Christophe Combelles]

Hi,

I've implemented this behaviour, it will be available starting from 1.0b4! 
During project creation, the latest versions.cfg is retrieved. This file 
contains a comment with a marker:

# LAST_TEMPLATE_CHANGE = 1.0b4

If the version of the marker is greater than the version used, the user will be 
warned:

**WARNING**: the project template for Bluebream has changed since version 1.0b4.
You should upgrade to this version.

Now, when releasing bluebream, this marker should be updated if the paster 
template contains significant changes. I've updated the release_howto to remind 
it at release time.

Christophe

Le 24/07/2010 01:06, Christophe Combelles a écrit :
>
> However we should find a way to warn the user of an old version that the
> template has been updated.
>
> Here is an example scenario:
> ----------------------------
> bluebream version:   1.0    1.0.1    1.0.2
> KGS modified?         .      yes      no
> template modified?    .      no       yes
>
> - A user has installed version 1.0.
> - We release bluebream version 1.0.1, with changes *only* in the versions
> - The user starts a new project with bluebream 1.0.
> =>  the project automatically get the new versions of 1.0.1. (done)
> - We release bluebream version 1.0.2, with changes *only* in the template
> - the user starts a new project again with bluebream 1.0
> =>  Here, the user should be warned that the latest version contains a new
> template, and that he should upgrade bluebream itself.
>
> How can we implement this behaviour?
>
> A first idea would be to put a comment in the versions.cfg file, detected during
> project creation, holding the latest version containing changes requiring an
> upgrade, and compared against the version used by the user.
>
> So with this scenario, the versions.cfg for 1.0.1 would begin with:
>
> # main version file for BlueBream
> # latest version that required an upgrade: 1.0
> [buildout]
> extends = ...
>
> And the versions.cfg for 1.0.2 would begin with:
>
> # main version file for BlueBream
> # latest version that required an upgrade: 1.0.2
> [buildout]
> extends = ...
>
> I think it's quite easy to implement and to maintain.
>
> Maybe it would also be nice to maintain a migration documentation, telling the
> user what to change in his project once created with 1.0 to be equivalent to 1.0.2.
>
> Christophe
>
>>
>> Regards,
>> Baiju M
>>
>>
>
> _______________________________________________
> bluebream mailing list
> bluebream at zope.org
> https://mail.zope.org/mailman/listinfo/bluebream