On 7/16/06, Jim Fulton [EMAIL PROTECTED] wrote:
On Jul 11, 2006, at 8:05 AM, Patrick Gerken wrote:
On 7/7/06, Julien Anguenot [EMAIL PROTECTED] wrote:
...
I marked the bug as bug + bugfix but nobody cares. That is much more
discouraging than what I can not do nice wiki links to in my
On Sep 11, 2006, at 5:47 AM, Patrick Gerken wrote:
On 7/16/06, Jim Fulton [EMAIL PROTECTED] wrote:
On Jul 11, 2006, at 8:05 AM, Patrick Gerken wrote:
On 7/7/06, Julien Anguenot [EMAIL PROTECTED] wrote:
...
I marked the bug as bug + bugfix but nobody cares. That is much
more
On Jul 11, 2006, at 8:05 AM, Patrick Gerken wrote:
On 7/7/06, Julien Anguenot [EMAIL PROTECTED] wrote:
...
I marked the bug as bug + bugfix but nobody cares. That is much more
discouraging than what I can not do nice wiki links to in my bugreport
other bugtracker items or svn sources like
--On 16. Juli 2006 09:33:33 -0400 Jim Fulton [EMAIL PROTECTED] wrote:
I'll note that *none* of the solutions include tests. Tests are often
the
bulk of the work. A submitter should not assume that just because a
patch is provided, than someone only has to check it in.
Submitter do
On 7/7/06, Julien Anguenot [EMAIL PROTECTED] wrote:
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
Jim Fulton wrote:
On Jul 11, 2006, at 8:05 AM, Patrick Gerken wrote:
...
As a non committer I would like to note that it was easy for me to
search if somebody already submitted a bug I found, and submit a new
patch, it was also trivial to add the for the bugfix and the test. The
only thing
Martijn Faassen wrote:
The other suggestion I made elsewhere is the ability for developers to
add breaking tests to the codebase (explicitly marked as such, and not
normally run).
+1
--
Benji York
Senior Software Engineer
Zope Corporation
___
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
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
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
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 updates on the collector
discourage me all that much.
Right. They don't discourage me either, but there is a special
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 it easy to find which bugs need to be urgently
fixed
On Wed, Jul 05, 2006 at 11:46:52AM +0200, 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.
...
I feel like fixing a bug every now and then when I have like 30 minutes
spare time and
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 introduce the fix because I have to start introducing tests?
We should find and announce a
14 matches
Mail list logo
