Le 13/01/11 17:50, yuppie a écrit :
> Godefroid Chapelle wrote:
>> One buildout per package is the practice in ZTK world.
>>
>> I have come to really appreciate it; it really lowers the barrier for
>> contributions.
>>
>> checkout
>> bootstrap
>> buildout
>> run tests to check state before changes
Godefroid Chapelle wrote:
> One buildout per package is the practice in ZTK world.
>
> I have come to really appreciate it; it really lowers the barrier for
> contributions.
>
> checkout
> bootstrap
> buildout
> run tests to check state before changes
> fix
> run tests
> commit
That only works if
Le 13/01/11 17:25, yuppie a écrit :
> Hi!
>
>
> Godefroid Chapelle wrote:
>> I even added the missing buildout (copied from trunk - see revision 119553).
>
> You know http://svn.zope.org/CMF/branches/2.2/ and
> http://svn.zope.org/CMF/trunk/ ?
>
> These buildouts are used for developing and testing
Hi!
Godefroid Chapelle wrote:
> I even added the missing buildout (copied from trunk - see revision 119553).
You know http://svn.zope.org/CMF/branches/2.2/ and
http://svn.zope.org/CMF/trunk/ ?
These buildouts are used for developing and testing all CMF Products. Do
we also need bootstrap and
Am 23.09.2010, 17:24 Uhr, schrieb Jens Vagelpohl :
> +1
+1 working fine here.
Charlie
--
Charlie Clark
Managing Director
Clark Consulting & Research
German Office
Helmholtzstr. 20
Düsseldorf
D- 40215
Tel: +49-211-600-3657
Mobile: +49-178-782-6226
___
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 9/23/10 12:38 , yuppie wrote:
> My goal is to have *one* branch for each CMF version. (Except of CMF
> 2.1, which has also a non-buildout branch.) I think we have always a
> primary target platform that is used for development (e.g. Zope trunk
>
On Thu, Sep 23, 2010 at 12:38 PM, yuppie wrote:
> If that concept works for everybody, I'll migrate the rest of the
> CMF.buildout branches.
+1, works for me as discussed in Dresden :)
Hanno
___
Zope-CMF maillist - Zope-CMF@zope.org
https://mail.zope
