Am Mittwoch, 6. September 2006 12:25 schrieb Stephan Richter:
> On Monday 14 August 2006 17:46, Florian Lindner wrote:
> > ow does that script works? Executing gives an error:
> >
> > [EMAIL PROTECTED] ~/Zope3 $ python utilities/static-apidoc
> > /home/florian/z3-doc/ Traceback (most recent call la
On 9/7/06, Rocky Burt <[EMAIL PROTECTED]> wrote:
My experience so far... after not having touched a project for over a
year and than the client wanting some work done, they usually expect to
have to pay to have it upgraded.
Well, in any case, they SHOULD expect that.
--
Lennart Regebro, Nuxeo
The Buildbot has detected a failed build of Zope3 branches 3.3 2.4 Windows 2000
zc-bbwin.
Buildbot URL: http://buildbot.zope.org/
Build Reason: changes
Build Source Stamp: 7521
Blamelist: flox
BUILD FAILED: failed failed slave lost
sincerely,
-The Buildbot
___
The Buildbot has detected a failed build of Zope3 branches 3.3 2.4 Windows 2000
zc-bbwin.
Buildbot URL: http://buildbot.zope.org/
Build Reason: changes
Build Source Stamp: 7519
Blamelist: fdrake,flox,jens,jim
BUILD FAILED: failed test
sincerely,
-The Buildbot
Hi,
Chris Withers wrote:
> Christian Theune wrote:
>> But changing APIs is what we do, and what we probably have to do, and
>> probably keep doing.
>
> I would prefer to see as much of this as possible turned into the past
> tense...
Yup. But it isn't, yet. Unfortunately.
>> However, I think, w
On Thu, 2006-07-09 at 08:06 +0100, Chris Withers wrote:
> Martijn Faassen wrote:
> > Just to give some real data on this from someone who actually spent time
> > updating applications: the churn is there, but it's not like this causes
> > absolutely massive amounts of work, and the deprecation wa
On 9/5/06, Philipp von Weitershausen <[EMAIL PROTECTED]> wrote:
> And therefore, we really need to make an
> overview over all API changes from 3.0.0 so you can see what happened
> (this in addition to the more detailed "whats new in vX" pages.
>
> Maybe somebody can start such a page somewhere,
Martijn Faassen wrote:
Just to give some real data on this from someone who actually spent time
updating applications: the churn is there, but it's not like this causes
absolutely massive amounts of work, and the deprecation warnings are
usually pretty helpful.
OK.
What's your experience wi
Christian Theune wrote:
But changing APIs is what we do, and what we probably have to do, and
probably keep doing.
I would prefer to see as much of this as possible turned into the past
tense...
However, I think, we need to get much more careful
with it and maybe we can try harder keeping e
Stephan Richter wrote:
I think at the end Jim and I agreed that the zope.* namespace should follow
and keep following the current Zope 3 style guide. Other namespaces, such as
zc, z3c, lovely, etc can choose their own style guide but must be consistent
within the namespace.
Sheesh, now you're
Fred Drake wrote:
I don't think this paragraph really applies to this discussion. Jim
suggested that we change the Z3 style guide, and I'm suggesting that
that's counter-productive.
Indeed, and it's an odd suggestion given that we're talking about how
change for change's sake is bad ;-)
11 matches
Mail list logo
