1.3.4 release

[Assaf Arkin]

Looks like we're having a 1.3.3 release later today, I'm already
thinking of 1.3.4.  I would like to roll out the next release quickly,
as in deciding which features will make it within the next few days,
and aiming for end of the month.  For the following reasons:

A few updates came out too late for inclusion in 1.3.3, specifically
Rake 0.8.3, AntUnit 1.1,  RSpec 1.1.8.  Also, I'm going to start
testing against RubyGems 1.3.0.  It would be easier to test 1.3.4 if
the majority of changes are merely upgrades to these dependencies.

BUILDR-172 [1].  My bad for breaking it.

I want someone else to make the next release.  I think it's important
that before graduation we get to the point where any committer can
take charge of making a release.  The release process/scripts are
getting there but not bug-free yet, so it would be good to take one
release to work just on that.

That means the new release won't have a lot of new features, whatever
we have in branches or can quickly get in, but I think it's worth
doing for these three reasons alone.

Assaf


[1] https://issues.apache.org/jira/browse/BUILDR-172

[Alex Boisvert-3]

I'd be happy to be the next release guinea-pig.

alex

On Thu, Oct 16, 2008 at 11:34 AM, Assaf Arkin <arkin@...> wrote:

> Looks like we're having a 1.3.3 release later today, I'm already
> thinking of 1.3.4.  I would like to roll out the next release quickly,
> as in deciding which features will make it within the next few days,
> and aiming for end of the month.  For the following reasons:
>
> A few updates came out too late for inclusion in 1.3.3, specifically
> Rake 0.8.3, AntUnit 1.1,  RSpec 1.1.8.  Also, I'm going to start
> testing against RubyGems 1.3.0.  It would be easier to test 1.3.4 if
> the majority of changes are merely upgrades to these dependencies.
>
> BUILDR-172 [1].  My bad for breaking it.
>
> I want someone else to make the next release.  I think it's important
> that before graduation we get to the point where any committer can
> take charge of making a release.  The release process/scripts are
> getting there but not bug-free yet, so it would be good to take one
> release to work just on that.
>
> That means the new release won't have a lot of new features, whatever
> we have in branches or can quickly get in, but I think it's worth
> doing for these three reasons alone.
>
> Assaf
>
>
> [1] https://issues.apache.org/jira/browse/BUILDR-172
>