|
Home > Archive > Apache Mod-Python > December 2006 > Release of mod_python 3.3.
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Release of mod_python 3.3.
|
|
| Graham Dumpleton 2006-12-06, 7:13 am |
| There were no more comments on basic apache.import_module()
documentation so I have tweaked a few last things, committed it
and marked as resolved the final issue in JIRA tagged for 3.3.
Thus, unless anyone else has got any last minute issues, we should
be good to go with a 3.3 release now.
Jim, would you like to get the ball rolling when you have some time.
Thanks to everyone who has contributed.
Graham
| |
| Jim Gallacher 2006-12-06, 1:14 pm |
| Graham Dumpleton wrote:
> There were no more comments on basic apache.import_module()
> documentation so I have tweaked a few last things, committed it
> and marked as resolved the final issue in JIRA tagged for 3.3.
>
> Thus, unless anyone else has got any last minute issues, we should
> be good to go with a 3.3 release now.
>
> Jim, would you like to get the ball rolling when you have some time.
>
> Thanks to everyone who has contributed.
>
> Graham
I do want to change the requirements in the docs. Currently it reads:
* Python 2.2.1 or later. Earlier versions of Python will not work.
* Apache 2.0.47 or later (For Apache 1.3.x, use mod_python version
2.7.x).
We decided to officially bump the Python version requirement to 2.3, but
are we still OK with Apache 2.0.47, or should we bump this to something
like 2.0.54 as well?
Once that is decided I'll roll the tarball, likely tonight. I assume
we'll use release-3-3-0b as the tag?
Jim
| |
| Graham Dumpleton 2006-12-07, 7:13 am |
|
On 07/12/2006, at 12:42 AM, Jim Gallacher wrote:
> Graham Dumpleton wrote:
>
> I do want to change the requirements in the docs. Currently it reads:
>
>
> * Python 2.2.1 or later. Earlier versions of Python will not work.
> * Apache 2.0.47 or later (For Apache 1.3.x, use mod_python
> version 2.7.x).
>
>
> We decided to officially bump the Python version requirement to 2.3,
Yep.
> but are we still OK with Apache 2.0.47, or should we bump this to
> something like 2.0.54 as well?
Our last round of testing only used 2.0.54 or later as you know, so
saying it
has only been tested on that or later is probably reasonable. We can
always
update it later if we get people with older versions of Apache
testing it.
> Once that is decided I'll roll the tarball, likely tonight. I
> assume we'll use release-3-3-0b as the tag?
Based on past conventions, that tag seems appropriate. If all is okay
do we
then just retag as 3.0.1?
Graham
| |
| Graham Dumpleton 2006-12-07, 7:13 am |
|
On 07/12/2006, at 9:14 PM, Graham Dumpleton wrote:
>
>
> Based on past conventions, that tag seems appropriate. If all is
> okay do we
> then just retag as 3.0.1?
Hmmm, I think you know what I mean, we don't actually want to go
backwards. :-)
Graham
| |
| Jim Gallacher 2006-12-07, 7:13 am |
| Graham Dumpleton wrote:
>
> On 07/12/2006, at 12:42 AM, Jim Gallacher wrote:
>
>
> Yep.
>
>
> Our last round of testing only used 2.0.54 or later as you know, so
> saying it
> has only been tested on that or later is probably reasonable. We can always
> update it later if we get people with older versions of Apache testing it.
>
>
> Based on past conventions, that tag seems appropriate. If all is okay do we
> then just retag as 3.0.1?
OK. I probably won't get to the tagging and rolling until tonight. (It's
morning here now).
Jim
|
|
|
|
|