Marius Gedminas wrote:
> Marius Gedminas wrote:
> Marius Gedminas wrote:
> On Fri, Jan 29, 2010 at 10:48:41AM +, Jan-Wijbrand Kolman wrote:
>> I'd like to make a 3.6.1 bugfix release for zope.app.wsgi.
>>
>> On the trunk there's support for picking up "product configuration"
>> that
On Fri, Jan 29, 2010 at 10:48:41AM +, Jan-Wijbrand Kolman wrote:
> I'd like to make a 3.6.1 bugfix release for zope.app.wsgi.
>
> On the trunk there's support for picking up "product configuration"
> that has not been released yet (however, it had been released in a
> bugfix release in the 3
Hi,
I'd like to make a 3.6.1 bugfix release for zope.app.wsgi.
On the trunk there's support for picking up "product configuration"
that has not been released yet (however, it had been released in a
bugfix release in the 3.4 line).
Could I ask someone to grant me pypi rights for this package?
> "TD" == Toby Dickenson <[EMAIL PROTECTED]> writes:
TD> A bug in the transaction manager would be really bad news. I
TD> would have thought it appropriate to resolve these problems and
TD> leave at least a few weeks of beta test before release.
I'm looking into the problem, as I report
On Fri, 29 Nov 2002, Toby Dickenson wrote:
> On Wednesday 27 November 2002 5:50 pm, Brian Lloyd wrote:
> > FYI I'd like to have a 2.6.1 beta out next week. Jeremy is still
> > looking at a few ZODB bug reports - as soon as he's done we'll
> > make the beta.
>
> Im not sure this is a good plan.
>
>
On Sunday 01 December 2002 3:36 pm, Brian Lloyd wrote:
> > > FYI I'd like to have a 2.6.1 beta out next week. Jeremy is still
> > > looking at a few ZODB bug reports - as soon as he's done we'll
> > > make the beta.
> >
> > Im not sure this is a good plan.
> >
> > Jeremy's sortKey changes look like
> > FYI I'd like to have a 2.6.1 beta out next week. Jeremy is still
> > looking at a few ZODB bug reports - as soon as he's done we'll
> > make the beta.
>
> Im not sure this is a good plan.
>
> Jeremy's sortKey changes look like they deserve a longer beta
> testing period
> than I would have
On Wednesday 27 November 2002 5:50 pm, Brian Lloyd wrote:
> FYI I'd like to have a 2.6.1 beta out next week. Jeremy is still
> looking at a few ZODB bug reports - as soon as he's done we'll
> make the beta.
Im not sure this is a good plan.
Jeremy's sortKey changes look like they deserve a longer
Casey Duncan wrote:
I'm assuming we will not have bug day before 2.6.1, but perhaps one shortly
thereafter is in order?
I'll upgrade to 2.6.2 when it comes out then ;-)
Chris
___
Zope-Dev maillist - [EMAIL PROTECTED]
http://lists.zope.org/mailman
Guido van Rossum wrote:
That means we either waste a lot more time doing releases, or the
releases become a lot more shoddy, hardly more than a snapshot from
CVS. Neither sounds attractive, sorry.
...or the release process becomes automated/documented enough that neither of
these happen ;-)
From: "Chris McDonough" <[EMAIL PROTECTED]>
> Sometimes
> going through the CVS logs for the module in which the bug is in, you
> can tell who has most recently been involved in that code and send them
> an email about the bug.
Heh. Never worked for me. Ah well, now I can fix things myself instead
I am assigned to fix this. I will make time to do it over the holiday. Time
has been extremely short for me (and basically all of us at ZC) lately, so
your patience is appreciated.
I'm assuming we will not have bug day before 2.6.1, but perhaps one shortly
thereafter is in order?
-Casey
On We
--On Mittwoch, 27. November 2002 13:17 -0500 Chris McDonough
<[EMAIL PROTECTED]> wrote:
On Wed, 2002-11-27 at 12:31, Wolfgang Strobl wrote:
On 27 Nov 2002, 11:18 seb bacon wrote:
> Can we have a bugfix release?
Me too. I'd like to get the fix for Issue 597
(http://collector.zope.org/Zope/59
> > I guess what I'm saying is that for a version 2.x.y, x should behave
> > as you describe while y should go up as often as a bug is discovered
> > and fixed...
>
> That means we either waste a lot more time doing releases, or the
> releases become a lot more shoddy, hardly more than a snapshot
On Wed, 2002-11-27 at 12:31, Wolfgang Strobl wrote:
> On 27 Nov 2002, 11:18 seb bacon wrote:
>
> > Can we have a bugfix release?
>
> Me too. I'd like to get the fix for Issue 597
> (http://collector.zope.org/Zope/597) in such a bugfix release.
> ZCTextIndex, quite different from the old TextIn
> From: "Andreas Jung" <[EMAIL PROTECTED]>
> > Someone posted already a fix for this problem. It should not be hard to
> fix
> > this single problem by exchanging the DateTime.py file on your sites
>
> Yep, it's on http://www.zope.org/Members/regebro/ somewhere.
> But I agree that it's time for a
On 27 Nov 2002, 11:18 seb bacon wrote:
> Can we have a bugfix release?
Me too. I'd like to get the fix for Issue 597
(http://collector.zope.org/Zope/597) in such a bugfix release.
ZCTextIndex, quite different from the old TextIndex, currently is
almost unusuable outside the US, because it isn
> Says who? I thought the idea behind it was to get the releases out
> early, so you can find the bugs faster and get the releases more
> stable more quickly...
>
> I guess what I'm saying is that for a version 2.x.y, x should behave
> as you describe while y should go up as often as a bug is disc
Guido van Rossum wrote:
Why is this not happening with Zope?
Because it doesn't apply. "Release early, release often" is for
bleeding edge developers.
Says who? I thought the idea behind it was to get the releases out early, so you
can find the bugs faster and get the releases more stable
> > Someone posted already a fix for this problem. It should not be
> > hard to fix this single problem by exchanging the DateTime.py file
> > on your sites
>
> I'll echo my earlier comment: Whatever happened to "release early,
> release often"?
>
> Why is this not happening with Zope?
Because i
From: "Andreas Jung" <[EMAIL PROTECTED]>
> Someone posted already a fix for this problem. It should not be hard to
fix
> this single problem by exchanging the DateTime.py file on your sites
Yep, it's on http://www.zope.org/Members/regebro/ somewhere.
But I agree that it's time for a bugfix release
Andreas Jung wrote:
Someone posted already a fix for this problem. It should not be hard to fix
this single problem by exchanging the DateTime.py file on your sites
I'll echo my earlier comment: Whatever happened to "release early, release often"?
Why is this not happening with Zope?
cheers,
Andreas Jung <[EMAIL PROTECTED]>:
> Someone posted already a fix for this problem. It should not be hard to fix
> this single problem by exchanging the DateTime.py file on your sites
You miss my point. It may have a trivial fix, but this is a severe bug which
should not be in released software.
> Someone posted already a fix for this problem. It should not be hard to fix
> this single problem by exchanging the DateTime.py file on your sites
That really doesn't matter. The official release on
http://www.zope.org/Products still has the bug.
--
/Magnus
__
Someone posted already a fix for this problem. It should not be hard to fix
this single problem by exchanging the DateTime.py file on your sites
-aj
--On Mittwoch, 27. November 2002 11:18 + seb bacon <[EMAIL PROTECTED]>
wrote:
The DateTime bug in 2.6.0 breaks all of my sites. This must be
The DateTime bug in 2.6.0 breaks all of my sites. This must be true for very
many other people.
If we collectively want use of Zope to multiply 10x, I don't think it's a great
idea to let a major bug like that stay in the latest-and-greatest release.
Can we have a bugfix release?
seb
-
26 matches
Mail list logo
