Yoav Shapira wrote:
I'll tag and cut 5.5.14 tomorrow like a new release. I don't want to
re-tag 5.5.13, I think that would confuse users more. I'll make the
changes clear in the release announcement email (that's why I wanted
clarification myself ;)).
I'm planning to do it at 9am my time, whic
Mladen Turk wrote:
Hi,
I know, it's been only couple of days, but the 5.5.13 build is broken
because we did not tag the tomcat-native (APR) to 1.1.1 version, that
is required because of extra API.
Numbers are cheap, burn another. Once it's tagged and rolled, even if it's
not released, it's be
Yoav Shapira wrote:
I'm planning to do it at 9am my time, which is 1400h UTC/GMT tomorrow,
December 6th.
OK.
I've committed the changes and tag the native.
The sources are at:
http://www.apache.org/dist/tomcat/tomcat-connectors/native/
They are also at:
http://ftp.heanet.ie/pub/tomcat/native/
Yoav Shapira wrote:
I'm planning to do it at 9am my time, which is 1400h UTC/GMT tomorrow,
December 6th.
Perfect.
By that time the mirrors will pick up
the new tomcat-native-1.1.1.tar.gz.
Regards,
Mladen.
-
To unsubscribe, e
Hi,
>. In that case the build would fail instead creating a wrong one.
Ah, OK, that's good.
> I'll update all that later this evening, so we can retag
> the 5.5.13/5.5.14 tomorrow. OK?
I'll tag and cut 5.5.14 tomorrow like a new release. I don't want to
re-tag 5.5.13, I think that would confus
Yoav Shapira wrote:
Hi,
Installer has an task for downloading binaries, so, since it poinits
to the old version it would be downloaded.
The second is that the tomcat-native.tar.gz is also downloaded
during build, so again the old version is used, and the user
must use the version from SVN if h
Hi,
> Installer has an task for downloading binaries, so, since it poinits
> to the old version it would be downloaded.
> The second is that the tomcat-native.tar.gz is also downloaded
> during build, so again the old version is used, and the user
> must use the version from SVN if he wish that co
Mladen Turk wrote:
> Yoav Shapira wrote:
> > This is probably a dumb question, but I'll ask anyways. Why isn't
> > this as simple as a user who downloaded 5.5.13 already going to
> > download the updated connectors/APR and plugging that in? Why does it
> > have to be integrated into the release o
Yoav Shapira wrote:
This is probably a dumb question, but I'll ask anyways. Why isn't
this as simple as a user who downloaded 5.5.13 already going to
download the updated connectors/APR and plugging that in? Why does it
have to be integrated into the release of Tomcat itself, especially
since
Hi,
I'm hesitant to re-tag or re-release 5.5.13, but I have no problem
cutting a 5.5.14 as soon as tomorrow if you so desire. But before I
do either, let me try to make sure I understand the issue.
The tomcat.nsi and/or build.xml files have a hard-coded version number
for the API we want, and thi
Hi,
I know, it's been only couple of days, but the 5.5.13 build is broken
because we did not tag the tomcat-native (APR) to 1.1.1 version, that
is required because of extra API.
Perhaps we can retag the 5.5.13 because the needed changes are in
nsi installer script and tomcat-native.tar.gz source
11 matches
Mail list logo
