Re: Frequency of Tomcat Native releases
On 04/10/2015 19:32, Justin wrote: > > | > Did you read the how to build tc-native page? > > Your link requires login to Confluence, so I'm not familiar with any > of the Windows build process other than what I read about APR and > what I read in native/BUILDING. Seems a login shouldn't be required > to read this info. I agree a login should not be required. I've now fixed this (anonymous users were missing the view permission). >> do not have a dependency on a specific msvc runtime > I believe MSYS2 MingW64 GCC and clang compilers should both work > without specific msvcrt: OK. I have no particular preference as long as it meets the requirements. >> Python is not - and hasnever been as far as I am aware - a >> dependency > See line 76 of native/buildconf. That isn't part of the Windows build. The Windows build does require various tools as you'll now be able to see from the Wiki page but python isn't one of them. That looks like it is required for the source release build (that I know I can do when I need to). > If all > patches have to go through devs, I'm sure one of the devs who has > updated before can do this in minutes. I don't understand why user > mailing list should document developer commits and submit patches. You are you one who asked for more frequent releases. The Tomcat community is exactly that. A community. The people here are all volunteers and that means they get to work on whatever they choose to work on. If you want to see more frequent tc-native releases then the best way to make that happen is to volunteer to do the work. I'm willing to contribute my time to help you find your way through the process of getting the native code ready for a release but if you don't want to do the work I'm not going to do it all for you. I have other priorities I'm concentrating on right now. Yes, this is probably better suited to the dev mailing list and I'm happy to move the conversation there if you prefer. On the other hand, the users list has a larger subscriber base and this thread is (hopefully) acting as an advertisement for how folks that want to can get more involved in Tomcat development. Mark - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Frequency of Tomcat Native releases
| > Did you read the how to build tc-native page?
Your link requires login to Confluence, so I'm not familiar with any of the
Windows build process other than what I read about APR and what I read in
native/BUILDING. Seems a login shouldn't be required to read this info.
> do not have a dependency on a specific msvc runtime
I believe MSYS2 MingW64 GCC and clang compilers should both work without
specific msvcrt:
$ which gcc
/mingw64/bin/gcc
$ gcc --version
gcc.exe (Rev3, Built by MSYS2 project) 5.2.0
$ gcc -m64 main.c
$ ldd a.exe
ntdll.dll => /c/Windows/SYSTEM32/ntdll.dll (0x7ff8167a)
KERNEL32.DLL => /c/Windows/system32/KERNEL32.DLL (0x7ff8143f)
KERNELBASE.dll => /c/Windows/system32/KERNELBASE.dll (0x7ff813c6)
msvcrt.dll => /c/Windows/system32/msvcrt.dll (0x7ff813f0)
$ clang --version
clang version 3.7.0 (tags/RELEASE_370/final)
$ clang -m64 main.c
$ ldd a.exe
ntdll.dll => /c/Windows/SYSTEM32/ntdll.dll (0x7ff8167a)
KERNEL32.DLL => /c/Windows/system32/KERNEL32.DLL (0x7ff8143f)
KERNELBASE.dll => /c/Windows/system32/KERNELBASE.dll (0x7ff813c6)
msvcrt.dll => /c/Windows/system32/msvcrt.dll (0x7ff813f0)
> Python is not - and hasnever been as far as I am aware - a dependency
See line 76 of native/buildconf. When I try to 'sh buildconf
--with-apr=$HOME/apr' per BUILDING: Building from the svn tree, in MSYS2
(probably not in the documented build process that I can't read), I get:
ImportError: No module named 'ConfigParser'
If all patches have to go through devs, I'm sure one of the devs who has
updated before can do this in minutes. I don't understand why user mailing list
should document developer commits and submit patches.
On Oct 4, 2015, 5:20:19 AM, Mark Thomas wrote:On 03/10/2015 23:51, Justin wrote:
>> - ensure the changelog is up to date
> Looks like r1681506 could be logged.
Patch please.
>> - versions all correct in source
> $ find . -type f -exec grep '-H' '1\.1\.' '{}' \;...
> ./1.1.x/xdocs/index.xml:...TC-Native-1.1.33 released
> ./1.1.x/xdocs/index.xml:... availability of Tomcat Native 1.1.33 Stable.
> ./1.1.x/xdocs/news/2015.xml:... TC-Native-1.1.33 released">
Looks good.
>> - select and document APR & OpenSSL versions
> Please update APR from 1.5.1 to 1.5.2.
Patch please.
> Please update OpenSSL from 1.0.1m to 1.0.2d.
The last release we did we decided it was to early for 1.0.2. I'd be
prepared to move to 1.0.2 now but that needs confirmation on the dev
list. A separate patch for this should be enough to start that discussion.
>> - check everything builds correctly
> You'd get more volunteers if building APR didn't require MSVC 6.0 or however
> you build .dsw.
Did you read the how to build tc-native page? MSVC is not required.
> In fact, it'd be nice to see many of these projects adopt Gradle and do away
> with many of these old build tools.
The toolchain used is driven by the desire to produce Windows binaries
that do not have a dependency on a specific msvc runtime. In the past we
have had all sorts of difficulties when the JVM depended on a different
version to Tomcat.
I certainly would not object to anything that made the build process
easier for new people to figure out as long as that does not mean
sacrificing the msvc runtime requirement.
> I tried to build Tomcat Native once from repository and found my version of
> Python was too new.
I have no idea what you were trying to build but Python is not - and has
never been as far as I am aware - a dependency for any Tomcat build.
> Gradle allows the flexibility of MSVC, GCC, clang.
I have no strong opinion on which build tool is used to simplify the
current process. If you known Gradle and want to produce a patch then go
for it.
Mark
>
>
>
>
> On Friday, October 2, 2015 5:15 PM, Mark Thomas ma...@apache.org> wrote:
>
>
> On 02/10/2015 19:01, Justin wrote:
>> Can we see more frequent releases of Tomcat Native, especially since
>> it statically links OpenSSL on Windows? I was hoping to see a new
>> release included in Tomcat 8.0.27. There have been a number of
>> changes to both Tomcat Native 1.1.x and OpenSSL 1.0.2.
>> http://svn.apache.org/viewvc/tomcat/native/branches/1.1.x/?view=log
>> https://github.com/openssl/openssl/commits/OpenSSL_1_0_2-stable
>
> I've done the last few tc-native releases because they reached the point
> where they really needed to happen. tc-native isn't my area of expertise
> so I'd be more than happy to see someone else take this on.
>
> More frequent releases are certainly possible and very much the way we
> should be aiming to do things as an Apache project. "Release early and
> release often" is the goal.
>
> What contribution are you (or anyone else reading this) willing/able to
> make to help this process along?
>
> The tc-native release process is documented (ish) here:
> http://svn.apache.org/viewvc/tomcat/native/branches/1.1.x/jnirelease.sh?view=annotate
>
> and
>
> h
Re: Frequency of Tomcat Native releases
On 03/10/2015 23:51, Justin wrote:
>> - ensure the changelog is up to date
> Looks like r1681506 could be logged.
Patch please.
>> - versions all correct in source
> $ find . -type f -exec grep '-H' '1\.1\.' '{}' \;...
> ./1.1.x/xdocs/index.xml:...TC-Native-1.1.33 released
> ./1.1.x/xdocs/index.xml:... availability of Tomcat Native 1.1.33 Stable.
> ./1.1.x/xdocs/news/2015.xml:... TC-Native-1.1.33 released">
Looks good.
>> - select and document APR & OpenSSL versions
> Please update APR from 1.5.1 to 1.5.2.
Patch please.
> Please update OpenSSL from 1.0.1m to 1.0.2d.
The last release we did we decided it was to early for 1.0.2. I'd be
prepared to move to 1.0.2 now but that needs confirmation on the dev
list. A separate patch for this should be enough to start that discussion.
>> - check everything builds correctly
> You'd get more volunteers if building APR didn't require MSVC 6.0 or however
> you build .dsw.
Did you read the how to build tc-native page? MSVC is not required.
> In fact, it'd be nice to see many of these projects adopt Gradle and do away
> with many of these old build tools.
The toolchain used is driven by the desire to produce Windows binaries
that do not have a dependency on a specific msvc runtime. In the past we
have had all sorts of difficulties when the JVM depended on a different
version to Tomcat.
I certainly would not object to anything that made the build process
easier for new people to figure out as long as that does not mean
sacrificing the msvc runtime requirement.
> I tried to build Tomcat Native once from repository and found my version of
> Python was too new.
I have no idea what you were trying to build but Python is not - and has
never been as far as I am aware - a dependency for any Tomcat build.
> Gradle allows the flexibility of MSVC, GCC, clang.
I have no strong opinion on which build tool is used to simplify the
current process. If you known Gradle and want to produce a patch then go
for it.
Mark
>
>
>
>
> On Friday, October 2, 2015 5:15 PM, Mark Thomas wrote:
>
>
> On 02/10/2015 19:01, Justin wrote:
>> Can we see more frequent releases of Tomcat Native, especially since
>> it statically links OpenSSL on Windows? I was hoping to see a new
>> release included in Tomcat 8.0.27. There have been a number of
>> changes to both Tomcat Native 1.1.x and OpenSSL 1.0.2.
>> http://svn.apache.org/viewvc/tomcat/native/branches/1.1.x/?view=log
>> https://github.com/openssl/openssl/commits/OpenSSL_1_0_2-stable
>
> I've done the last few tc-native releases because they reached the point
> where they really needed to happen. tc-native isn't my area of expertise
> so I'd be more than happy to see someone else take this on.
>
> More frequent releases are certainly possible and very much the way we
> should be aiming to do things as an Apache project. "Release early and
> release often" is the goal.
>
> What contribution are you (or anyone else reading this) willing/able to
> make to help this process along?
>
> The tc-native release process is documented (ish) here:
> http://svn.apache.org/viewvc/tomcat/native/branches/1.1.x/jnirelease.sh?view=annotate
>
> and
>
> https://cwiki.apache.org/confluence/display/TOMCAT/Building+the+Tomcat+Native+Connector+binaries+for+Windows
>
> Off the top of my head things that need to be done / checked:
>
> - ensure the changelog is up to date
> - versions all correct in source
> - select and document APR & OpenSSL versions
> - check everything builds correctly
>
> Confirmation that any of the above is ready to go or patches to fix
> things if there are gaps will move a release forward.
>
> I can find the time to apply patches and turn the handle on the release
> if others can do the work to ensure that svn is in a good state to release.
>
> It is a fairly safe bet that anyone helping out substantially on the
> release is going to find themselves with an invitation to become a
> Tomcat committer and the RM for the next release.
>
> Mark
>
> -
> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
> For additional commands, e-mail: users-h...@tomcat.apache.org
>
>
>
>
>
-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Frequency of Tomcat Native releases
> - ensure the changelog is up to date
Looks like r1681506 could be logged.
> - versions all correct in source
$ find . -type f -exec grep '-H' '1\.1\.' '{}' \;...
./1.1.x/xdocs/index.xml:...TC-Native-1.1.33 released
./1.1.x/xdocs/index.xml:... availability of Tomcat Native 1.1.33 Stable.
./1.1.x/xdocs/news/2015.xml:... TC-Native-1.1.33 released">
> - select and document APR & OpenSSL versions
Please update APR from 1.5.1 to 1.5.2. Please update OpenSSL from 1.0.1m to
1.0.2d.
> - check everything builds correctly
You'd get more volunteers if building APR didn't require MSVC 6.0 or however
you build .dsw. In fact, it'd be nice to see many of these projects adopt
Gradle and do away with many of these old build tools. I tried to build Tomcat
Native once from repository and found my version of Python was too new. Gradle
allows the flexibility of MSVC, GCC, clang.
On Friday, October 2, 2015 5:15 PM, Mark Thomas wrote:
On 02/10/2015 19:01, Justin wrote:
> Can we see more frequent releases of Tomcat Native, especially since
> it statically links OpenSSL on Windows? I was hoping to see a new
> release included in Tomcat 8.0.27. There have been a number of
> changes to both Tomcat Native 1.1.x and OpenSSL 1.0.2.
> http://svn.apache.org/viewvc/tomcat/native/branches/1.1.x/?view=log
> https://github.com/openssl/openssl/commits/OpenSSL_1_0_2-stable
I've done the last few tc-native releases because they reached the point
where they really needed to happen. tc-native isn't my area of expertise
so I'd be more than happy to see someone else take this on.
More frequent releases are certainly possible and very much the way we
should be aiming to do things as an Apache project. "Release early and
release often" is the goal.
What contribution are you (or anyone else reading this) willing/able to
make to help this process along?
The tc-native release process is documented (ish) here:
http://svn.apache.org/viewvc/tomcat/native/branches/1.1.x/jnirelease.sh?view=annotate
and
https://cwiki.apache.org/confluence/display/TOMCAT/Building+the+Tomcat+Native+Connector+binaries+for+Windows
Off the top of my head things that need to be done / checked:
- ensure the changelog is up to date
- versions all correct in source
- select and document APR & OpenSSL versions
- check everything builds correctly
Confirmation that any of the above is ready to go or patches to fix
things if there are gaps will move a release forward.
I can find the time to apply patches and turn the handle on the release
if others can do the work to ensure that svn is in a good state to release.
It is a fairly safe bet that anyone helping out substantially on the
release is going to find themselves with an invitation to become a
Tomcat committer and the RM for the next release.
Mark
-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Frequency of Tomcat Native releases
On 02/10/2015 19:01, Justin wrote: > Can we see more frequent releases of Tomcat Native, especially since > it statically links OpenSSL on Windows? I was hoping to see a new > release included in Tomcat 8.0.27. There have been a number of > changes to both Tomcat Native 1.1.x and OpenSSL 1.0.2. > http://svn.apache.org/viewvc/tomcat/native/branches/1.1.x/?view=log > https://github.com/openssl/openssl/commits/OpenSSL_1_0_2-stable I've done the last few tc-native releases because they reached the point where they really needed to happen. tc-native isn't my area of expertise so I'd be more than happy to see someone else take this on. More frequent releases are certainly possible and very much the way we should be aiming to do things as an Apache project. "Release early and release often" is the goal. What contribution are you (or anyone else reading this) willing/able to make to help this process along? The tc-native release process is documented (ish) here: http://svn.apache.org/viewvc/tomcat/native/branches/1.1.x/jnirelease.sh?view=annotate and https://cwiki.apache.org/confluence/display/TOMCAT/Building+the+Tomcat+Native+Connector+binaries+for+Windows Off the top of my head things that need to be done / checked: - ensure the changelog is up to date - versions all correct in source - select and document APR & OpenSSL versions - check everything builds correctly Confirmation that any of the above is ready to go or patches to fix things if there are gaps will move a release forward. I can find the time to apply patches and turn the handle on the release if others can do the work to ensure that svn is in a good state to release. It is a fairly safe bet that anyone helping out substantially on the release is going to find themselves with an invitation to become a Tomcat committer and the RM for the next release. Mark - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Frequency of Tomcat Native releases
Can we see more frequent releases of Tomcat Native, especially since it statically links OpenSSL on Windows? I was hoping to see a new release included in Tomcat 8.0.27. There have been a number of changes to both Tomcat Native 1.1.x and OpenSSL 1.0.2. http://svn.apache.org/viewvc/tomcat/native/branches/1.1.x/?view=log https://github.com/openssl/openssl/commits/OpenSSL_1_0_2-stable
