Re: [Sablevm-developer] On the 1.1.1 release and further

[Chris P. <chr...@ma...>]

Grzegorz B. Prokopski wrote:

> Hi all,
> 
> I wanted to ask you for opinions and suggestions about how and when
> should SableVM 1.1.1 release happend. Below you'll find what I think
> about it, given our last experiences with 1.1.0 and current state of the
> affairs. I also touch some further issues. Even if you (accidentally)
> agree with the below, I'd love to hear it.
> 
> SableVM 1.1.1 release objectives:
> * Fixes of grave bugs since 1.1.0 (like waitfor())
> * Enchancements since 1.1.0
>   - new classpath 0.08 (soon to be released)
>   - David's fillings in the JNI interface
>   - Thread.interrupt() and (if I make it on time) EnsureLocalCapacity()
> * Get more attention as our conficence in 1.1.1 is bigger (announces
>   on sablevm-announce, freshmeat, etc. - should we call it "1.2 beta?")

I think 1.2 beta is too much ... 1.2 will only come when Etienne has 
time to review the code (and I'm guessing May at the earliest).

> SableVM 1.1.1 release path (based on what worked for us before):
> 1. Importing new Classpath release
> 2. Merging new Classpath into staging
> 3. Testing the codebase
> 4. Making and announcing the release
> 
> Last time 1) was done by Etienne, 2) by David, 3) by Chris,  4) by me.
> I think that besides some side issues and bad timing caused by things
> beyond our influence, it worked pretty well, so it'd be great, if this
> time also everyone could put his share in the process.  (I'd be
> particularly interested in helping with 2), but only if I have
> interrupt() and EnsureLocalCapacity() done by that time)

I can do (3) again, but I want to get a paper finished first.  I am 
aiming for the end of March at the moment.  Also, it would be nice at 
some point to merge a few my changes into staging (possibly even all of 
those that are used in the paper?), but I don't mind if this waits until 
after 1.1.1.

Cheers,
Chris