Jim Gallacher wrote ..
> Graham Dumpleton wrote:
> > Is my list of suggested JIRA items then seen as being reasonable for
> > such a projected release?
>
> This seems reasonable, since we have either already committed the fixes
> or have patches available (I think).
I don't have changes ready for
Graham Dumpleton wrote:
Is my list of suggested JIRA items then seen as being reasonable for
such a projected release?
This seems reasonable, since we have either already committed the fixes
or have patches available (I think).
Do we want to create a new JIRA issue for the mutex directory i
Is my list of suggested JIRA items then seen as being reasonable for
such a projected release?
Do we want to create a new JIRA issue for the mutex directory issue and
also include a fix for that, but limit it to just an option to configure
to override the directory?
Graham
Nicolas Lehuen wrote .
Grisha wrote ..
>
> On Tue, 14 Feb 2006, Nicolas Lehuen wrote:
>
> > 2006/2/14, Graham Dumpleton <[EMAIL PROTECTED]>:
> > [...]
> >> If we want to go down the path of having interim 3.2 bug rollup releases
> >> while 3.3 is being developed, might I suggest that we target the following
> >> for su
On Tue, 14 Feb 2006, Nicolas Lehuen wrote:
2006/2/14, Graham Dumpleton <[EMAIL PROTECTED]>:
[...]
If we want to go down the path of having interim 3.2 bug rollup releases
while 3.3 is being developed, might I suggest that we target the following
for such a release in the near future.
MODPYTHO
Nicolas Lehuen wrote:
Based on today's traffic on the mailing lists, I think that we should
go for a short-term 3.2.8 release of mod_python, with certified Apache
2.2 support on multiple platforms. The code is only there but I
suppose we'll need a lot of testing, so maybe we could expect to
relea
2006/2/14, Nicolas Lehuen <[EMAIL PROTECTED]>:
> Based on today's traffic on the mailing lists, I think that we should
> go for a short-term 3.2.8 release of mod_python, with certified Apache
> 2.2 support on multiple platforms. The code is only there but I
> suppose we'll need a lot of testing, so
Based on today's traffic on the mailing lists, I think that we should
go for a short-term 3.2.8 release of mod_python, with certified Apache
2.2 support on multiple platforms. The code is only there but I
suppose we'll need a lot of testing, so maybe we could expect to
release this in a month or tw
2006/2/14, Graham Dumpleton <[EMAIL PROTECTED]>:
[...]
> If we want to go down the path of having interim 3.2 bug rollup releases
> while 3.3 is being developed, might I suggest that we target the following
> for such a release in the near future.
>
> MODPYTHON-77
>
> The Simplified GIL Aquisitio
Jim Gallacher wrote ..
> Jorey Bump wrote:
> > Jim Gallacher wrote:
> >
> >> This is how I would set priorities:
> >
> >
> >> Try and assign most of the issues to someone. This is a bit of PR
> >> spin, but I think it looks bad when there are a large number of open
> >> issues with no assignee.
Graham Dumpleton wrote:
As Jim pointed out a while back, we need to get going on mod_python 3.3
before I fill up JIRA with another page of bug reports or suggestions.
I think you already *have* filled another page since I made that comment. ;)
That said, how do we want to proceed on this? Do
11 matches
Mail list logo
