On 2/2/07, Trustin Lee <[EMAIL PROTECTED]> wrote:
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.
+1
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. :)
+1
<snip>
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.
+1
alternatively, there are more official spaces available (on
people.apache.org) for snapshots and nightly builds. all that's needed
would be a simple vote to approve the snapshot.
- robert
