Actually from my reading of jk_version.h this change was already made in the test release. [And the version string shows up as 1.2.5 on Windows.]

Mike Anderson wrote:

There is one minor change to jk_version.h so that the module reports
that it is version 1.2.5 instead of 1.2.5-dev.  If you already cheated
and modified that locally, or you don't care what it reports, you should
be fine.

Mike Anderson



[EMAIL PROTECTED] 9/25/2003 8:00:54 AM >>>


The test release at cvs.apache.org/~glenn is what will be released
with no changes and does reflect the source which was tagged as
mod_jk_1_2_5.

So yes, you can use binaries built from that source as mod_jk 1.2.5
release binaries.

Regards,

Glenn

Jess Holle wrote:


Were there any changes since the test release, i.e. does the tagging





reflect (minus release notes, etc) the test release?

[I'm asking as I've built binaries for all platforms I need from the





test release and would like to avoid rebuilding all of them....]

Glenn Nielsen wrote:



Glenn Nielsen wrote:



Henri Gomez wrote:



Glenn, could you tag JTC 1.2.5 so I could commit my work on JTC

?


I would like to see modjk 1.2.5 tagged/released before committing
this.  I was waiting on a report for Windows before releasign,
we now have that.  I'll post a release vote shortly.



mod_jk_1_2_5 has been tagged in CVS, the HEAD is now mod_jk


1.2.6-dev.


Glenn





---------------------------------------------------------------------


To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]










---------------------------------------------------------------------


To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]






---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]



--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]







Reply via email to