You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@httpd.apache.org by "William A. Rowe, Jr." <wr...@rowe-clan.net> on 2006/07/07 07:40:52 UTC
[VOTE] Release mod_aspdotnet build 2004?
Build 2004 of mod_aspdotnet is prepared (after a number of abortive
attempts due to the whole 2.0/2.2 partitioning and renaming of apache.exe,
along with switching flavors of InstallShield to a version I have installed)
and seeking voters. The update is here;
http://httpd.apache.org/dev/dist/mod_aspdotnet/
Please cast your +/- 1's to release mod_aspdotnet-2.x.0.2004-source.zip
(along with associated binaries ...2.0.0.2004.msi and ...2.2.0.2004.msi,
one corresponding to 2.0.44 and later, the other to 2.2.2 and later).
This is the last expected release on the Visual Studio .NET (al la 2002)
compiler toolchain; the next effort is porting it to VS 2005 (al la, the
one available in a free flavor). Porting breaks compatibility with the
older tools, since VS 2005's C++.NET schema is miles beyond 2002. For
example, a reference becomes a reference, not an overloaded psuedo-pointer.
Bill
Re: [VOTE] Release mod_aspdotnet build 2004?
Posted by "James Park (pencil_ethics)" <pe...@gmail.com>.
Binary looks good on 2.0.58 - runs Windows Server Update Services with
zero problems. Because I'm roughly 10000 km from my test machine (and
will remain so until July 27), I haven't gotten around to testing it on
2.2.2, but I believe there will be no problems on 2.2.x. Can't compile
source either, owing to the fact that I do not have VS.NET 2002
installed on this machine. I give this build my non-binding +1.
To everyone out there, especially the PMC: _please_ don't let
mod_aspdotnet die out so easily... mod_aspdotnet is the only hope for
Windows users who despise IIS but do need ASP.NET. :( Throw in your
votes before 7/17 and make the effort to save this module from its Doomsday.
Re: [VOTE] Release mod_aspdotnet build 2004?
Posted by "William A. Rowe, Jr." <wr...@rowe-clan.net>.
Ping to the committee and interested users;
vote began early on 7/7 and will close early on 7/17. Three +1's of the PMC
are required to release this software, with more +'s than -'s. Other voters
are welcome to chime in with advisory votes to help the PMC.
On 7/17 the software will be released, or this software will be ejected from
the httpd PMC and the module officially shuttered. This is just your friendly
midpoint reminder.
And after my own review (which I don't until after rolling it), +1 for release.
Bill
William A. Rowe, Jr. wrote:
> Build 2004 of mod_aspdotnet is prepared (after a number of abortive
> attempts due to the whole 2.0/2.2 partitioning and renaming of apache.exe,
> along with switching flavors of InstallShield to a version I have
> installed)
> and seeking voters. The update is here;
>
> http://httpd.apache.org/dev/dist/mod_aspdotnet/
>
> Please cast your +/- 1's to release mod_aspdotnet-2.x.0.2004-source.zip
> (along with associated binaries ...2.0.0.2004.msi and ...2.2.0.2004.msi,
> one corresponding to 2.0.44 and later, the other to 2.2.2 and later).
>
> This is the last expected release on the Visual Studio .NET (al la 2002)
> compiler toolchain; the next effort is porting it to VS 2005 (al la, the
> one available in a free flavor). Porting breaks compatibility with the
> older tools, since VS 2005's C++.NET schema is miles beyond 2002. For
> example, a reference becomes a reference, not an overloaded psuedo-pointer.
>
> Bill
>
> .
>
Re: [TALLY] Release mod_aspdotnet build 2004?
Posted by Steffen <in...@apachelounge.com>.
Is this the end of mod_aspdotnet ? Or it is not anymore under the ASF flag ?
I know quite some (Win)Apacherians using mod_aspdotnet. I am wondering if the Vote-system is working for this kind of mods, special when it is related to Windows (we all know that most, pmc members?, here are dedicated to *nix flavors). I have no insight in the ASF vote-system, not sure I could vote.
I build and running now version 2004 without issues.
Steffen
----- Original Message -----
From: Jorge Schrauwen
To: dev@httpd.apache.org
Sent: Wednesday, July 19, 2006 16:29
Subject: Re: [TALLY] Release mod_aspdotnet build 2004?
This slightly worries me...
Other modules in the early phase of incubation that looks promesing like mod_ftp might end up having simular fates!
Is placing interesing modules like mod_aspdotnet, mod_ftp,... in a seperated project a good idea?
Maybe they live longer if there where part of the httpd-truck?
Jorge
On 7/19/06, William A. Rowe, Jr. < wrowe@rowe-clan.net> wrote:
Summary;
+1 binding: wrowe
+1 nonbinding feedback (with qualitative data) from:
Jorge Schrauwen
James Park (pencil_ethics)
Trent Nelson
As none of the other pmc members care to inspect the source tarball, the
vote fails. As Roy has raised concerns about httpd's ongoing ownership,
even of the prior release, that too will be removed from the active
www.apache.org/dist/httpd/mod_aspdotnet location. archive.apache.org is
a lovely permanent museum for that wrinkle in time (2.0.0.2000 21 Nov 2004).
As 2.0.4 and the various snapshots between now and then are not releases,
those have been removed from /dev/dist. It will take me a few days to find
the free cycles to expunge the trunk of httpd/docs/manual/, downloads.cgi,
etc and then remove /dist/httpd/mod_aspdotnet.
As there is no oversight going on here, no further commits will occur to
bring mod_aspdotnet to Visual Studio 2005 here.
What does the list want to do with the unreleased mod_arm4 and mod_aspdotnet
code repositories? Do we want to create a /repos/asf/httpd/attic/ repository
for abandoned/orphaned httpd code? Or simply svn rm them, knowing they still
persist at certain points in history and can be resurrected?
To those disappointed, I share your disappointment, but have no regret. This
is what it is. I have spent considerable time reviewing the history of posts
to cli-dev, cli-users, and the bugtraq database. No specific individuals
stand out as frequent posters of bug fixes (not that many were needed), peer
to peer user feedback authors etc. Obviously one solution would be to draft the
few that express an interest here and now, but the httpd project (appropriately)
expects a reasonable track record to avoid exactly this sort of issue.
Although this was a rather mature module from it's inception, with a very short
list of issues that users wanted addressed, it certainly attracts many more
users than developers. The net code changes since it was granted two years ago
are less than 250 LoC, and developing -within- the framework has much more
interest than developing the -module-, itself.
I'm afraid this is no different than the passing of JRun and other similar, now
abandoned code. Developers and their technologies move on. It would be amusing
if the project spent 5% of the effort that's invested in Apache 1.3 to review
this release, but that wasn't to be.
Sadly yours,
Bill
William A. Rowe, Jr. wrote:
> Build 2004 of mod_aspdotnet is prepared (after a number of abortive
> attempts due to the whole 2.0/2.2 partitioning and renaming of apache.exe,
> along with switching flavors of InstallShield to a version I have
> installed)
> and seeking voters. The update is here;
>
> http://httpd.apache.org/dev/dist/mod_aspdotnet/
>
> Please cast your +/- 1's to release mod_aspdotnet-2.x.0.2004-source.zip
> (along with associated binaries ...2.0.0.2004.msi and ...2.2.0.2004.msi,
> one corresponding to 2.0.44 and later, the other to 2.2.2 and later).
>
> This is the last expected release on the Visual Studio .NET (al la 2002)
> compiler toolchain; the next effort is porting it to VS 2005 (al la, the
> one available in a free flavor). Porting breaks compatibility with the
> older tools, since VS 2005's C++.NET schema is miles beyond 2002. For
> example, a reference becomes a reference, not an overloaded psuedo-pointer.
>
> Bill
>
> .
>
--
~Jorge
Re: [TALLY] Release mod_aspdotnet build 2004?
Posted by Jorge Schrauwen <jo...@gmail.com>.
This slightly worries me...
Other modules in the early phase of incubation that looks promesing like
mod_ftp might end up having simular fates!
Is placing interesing modules like mod_aspdotnet, mod_ftp,... in a seperated
project a good idea?
Maybe they live longer if there where part of the httpd-truck?
Jorge
On 7/19/06, William A. Rowe, Jr. <wr...@rowe-clan.net> wrote:
>
> Summary;
>
> +1 binding: wrowe
>
> +1 nonbinding feedback (with qualitative data) from:
>
> Jorge Schrauwen
> James Park (pencil_ethics)
> Trent Nelson
>
> As none of the other pmc members care to inspect the source tarball, the
> vote fails. As Roy has raised concerns about httpd's ongoing ownership,
> even of the prior release, that too will be removed from the active
> www.apache.org/dist/httpd/mod_aspdotnet location. archive.apache.org is
> a lovely permanent museum for that wrinkle in time (2.0.0.2000 21 Nov
> 2004).
> As 2.0.4 and the various snapshots between now and then are not releases,
> those have been removed from /dev/dist. It will take me a few days to
> find
> the free cycles to expunge the trunk of httpd/docs/manual/, downloads.cgi,
> etc and then remove /dist/httpd/mod_aspdotnet.
>
> As there is no oversight going on here, no further commits will occur to
> bring mod_aspdotnet to Visual Studio 2005 here.
>
> What does the list want to do with the unreleased mod_arm4 and
> mod_aspdotnet
> code repositories? Do we want to create a /repos/asf/httpd/attic/
> repository
> for abandoned/orphaned httpd code? Or simply svn rm them, knowing they
> still
> persist at certain points in history and can be resurrected?
>
> To those disappointed, I share your disappointment, but have no
> regret. This
> is what it is. I have spent considerable time reviewing the history of
> posts
> to cli-dev, cli-users, and the bugtraq database. No specific individuals
> stand out as frequent posters of bug fixes (not that many were needed),
> peer
> to peer user feedback authors etc. Obviously one solution would be to
> draft the
> few that express an interest here and now, but the httpd project
> (appropriately)
> expects a reasonable track record to avoid exactly this sort of issue.
>
> Although this was a rather mature module from it's inception, with a very
> short
> list of issues that users wanted addressed, it certainly attracts many
> more
> users than developers. The net code changes since it was granted two
> years ago
> are less than 250 LoC, and developing -within- the framework has much more
> interest than developing the -module-, itself.
>
> I'm afraid this is no different than the passing of JRun and other
> similar, now
> abandoned code. Developers and their technologies move on. It would be
> amusing
> if the project spent 5% of the effort that's invested in Apache 1.3 to
> review
> this release, but that wasn't to be.
>
> Sadly yours,
>
> Bill
>
>
>
> William A. Rowe, Jr. wrote:
> > Build 2004 of mod_aspdotnet is prepared (after a number of abortive
> > attempts due to the whole 2.0/2.2 partitioning and renaming of
> apache.exe,
> > along with switching flavors of InstallShield to a version I have
> > installed)
> > and seeking voters. The update is here;
> >
> > http://httpd.apache.org/dev/dist/mod_aspdotnet/
> >
> > Please cast your +/- 1's to release mod_aspdotnet-2.x.0.2004-source.zip
> > (along with associated binaries ...2.0.0.2004.msi and ...2.2.0.2004.msi,
> > one corresponding to 2.0.44 and later, the other to 2.2.2 and later).
> >
> > This is the last expected release on the Visual Studio .NET (al la 2002)
> > compiler toolchain; the next effort is porting it to VS 2005 (al la, the
> > one available in a free flavor). Porting breaks compatibility with the
> > older tools, since VS 2005's C++.NET schema is miles beyond 2002. For
> > example, a reference becomes a reference, not an overloaded
> psuedo-pointer.
> >
> > Bill
> >
> > .
> >
>
>
>
--
~Jorge
Re: [TALLY] Release mod_aspdotnet build 2004?
Posted by "William A. Rowe, Jr." <wr...@rowe-clan.net>.
Summary;
+1 binding: wrowe
+1 nonbinding feedback (with qualitative data) from:
Jorge Schrauwen
James Park (pencil_ethics)
Trent Nelson
As none of the other pmc members care to inspect the source tarball, the
vote fails. As Roy has raised concerns about httpd's ongoing ownership,
even of the prior release, that too will be removed from the active
www.apache.org/dist/httpd/mod_aspdotnet location. archive.apache.org is
a lovely permanent museum for that wrinkle in time (2.0.0.2000 21 Nov 2004).
As 2.0.4 and the various snapshots between now and then are not releases,
those have been removed from /dev/dist. It will take me a few days to find
the free cycles to expunge the trunk of httpd/docs/manual/, downloads.cgi,
etc and then remove /dist/httpd/mod_aspdotnet.
As there is no oversight going on here, no further commits will occur to
bring mod_aspdotnet to Visual Studio 2005 here.
What does the list want to do with the unreleased mod_arm4 and mod_aspdotnet
code repositories? Do we want to create a /repos/asf/httpd/attic/ repository
for abandoned/orphaned httpd code? Or simply svn rm them, knowing they still
persist at certain points in history and can be resurrected?
To those disappointed, I share your disappointment, but have no regret. This
is what it is. I have spent considerable time reviewing the history of posts
to cli-dev, cli-users, and the bugtraq database. No specific individuals
stand out as frequent posters of bug fixes (not that many were needed), peer
to peer user feedback authors etc. Obviously one solution would be to draft the
few that express an interest here and now, but the httpd project (appropriately)
expects a reasonable track record to avoid exactly this sort of issue.
Although this was a rather mature module from it's inception, with a very short
list of issues that users wanted addressed, it certainly attracts many more
users than developers. The net code changes since it was granted two years ago
are less than 250 LoC, and developing -within- the framework has much more
interest than developing the -module-, itself.
I'm afraid this is no different than the passing of JRun and other similar, now
abandoned code. Developers and their technologies move on. It would be amusing
if the project spent 5% of the effort that's invested in Apache 1.3 to review
this release, but that wasn't to be.
Sadly yours,
Bill
William A. Rowe, Jr. wrote:
> Build 2004 of mod_aspdotnet is prepared (after a number of abortive
> attempts due to the whole 2.0/2.2 partitioning and renaming of apache.exe,
> along with switching flavors of InstallShield to a version I have
> installed)
> and seeking voters. The update is here;
>
> http://httpd.apache.org/dev/dist/mod_aspdotnet/
>
> Please cast your +/- 1's to release mod_aspdotnet-2.x.0.2004-source.zip
> (along with associated binaries ...2.0.0.2004.msi and ...2.2.0.2004.msi,
> one corresponding to 2.0.44 and later, the other to 2.2.2 and later).
>
> This is the last expected release on the Visual Studio .NET (al la 2002)
> compiler toolchain; the next effort is porting it to VS 2005 (al la, the
> one available in a free flavor). Porting breaks compatibility with the
> older tools, since VS 2005's C++.NET schema is miles beyond 2002. For
> example, a reference becomes a reference, not an overloaded psuedo-pointer.
>
> Bill
>
> .
>
Re: [VOTE] Release mod_aspdotnet build 2004?
Posted by "William A. Rowe, Jr." <wr...@rowe-clan.net>.
WDaquell wrote:
> William A. Rowe, Jr. wrote:
>> FWIW - everyone can vote ;-) It's a matter of the counting that's the
>> issue. In any case thank you for the testing and your feedback.
> If anyone can vote... then +1 from me.
Thanks Daquell :) But can you please mention what you reviewed or tested,
so that other PMC members can cast educated votes based on your decision?
Re: [VOTE] Release mod_aspdotnet build 2004?
Posted by WDaquell <wd...@gmail.com>.
William A. Rowe, Jr. wrote:
> FWIW - everyone can vote ;-) It's a matter of the counting that's the
> issue. In any case thank you for the testing and your feedback.
If anyone can vote... then +1 from me.
-Daquell
Re: [VOTE] Release mod_aspdotnet build 2004?
Posted by "William A. Rowe, Jr." <wr...@rowe-clan.net>.
Jorge Schrauwen wrote:
> Well i can't vote but since no-one seem to be replying...
FWIW - everyone can vote ;-) It's a matter of the counting that's the
issue. In any case thank you for the testing and your feedback.
x46 e.g. x64 amd build of 2.2.2? You self compiled mod_aspdotnet from the
.zip source package? It would be additional useful information.
Re: [VOTE] Release mod_aspdotnet build 2004?
Posted by Jorge Schrauwen <jo...@gmail.com>.
Well i can't vote but since no-one seem to be replying...
I've installed it on:
OS: Windows XP Pro x46
Server: httpd 2.2.2 (self compiled)
I tested a few ASP.net sample I found on the net and all worked.
On 7/7/06, William A. Rowe, Jr. <wr...@rowe-clan.net> wrote:
>
> Build 2004 of mod_aspdotnet is prepared (after a number of abortive
> attempts due to the whole 2.0/2.2 partitioning and renaming of apache.exe,
> along with switching flavors of InstallShield to a version I have
> installed)
> and seeking voters. The update is here;
>
> http://httpd.apache.org/dev/dist/mod_aspdotnet/
>
> Please cast your +/- 1's to release mod_aspdotnet-2.x.0.2004-source.zip
> (along with associated binaries ...2.0.0.2004.msi and ...2.2.0.2004.msi,
> one corresponding to 2.0.44 and later, the other to 2.2.2 and later).
>
> This is the last expected release on the Visual Studio .NET (al la 2002)
> compiler toolchain; the next effort is porting it to VS 2005 (al la, the
> one available in a free flavor). Porting breaks compatibility with the
> older tools, since VS 2005's C++.NET schema is miles beyond 2002. For
> example, a reference becomes a reference, not an overloaded
> psuedo-pointer.
>
> Bill
>
--
~Jorge