-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Michael Haubenwallner wrote:
> Tres Seaver wrote:
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA1
>>
>> Jim Fulton wrote:
>>
>>> Zope 3, as releases is not affected by the security hole that
>>> has plagued Zope 2, however, Michael Haubenwallner ha
Tres Seaver wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jim Fulton wrote:
Zope 3, as releases is not affected by the security hole that
has plagued Zope 2, however, Michael Haubenwallner has pointed
out that some add-on-products, such as zwiki and bugtracker, may
provide TTW reST.
T
On Jul 7, 2006, at 4:37 PM, Tres Seaver wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jim Fulton wrote:
Zope 3, as releases is not affected by the security hole that
has plagued Zope 2, however, Michael Haubenwallner has pointed
out that some add-on-products, such as zwiki and bugtrac
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jim Fulton wrote:
> Zope 3, as releases is not affected by the security hole that
> has plagued Zope 2, however, Michael Haubenwallner has pointed
> out that some add-on-products, such as zwiki and bugtracker, may
> provide TTW reST.
They appear to b
Philipp von Weitershausen wrote at 2006-7-6 21:35 +0200:
> ...
>If you follow the argument that untested code is broken by definition,
I do not follow it.
>then you essentially have no fix if you get a fix without knowing
>whether it actually works.
In many cases, I can convince myself that a fi
Zope 3, as releases is not affected by the security hole that
has plagued Zope 2, however, Michael Haubenwallner has pointed
out that some add-on-products, such as zwiki and bugtracker, may
provide TTW reST.
There are 2 issues here:
1. That we need to warn anyone using these that there is an is
Tres Seaver wrote:
> [EMAIL PROTECTED] wrote:
>
>>> no problem, I agree to have a place for such infos.
>>> The README.txt files are not good enough for give a overview
>>> because you have to checkout first or browse the really slow
>>> repos with a browser.
>>>
>>> Tell me where is somewhere and
Jim Fulton wrote:
>
> On Jul 7, 2006, at 9:45 AM, Julien Anguenot wrote:
>
>> Hi there,
>>
>> Jim Fulton wrote:
>>> On Jul 5, 2006, at 5:46 AM, Christian Theune wrote:
I'm sitting at EuroPython right now, and a small discussion came up,
trying to find out why nobody seems motivated to f
On Jul 7, 2006, at 9:45 AM, Julien Anguenot wrote:
Hi there,
Jim Fulton wrote:
On Jul 5, 2006, at 5:46 AM, Christian Theune wrote:
I'm sitting at EuroPython right now, and a small discussion came up,
trying to find out why nobody seems motivated to fix bugs came up.
Martijn Fassen noted tha
Hi there,
Jim Fulton wrote:
> On Jul 5, 2006, at 5:46 AM, Christian Theune wrote:
>> I'm sitting at EuroPython right now, and a small discussion came up,
>> trying to find out why nobody seems motivated to fix bugs came up.
>>
>> Martijn Fassen noted that the tools we use should be better (I agree
On Jul 7, 2006, at 7:52 AM, Christian Theune wrote:
Hi,
Jim Fulton wrote:
On Jul 6, 2006, at 12:29 PM, Philipp von Weitershausen wrote:
[EMAIL PROTECTED] wrote:
Christian Theune wrote at 2006-7-5 11:46 +0200:
...
Another thing are the rules about unit tests. Some bugs touch
areas that
ar
Hi,
Jim Fulton wrote:
On Jul 6, 2006, at 12:29 PM, Philipp von Weitershausen wrote:
[EMAIL PROTECTED] wrote:
Christian Theune wrote at 2006-7-5 11:46 +0200:
...
Another thing are the rules about unit tests. Some bugs touch areas
that
are poorly tested. When I fix a bug over there, do I hav
Jim Fulton wrote:
I think we need to be more draconian about quality. Because
we are late for this release, we will need to take the usual shortcuts,
however, if we find missing tests, we should report them as non-critical
bugs. In addition, we should disallow any new features that would
affect
On Jul 5, 2006, at 5:46 AM, Christian Theune wrote:
Hi,
I'm sitting at EuroPython right now, and a small discussion came
up, trying to find out why nobody seems motivated to fix bugs came up.
Martijn Fassen noted that the tools we use should be better (I
agree on that, especially making
On Jul 6, 2006, at 10:11 PM, Tres Seaver wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Christian Theune wrote:
Hi,
Marius Gedminas wrote:
I do not think that the requirements to
4. Write unit tests
5. Merge bugfixes from trunk to the release branch
6. Wait for the incredibly slow upd
On Jul 6, 2006, at 2:03 PM, Lennart Regebro wrote:
On 7/6/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
When I have introduced secondary bugs in my fixes (which occasionally
happened), then a unit test would not have helped. The reason was
then
that the affected code was used in unantici
Philipp von Weitershausen wrote:
Zope 2 releases should ship with bin/test.py (probably Scripts\test.py
on Windows). Though the one shipping with Zope 2.9.3 doesn't properly
set up PYTHONPATH to include the Zope 2.9.3 SOFTWARE_HOME. Perhaps
that's going to be fixed in Zope 2.9.4 which won't be bu
On Jul 6, 2006, at 12:29 PM, Philipp von Weitershausen wrote:
[EMAIL PROTECTED] wrote:
Christian Theune wrote at 2006-7-5 11:46 +0200:
...
Another thing are the rules about unit tests. Some bugs touch
areas that
are poorly tested. When I fix a bug over there, do I have to work
harder
to
On Friday 07 July 2006 05:18, Chris Withers wrote:
> Well, that was one of the most useless responses I've ever read ;-)
>
> Care to explain what, exactly, you were saying "yes" too?
Sorry, it is not relevant and can be removed.
Regards,
Stephan
--
Stephan Richter
CBU Physics & Chemistry (B.S.)
Excuse my abscence. I'm a little busy and cannot find the time to track
the list daily.
Small summary of zope.generic:
it's a not-yet-fully-implemented, experimental prototype trying to find
a high-level-usage pattern or framework for zope 3.
During the easter-sprint I decided to put the code
Chris Withers wrote:
> Philipp von Weitershausen wrote:
>> $ svn co .../trunk Zope3
>> $ cd Zope3
>> $ make
>> $ python test.py -s zope.i18n
>
> Ah cool, didn't notice that test.py lived there in Zope 3...
>
> Now, what about Zope 2,
Zope 2 checkouts ship with pretty much the same test.py scrip
Stephan Richter wrote:
On Thursday 06 July 2006 10:31, Chris Withers wrote:
Is it still relevant or can it be removed?
Yes.
Well, that was one of the most useless responses I've ever read ;-)
Care to explain what, exactly, you were saying "yes" too?
Chris
--
Simplistix - Content Managemen
Philipp von Weitershausen wrote:
$ svn co .../trunk Zope3
$ cd Zope3
$ make
$ python test.py -s zope.i18n
Ah cool, didn't notice that test.py lived there in Zope 3...
Now, what about Zope 2, more specifically Zope 2 releases for Windows?
cheers
Chris
--
Simplistix - Content Management, Zope
Philipp von Weitershausen wrote:
I disagree. How would you make sure that your fix for even a "trivial"
NameError actually works? Perhaps you introduced another typo in the
bugfix? Or perhaps another problem pops up in the same codepath.
Clearly, since the NameError didn't occur in any other test
On Thursday 06 July 2006 10:31, Chris Withers wrote:
> Is it still relevant or can it be removed?
Yes.
Regards,
Stephan
--
Stephan Richter
CBU Physics & Chemistry (B.S.) / Tufts Physics (Ph.D. student)
Web2k - Web Software Design, Development and Training
25 matches
Mail list logo
