On Mon, Feb 2, 2009 at 16:28, Sebastien Douche wrote:
> On Mon, Feb 2, 2009 at 15:04, Benji York wrote:
>> wrote:
>>>
>>> - Zope 3.4 Versions:
>>> http://download.zope.org/zope3.4/3.4.0/versions.cfg
>>
>> I had been using http://download.zope.org/zope3.4/versions.cfg, but that
>> has gone aw
On Mon, Feb 2, 2009 at 17:12, Stephan Richter
wrote:
> On Monday 02 February 2009, Ignas Mikalajunas wrote:
>> Yes, and still it broke all of my branches as now I will have to
>> update a whole lot of checkouts to get them working again. So while I
>> am all for the new syst
> I don't really have time to read this whole discussion, but note that
> Grok's REST support uses ++rest++ and then provides a rest
> layer (for that protocol) to the request. That sounds quite similar to
> what you are proposing for XMLRPC.
>
> It's still ugly as POST and GET need to be handled b
On Jan 25, 2008 4:19 PM, Fred Drake <[EMAIL PROTECTED]> wrote:
> On Jan 25, 2008 6:13 AM, Stephan Richter <[EMAIL PROTECTED]> wrote:
> > Well, pinning versions for production is okay, but what are you doing during
> > development? If everyone keeps their own working set of versions, we will
> > soo
> > > Okay, so I think we should use the KGS and declare the set of packages in
> > > there as Zope 3.4.0.
> >
> > The KGS changes from time to time, doesn't it? Do you mean "the set of
> > packages frozen at this moment in time"?
>
> No, when we do a release, I provide frozen versions of th
