[snapshot] Code unfrozen

[Tim Ellison <t....@gmail.com>]

It would seem that our M1 candidate (r533500) is good enough to be
declared a stable build.  If this were a release we would vote on it
over a few days, but I think for a milestone we can just agree
informally and re-open the code for development.  Do you agree?

Thanks everyone for a smooth chill down, freeze, test and publish
process (good training for our real releases too!); and congratulations
to everyone for producing some very cool code.  M2 here we come<g>

Regards,
Tim

Re: [snapshot] Code unfrozen

[Yang Paulex <pa...@gmail.com>]

2007/4/30, Tim Ellison <t....@gmail.com>:
>
> It would seem that our M1 candidate (r533500) is good enough to be
> declared a stable build.  If this were a release we would vote on it
> over a few days, but I think for a milestone we can just agree
> informally and re-open the code for development.  Do you agree?

The r533500 build looks good to me(supposing we defer the ), I have several
patches in hand, most on beans bug fixing and sql API completion. I think
they are low risk and have little harm to the build. so +1 to unfrozen the
codes.


Thanks everyone for a smooth chill down, freeze, test and publish
> process (good training for our real releases too!); and congratulations
> to everyone for producing some very cool code.  M2 here we come<g>


Here we go! :)

Regards,
> Tim
>



-- 
Paulex Yang
China Software Development laboratory
IBM

Re: [snapshot] Code unfrozen

[Mikhail Fursov <mi...@gmail.com>]

There is nothing critical to be committed in JIT this week, so if the trunk
will be frozen a couple of days more is not an issue for the JIT
subcomponent.
Anyway, I support unfrozing.  Hope to the JavaOne time our trunk will be
even more stable then M1 :)

On 4/30/07, Tim Ellison <t....@gmail.com> wrote:
>
> It would seem that our M1 candidate (r533500) is good enough to be
> declared a stable build.  If this were a release we would vote on it
> over a few days, but I think for a milestone we can just agree
> informally and re-open the code for development.  Do you agree?
>
> Thanks everyone for a smooth chill down, freeze, test and publish
> process (good training for our real releases too!); and congratulations
> to everyone for producing some very cool code.  M2 here we come<g>
>
> Regards,
> Tim
>



-- 
Mikhail Fursov

Re: [snapshot] Code unfrozen

[Mikhail Loenko <ml...@gmail.com>]

2007/4/30, Alexey Petrenko <al...@gmail.com>:
> +1 for unfreeze
>
> Good job, everybody! :)

+1


>
> 2007/4/30, Tim Ellison <t....@gmail.com>:
> > It would seem that our M1 candidate (r533500) is good enough to be
> > declared a stable build.  If this were a release we would vote on it
> > over a few days, but I think for a milestone we can just agree
> > informally and re-open the code for development.  Do you agree?
> >
> > Thanks everyone for a smooth chill down, freeze, test and publish
> > process (good training for our real releases too!); and congratulations
> > to everyone for producing some very cool code.  M2 here we come<g>
> >
> > Regards,
> > Tim
> >
>

Re: [snapshot] Code unfrozen

[Alexey Petrenko <al...@gmail.com>]

+1 for unfreeze

Good job, everybody! :)

2007/4/30, Tim Ellison <t....@gmail.com>:
> It would seem that our M1 candidate (r533500) is good enough to be
> declared a stable build.  If this were a release we would vote on it
> over a few days, but I think for a milestone we can just agree
> informally and re-open the code for development.  Do you agree?
>
> Thanks everyone for a smooth chill down, freeze, test and publish
> process (good training for our real releases too!); and congratulations
> to everyone for producing some very cool code.  M2 here we come<g>
>
> Regards,
> Tim
>