Hi folks, I won't reply to the other response messsages but this message because I believe everyone understand what Mike's intention was; to show a piece of great software to the community rather than breaking the rule.
On 2/1/07, Mike Heath <[EMAIL PROTECTED]> wrote:
Trustin, Thanks for holding me to the Apache process. So, don't think of it as a release then. Perhaps the term 'release' to too formal for what this is. Can we think of it as a conveniently downloadable build for testing purposes?
Sure. You could say 'please review this snapshot build.' I know what your intention was, so it's no problem. Everybody makes a mistake. :) This code is certainly not ready for production use yet. My goal was
to get a .jar out there so that people can conveniently download the framework and start playing with it and provide some feedback.
Yep. Let's focus on reviewing your code. After the review is done, we could move your code to /trunk/aioj or /trunk/<another neat name>. You are the initial author of the project, so you could name it as you want as long as it is not offensive. :) As far as a formal release of AIOJ, I would love to see it in MINA
2.0-M1. We'll need to figure out the logistics of this because when there's JNI code involved the build/release process gets much more complicated because we have to build and release for each platform. We may want to make POSIX AIO and Linux libaio support (the parts that require JNI) separate releases.
Yep. Let's include it in 2.0-M1. I also would like to provide MINA transport for it, rather than just providing AIOJ as a sole subproject. I agree with you for the JNI issues. We could probably provide two providers (the current one and the JNI one) and use Ant or make for the JNI one. WDYT? Until MINA 2.0-M1 is ready for release, is it appropriate to make
builds available as progress is made without conducting a formal release? I would like to get feedback earlier rather than later. And make a .jar available for download makes it easier for people to play with the framework. Refactoring JNI code is anything but pleasant so the sooner the API stabilizes the better. Please let me know the proper process for infant projects like this as I've never done anything like this at Apache before and the more I understand about the Apache process, the better off I'll be.
Uploading the nightly build or snapshot to your home directory at people.apache.org sounds fine for me. I saw people at jakarta project do the same for reviewing purpose. It's OK as long as you state that it's not an official release and retain '-SNAPSHOT' suffix to the distribution. Sombody please correct me if I am saying something wrong. Cheers, Trustin -- what we call human nature is actually human habit -- http://gleamynode.net/ -- PGP key fingerprints: * E167 E6AF E73A CBCE EE41 4A29 544D DE48 FE95 4E7E * B693 628E 6047 4F8F CFA4 455E 1C62 A7DC 0255 ECA6
