On Jan 19, 2006, at 8:36 PM, Allen Gilliland wrote:
On Thu, 2006-01-19 at 17:25, Henri Yandell wrote:
I agree that it's a great way to get some real world testing, but
want
to make sure that the whole community is able to get involved in
doing
their testing at the same time. That was the 'hidden'.
Absolutely. As Dave mentioned, we are considering today the code
freeze day, so what is in the trunk now can be considered Roller
2.1 RC1. Any further commits will only be for bug fixes.
I'll second that. We want to get as much of the community involved in
testing as possible.
Ideally, I'd like to sync up BSC deployments with Roller releases so
that we can all test at the same time/benefit from each other's
testing but that's been a little difficult due to our fast paced
monthly deployment schedule. I don't necessarily want the fast pace
of BSC deployments to dictate the Roller release schedule. Monthly
might be OK, but the important thing to me is to find the right pace
to enable maximum community collaboration.
I'd also like to sync up our development roadmaps. We each have our
own priorities for Roller development, but by sharing we'll be able
to better coordinate and collaborate. We've shared our priorities by
mapping the features we want to contribute to Roller release in JIRA
(see the roadmap here: http://tinyurl.com/cge3u) and I hope others
will do the same.
- Dave
