Mailing List Archive: ModPerl: Dev

Retiring mod_perl 1.3.x

Index | Next | Previous | View Threaded

pgollucci at p6m7g8

Feb 19, 2011, 10:45 AM

Post #1 of 9 (890 views)
Permalink

Retiring mod_perl 1.3.x

In 2010, httpd 1.3.x official went EOL.

In February 2011, the httpd 1.3.x binaries moved officially to
archive.apache.org.

I think its finally time we do the same thing for mod_perl 1.3.x and
dedicate 100% of our resources to 2.0.x/2.2.x.

I'll leave 5 days for comments.

------------------------------------------------------------------------
1024D/DB9B8C1C B90B FBC3 A3A1 C71A 8E70 3F8C 75B8 8FFB DB9B 8C1C
Philip M. Gollucci (pgollucci [at] p6m7g8) c: 703.336.9354
VP Apache Infrastructure; Member, Apache Software Foundation
Committer, FreeBSD Foundation
Consultant, P6M7G8 Inc.
Sr. System Admin, Ridecharge Inc.

Work like you don't need the money,
love like you'll never get hurt,
and dance like nobody's watching.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe [at] perl
For additional commands, e-mail: dev-help [at] perl

torsten.foertsch at gmx

Feb 19, 2011, 10:51 AM

Post #2 of 9 (868 views)
Permalink

Re: Retiring mod_perl 1.3.x [In reply to]

On Saturday, February 19, 2011 19:45:56 Philip M. Gollucci wrote:
> In February 2011, the httpd 1.3.x binaries moved officially to
> archive.apache.org.
>
> I think its finally time we do the same thing for mod_perl 1.3.x and
> dedicate 100% of our resources to 2.0.x/2.2.x.
>
> I'll leave 5 days for comments.

+1

Torsten Förtsch

--
Need professional modperl support? Hire me! (http://foertsch.name)

Like fantasy? http://kabatinte.net

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe [at] perl
For additional commands, e-mail: dev-help [at] perl

fred at redhotpenguin

Feb 19, 2011, 11:15 AM

Post #3 of 9 (870 views)
Permalink

Re: Retiring mod_perl 1.3.x [In reply to]

2011/2/19 Torsten Förtsch <torsten.foertsch [at] gmx>:
> On Saturday, February 19, 2011 19:45:56 Philip M. Gollucci wrote:
>> In February 2011, the httpd 1.3.x binaries moved officially to
>> archive.apache.org.
>>
>> I think its finally time we do the same thing for mod_perl 1.3.x and
>> dedicate 100% of our resources to 2.0.x/2.2.x.
>>
>> I'll leave 5 days for comments.
>
> +1

+/- 0

I think this move is a prudent one, but I'd like to see another mp2
release before we do this. Making this a goal over the next couple of
months is a good idea I think, but I think it would be wise to ask a
few 'what if' questions before we push into this 100%.

Such as:

1) What procedures do we have to go through to end of life mp1?

2) Are there any issues that will prevent users from moving to mp2?

3) What do we do if a security issue with mp1 arises?

4) What effect will this have on mp1 users who have hundreds of
servers running mod_perl1?

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe [at] perl
For additional commands, e-mail: dev-help [at] perl

perrin at elem

Feb 19, 2011, 11:50 AM

Post #4 of 9 (859 views)
Permalink

Re: Retiring mod_perl 1.3.x [In reply to]

I guess my question is how would this be any different from what we're
doing now? Is anyone actively working on mod_perl 1 development,
except when a security issue is raised?

- Perrin

On Sat, Feb 19, 2011 at 1:45 PM, Philip M. Gollucci
<pgollucci [at] p6m7g8> wrote:
> In 2010, httpd 1.3.x official went EOL.
>
> In February 2011, the httpd 1.3.x binaries moved officially to
> archive.apache.org.
>
> I think its finally time we do the same thing for mod_perl 1.3.x and
> dedicate 100% of our resources to 2.0.x/2.2.x.
>
> I'll leave 5 days for comments.
>
> ------------------------------------------------------------------------
> 1024D/DB9B8C1C B90B FBC3 A3A1 C71A 8E70 3F8C 75B8 8FFB DB9B 8C1C
> Philip M. Gollucci (pgollucci [at] p6m7g8) c: 703.336.9354
> VP Apache Infrastructure; Member, Apache Software Foundation
> Committer, FreeBSD Foundation
> Consultant, P6M7G8 Inc.
> Sr. System Admin, Ridecharge Inc.
>
> Work like you don't need the money,
> love like you'll never get hurt,
> and dance like nobody's watching.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe [at] perl
> For additional commands, e-mail: dev-help [at] perl
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe [at] perl
For additional commands, e-mail: dev-help [at] perl

pgollucci at p6m7g8

Feb 19, 2011, 1:00 PM

Post #5 of 9 (818 views)
Permalink

Re: Retiring mod_perl 1.3.x [In reply to]

On 2/19/2011 2:15 PM, Fred Moyer wrote:
> 1) What procedures do we have to go through to end of life mp1?
Officially announce it on announce@ lists and maybe dev@
move the dist files to archives.apache.org only.

> 2) Are there any issues that will prevent users from moving to mp2?
All the normal ones, not going to change. Period.

> 3) What do we do if a security issue with mp1 arises?
Nothing, its EOL. Thats the point.

>
> 4) What effect will this have on mp1 users who have hundreds of
> servers running mod_perl1?
Nothing, they aren't going to upgrade. The dist file is still available
but doesn't burden our mirror network.

--
------------------------------------------------------------------------
1024D/DB9B8C1C B90B FBC3 A3A1 C71A 8E70 3F8C 75B8 8FFB DB9B 8C1C
Philip M. Gollucci (pgollucci [at] p6m7g8) c: 703.336.9354
VP Apache Infrastructure; Member, Apache Software Foundation
Committer, FreeBSD Foundation
Consultant, P6M7G8 Inc.
Sr. System Admin, Ridecharge Inc.

Work like you don't need the money,
love like you'll never get hurt,
and dance like nobody's watching.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe [at] perl
For additional commands, e-mail: dev-help [at] perl

pgollucci at p6m7g8

Feb 19, 2011, 1:02 PM

Post #6 of 9 (865 views)
Permalink

Re: Retiring mod_perl 1.3.x [In reply to]

On 2/19/2011 2:50 PM, Perrin Harkins wrote:
> I guess my question is how would this be any different from what we're
> doing now? Is anyone actively working on mod_perl 1 development,
> except when a security issue is raised?
Its 'official', good practice, and prudent :)

The security practice is biggest thing. But the way we handle it
standard with other ASF projects and other 3rd Parties (i.e. FreeBSD).

--
------------------------------------------------------------------------
1024D/DB9B8C1C B90B FBC3 A3A1 C71A 8E70 3F8C 75B8 8FFB DB9B 8C1C
Philip M. Gollucci (pgollucci [at] p6m7g8) c: 703.336.9354
VP Apache Infrastructure; Member, Apache Software Foundation
Committer, FreeBSD Foundation
Consultant, P6M7G8 Inc.
Sr. System Admin, Ridecharge Inc.

Work like you don't need the money,
love like you'll never get hurt,
and dance like nobody's watching.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe [at] perl
For additional commands, e-mail: dev-help [at] perl

fred at redhotpenguin

Feb 19, 2011, 8:41 PM

Post #7 of 9 (857 views)
Permalink

Re: Retiring mod_perl 1.3.x [In reply to]

On Sat, Feb 19, 2011 at 1:02 PM, Philip M. Gollucci
<pgollucci [at] p6m7g8> wrote:
> On 2/19/2011 2:50 PM, Perrin Harkins wrote:
>> I guess my question is how would this be any different from what we're
>> doing now? Is anyone actively working on mod_perl 1 development,
>> except when a security issue is raised?
> Its 'official', good practice, and prudent :)

+1 for releasing 1.32 - there is a non security compilation fix, and
I'll be committing another change discussed off list.

The more I think about it, the less it makes sense to spend tuits on
retiring mp 1.3. I would however say that future versions of
Apache::Test et al should not need to support mod_perl 1 at the same
time as supporting mod_perl2.

For instance, the next release of Apache::Reload could be
Apache2::Reload. It can use Apache2::Build to do all the mp2
bootstrapping. It is unlikely that someone out on the list will get
an itch and fix an issue with Apache::Reload on mod_perl 1 at this
point. If they do, the best practice would be to put it in their own
repository; I don't see hordes of mp1 contributors suddenly showing up
and showering us with patches :)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe [at] perl
For additional commands, e-mail: dev-help [at] perl

fred at redhotpenguin

Feb 19, 2011, 9:05 PM

Post #8 of 9 (858 views)
Permalink

Re: Retiring mod_perl 1.3.x [In reply to]

One more comment - if this helps take some load off infrastructure@
and allows them to give us help with other needs, I see benefits
there.

So my official vote is +1 for retiring after the 1.32 final release :)

On Sat, Feb 19, 2011 at 1:02 PM, Philip M. Gollucci
<pgollucci [at] p6m7g8> wrote:
> On 2/19/2011 2:50 PM, Perrin Harkins wrote:
>> I guess my question is how would this be any different from what we're
>> doing now? Is anyone actively working on mod_perl 1 development,
>> except when a security issue is raised?
> Its 'official', good practice, and prudent :)
>
> The security practice is biggest thing. But the way we handle it
> standard with other ASF projects and other 3rd Parties (i.e. FreeBSD).
>
>
>
> --
> ------------------------------------------------------------------------
> 1024D/DB9B8C1C B90B FBC3 A3A1 C71A 8E70 3F8C 75B8 8FFB DB9B 8C1C
> Philip M. Gollucci (pgollucci [at] p6m7g8) c: 703.336.9354
> VP Apache Infrastructure; Member, Apache Software Foundation
> Committer, FreeBSD Foundation
> Consultant, P6M7G8 Inc.
> Sr. System Admin, Ridecharge Inc.
>
> Work like you don't need the money,
> love like you'll never get hurt,
> and dance like nobody's watching.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe [at] perl
> For additional commands, e-mail: dev-help [at] perl
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe [at] perl
For additional commands, e-mail: dev-help [at] perl

pgollucci at p6m7g8

Feb 20, 2011, 10:35 AM

Post #9 of 9 (854 views)
Permalink

Re: Retiring mod_perl 1.3.x [In reply to]

On 2/20/2011 12:05 AM, Fred Moyer wrote:
> One more comment - if this helps take some load off infrastructure@
> and allows them to give us help with other needs, I see benefits
> there.
>
> So my official vote is +1 for retiring after the 1.32 final release :)
No objection to doing 1.32 1st.

--
------------------------------------------------------------------------
1024D/DB9B8C1C B90B FBC3 A3A1 C71A 8E70 3F8C 75B8 8FFB DB9B 8C1C
Philip M. Gollucci (pgollucci [at] p6m7g8) c: 703.336.9354
VP Apache Infrastructure; Member, Apache Software Foundation
Committer, FreeBSD Foundation
Consultant, P6M7G8 Inc.
Sr. System Admin, Ridecharge Inc.

Work like you don't need the money,
love like you'll never get hurt,
and dance like nobody's watching.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe [at] perl
For additional commands, e-mail: dev-help [at] perl

Index | Next | Previous | View Threaded

Interested in having your list archived? Contact Gossamer Threads