Feature freeze

[Assaf Arkin <ar...@intalio.com>]

Are we ready to do a feature freeze for 1.3?
I just rolled out the last two features that I wanted to have in 1.3,
support for extensions using Gems and YAML configuration files.  Those are
lightly implemented, intentionally, but give us something to build upon in
1.3.x going forward.

If there are no other outstanding features, I would suggest we do the
following:
1.  No new features added in trunk.
2.  Catch up with documentation and test cases.
3.  Fix outstanding bugs, specifically anything broken switching from 1.2.10
to 1.3.
4.  Wait 72 hours from the last bug fix and vote to cut a release.

Assaf

Re: Feature freeze

[Victor Hugo Borja <vi...@gmail.com>]

Assaf Arkin wrote:
> Are we ready to do a feature freeze for 1.3?
I think yes, no major changes from my part.

> If there are no other outstanding features, I would suggest we do the
> following:
> 1.  No new features added in trunk.
> 2.  Catch up with documentation and test cases.
> 3.  Fix outstanding bugs, specifically anything broken switching from 1.2.10
> to 1.3.
> 4.  Wait 72 hours from the last bug fix and vote to cut a release.

Sounds good to me, we need more test cases at this point than new features.

-- 
   vic

Re: Feature freeze

[Alex Boisvert <bo...@intalio.com>]

On Wed, Apr 9, 2008 at 11:13 AM, Assaf Arkin <ar...@intalio.com> wrote:

> Are we ready to do a feature freeze for 1.3?


Ready :)


> I just rolled out the last two features that I wanted to have in 1.3,
> support for extensions using Gems and YAML configuration files.  Those are
> lightly implemented, intentionally, but give us something to build upon in
> 1.3.x going forward.
>
> If there are no other outstanding features, I would suggest we do the
> following:
> 1.  No new features added in trunk.
> 2.  Catch up with documentation and test cases.
> 3.  Fix outstanding bugs, specifically anything broken switching from
> 1.2.10
> to 1.3.
> 4.  Wait 72 hours from the last bug fix and vote to cut a release.


Good plan.

alex

Re: Feature freeze

[Tal Rotbart <re...@gmail.com>]

As a lurker on this list, I'd like to offer my opinion that 1.3 would
be an amazing release!
I believe that the jruby integration in 1.3 will drive adoption far
and wide, so the sooner it is out there, the better ;-)

Thank you guys for all your hard work.
-Tal

On Thu, Apr 10, 2008 at 4:13 AM, Assaf Arkin <ar...@intalio.com> wrote:
> Are we ready to do a feature freeze for 1.3?
>  I just rolled out the last two features that I wanted to have in 1.3,
>  support for extensions using Gems and YAML configuration files.  Those are
>  lightly implemented, intentionally, but give us something to build upon in
>  1.3.x going forward.
>
>  If there are no other outstanding features, I would suggest we do the
>  following:
>  1.  No new features added in trunk.
>  2.  Catch up with documentation and test cases.
>  3.  Fix outstanding bugs, specifically anything broken switching from 1.2.10
>  to 1.3.
>  4.  Wait 72 hours from the last bug fix and vote to cut a release.
>
>  Assaf
>