You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@roller.apache.org by David M Johnson <Da...@Sun.COM> on 2006/01/19 14:50:20 UTC
Roller 2.1 release plans
Allen and I are planning to deploy Roller 2.1 to production sites
next week, so we're going into code freeze mode today. At the same
time, I'd like to try to get an "Apache Roller (incubating)" release
out.
I propose this plan:
1 - Write a what's new in Roller 2.1 page for the wiki
2 - Create Roller 2.1 release candidate (today or tomorrow)
3 - Testing through Thursday of next week
4 - Fix or defer remaining issues here: http://tinyurl.com/d3cwa
5 - Call for release vote late next week
6 - Profit!
I'll do 1, 2 and 5. I need help with 3 and 4.
Am I leaving anything out?
- Dave
Re: Roller 2.1 release plans
Posted by Elias Torres <el...@torrez.us>.
On 1/19/06, David M Johnson <Da...@sun.com> wrote:
>
> On Jan 19, 2006, at 11:32 AM, Henri Yandell wrote:
> > On 1/19/06, David M Johnson <Da...@sun.com> wrote:
> >> 1 - Write a what's new in Roller 2.1 page for the wiki
> >> 2 - Create Roller 2.1 release candidate (today or tomorrow)
> >> 3 - Testing through Thursday of next week
> >> 4 - Fix or defer remaining issues here: http://tinyurl.com/d3cwa
> >
> > Why not doing this before hand 1?
> >
> > ie) Why are we preparing to release 2.1 when it's only 60% complete?
> > Are the other 40% less essential for Sun Roller? Do those priorities
> > fit with other users (Elias/Matt)?
>
> Good point.
>
> I'm counting on the facts that 1) most of those issues are actually
> fixed but have not been marked RESOLVED in JIRA and 2) folks will
> happily defer the other issues.
>
> I believe Elias just wants us to finish 2.1 so he can commit his tag
> work.
Exactly my thoughts. I'm waiting for a go so I can start hacking the
trunk. :-) You guys have been doing this for a while, I don't want to
slow you down. I'm (we, IBM) only here to help.
>
> I could be wrong (it happens all the time), so speak up good peoples.
>
>
> >> 6 - Profit!
> >
> > 7 - IRS inspection of non-profit organization suddenly making profits.
>
> Oops. I meant profit in the purely metaphysical sense.
>
> - Dave
>
>
>
>
Re: Roller 2.1 release plans
Posted by David M Johnson <Da...@Sun.COM>.
On Jan 19, 2006, at 11:32 AM, Henri Yandell wrote:
> On 1/19/06, David M Johnson <Da...@sun.com> wrote:
>> 1 - Write a what's new in Roller 2.1 page for the wiki
>> 2 - Create Roller 2.1 release candidate (today or tomorrow)
>> 3 - Testing through Thursday of next week
>> 4 - Fix or defer remaining issues here: http://tinyurl.com/d3cwa
>
> Why not doing this before hand 1?
>
> ie) Why are we preparing to release 2.1 when it's only 60% complete?
> Are the other 40% less essential for Sun Roller? Do those priorities
> fit with other users (Elias/Matt)?
Good point.
I'm counting on the facts that 1) most of those issues are actually
fixed but have not been marked RESOLVED in JIRA and 2) folks will
happily defer the other issues.
I believe Elias just wants us to finish 2.1 so he can commit his tag
work.
I could be wrong (it happens all the time), so speak up good peoples.
>> 6 - Profit!
>
> 7 - IRS inspection of non-profit organization suddenly making profits.
Oops. I meant profit in the purely metaphysical sense.
- Dave
Re: Roller 2.1 release plans
Posted by Henri Yandell <fl...@gmail.com>.
On 1/19/06, David M Johnson <Da...@sun.com> wrote:
> Allen and I are planning to deploy Roller 2.1 to production sites
> next week, so we're going into code freeze mode today. At the same
> time, I'd like to try to get an "Apache Roller (incubating)" release
> out.
>
> I propose this plan:
>
> 1 - Write a what's new in Roller 2.1 page for the wiki
> 2 - Create Roller 2.1 release candidate (today or tomorrow)
> 3 - Testing through Thursday of next week
> 4 - Fix or defer remaining issues here: http://tinyurl.com/d3cwa
Why not doing this before hand 1?
ie) Why are we preparing to release 2.1 when it's only 60% complete?
Are the other 40% less essential for Sun Roller? Do those priorities
fit with other users (Elias/Matt)?
> 5 - Call for release vote late next week
5.5 - notify pmc@incubator
> 6 - Profit!
7 - IRS inspection of non-profit organization suddenly making profits.
> I'll do 1, 2 and 5. I need help with 3 and 4.
Thanks for volunteering :) +1 from me.
I'm definitely available to test a postgres update + install.
Hopefully a derby one too on the version I setup on my laptop.
Hen
Re: Roller 2.1 release plans
Posted by David M Johnson <Da...@Sun.COM>.
On Jan 19, 2006, at 12:19 PM, Allen Gilliland wrote:
> On Thu, 2006-01-19 at 05:50, David M Johnson wrote:
>> I propose this plan:
>> 1 - Write a what's new in Roller 2.1 page for the wiki
>> 2 - Create Roller 2.1 release candidate (today or tomorrow)
>> 3 - Testing through Thursday of next week
>> 4 - Fix or defer remaining issues here: http://tinyurl.com/d3cwa
>> 5 - Call for release vote late next week
>
> I want to make sure I understand the timing properly. Do you want
> to release Roller 2.1 late next week when we deploy to
> blogs.sun.com? or do you just want to vote then?
I meant call for vote next week not make release next week.
I want to make the release soon after the BSC deployment, but not
multiple weeks later. That's why I'm trying to get the ball rolling now.
> Personally, I would rather wait a week after deploying to
> blogs.sun.com before doing the full Roller 2.1 release to the
> community. I just think it's such a great way to get some real
> world testing on the release and usually if there are show stopping
> bugs we can find them and fix them within that week.
Agreed.
> So I don't mind if we vote on the release late next week, but I
> believe the actual release day should be at the very end of
> January, like the 31st, or possibly the first of February.
Me too.
- Dave
Re: Roller 2.1 release plans
Posted by David M Johnson <Da...@Sun.COM>.
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
Re: Roller 2.1 release plans
Posted by Allen Gilliland <Al...@Sun.COM>.
On Thu, 2006-01-19 at 17:25, Henri Yandell wrote:
> >
> > That sounds about right except that we won't actually deploy the RC1
> > build since we have our own build which is created from trunk at
> > (effectively) the same time as the RC1 build.
>
> How do you handle the cvs/svn of it all? Asking from personal interest
> rather than anything Apache related.
>
> Do you have a Roller trunk and then a separate directory that you
> merge in for the build? I'm assuming the custom bits have to be there
> at build time, rather than being overlaid on an existing build.
We just replace the "custom" directory in the standard build with our own version. So the steps are ...
* svn co $roller_trunk
* cd $roller_trunk
* rm -r custom
* ln -s $sun_roller_custom custom
* ./build.sh rebuild
This is effectively the same exact thing as what will be the RC1 build. The only difference is that we have to include some of our Sun customizations at build time.
>
> > > Probably obvious that I'm wanting to emphasize that we make sure we
> > > don't tie the Sun deploy in as something special and hidden. Language
> > > can be fickle sometimes, so just being boring and confirming that.
> >
> > I'm not sure what you mean by "something special and hidden"
>
> There's that fickle language - meaning I couldn't find a fitting
> phrase. It's a reply to Allen's:
>
> "Personally, I would rather wait a week after deploying to
> blogs.sun.com before doing the full Roller 2.1 release to the
> community."
>
> I want to make sure that that statement really means:
>
> [modified]: "Personally, I would rather wait a week after releasing
> RC-1 before doing the full Roller 2.1 release to the community. "
Yes. That is exactly what I meant. We like to put the latest RC builds on blogs.sun.com for a week before cutting the final release just as a way to get some real world testing before the final release goes out.
>
> 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.
>
> The 'special' was along much the same lines; that we weren't building
> a pre-RC1 test into the release plan. That it was just an RC-1 - and
> wow what a lot of bug reports.
No, there is no pre-RC test process. Assuming that everyone agrees to "freeze" the 2.1 code base right now then we can consider the current trunk to be RC1 and everyone can test.
-- Allen
>
> I'm sure that's how it'll be anyway; I'm here to be a worrywart.
>
> Hen
Re: Roller 2.1 release plans
Posted by Henri Yandell <fl...@gmail.com>.
On 1/19/06, David M Johnson <Da...@sun.com> wrote:
>
> Allen commented just before I hit send and I agree with what he said.
>
> Here are some additional comments.
>
>
> On Jan 19, 2006, at 12:48 PM, Henri Yandell wrote:
> > On 1/19/06, Allen Gilliland <Al...@sun.com> wrote:
> >> Personally, I would rather wait a week after deploying to
> >> blogs.sun.com before doing the full Roller 2.1 release to the
> >> community. I just think it's such a great way to get some real
> >> world testing on the release and usually if there are show
> >> stopping bugs we can find them and fix them within that week.
> >
> > How's the codebase work for Sun? Do you have an internal version with
> > changes, or do you deploy a pure Roller version?
>
> We create our build from Roller trunk plus some custom code tied in
> via the custom/*.xmlf files. We usually deploy to staging servers a
> week before our production deployments.
>
> I believe IBM and Javalobby are also using that custom/*.xmlf
> facility to tie in custom stuff.
>
> > ie: should it be:
> > * Build roller-2.1-rc1 and mention on -dev.
> > * Deploy that to Sun, IBM, JavaLobby, individuals, wherever.
> > * Test, debug, fix.
> > * Release 2.1
>
> That sounds about right except that we won't actually deploy the RC1
> build since we have our own build which is created from trunk at
> (effectively) the same time as the RC1 build.
How do you handle the cvs/svn of it all? Asking from personal interest
rather than anything Apache related.
Do you have a Roller trunk and then a separate directory that you
merge in for the build? I'm assuming the custom bits have to be there
at build time, rather than being overlaid on an existing build.
> > Probably obvious that I'm wanting to emphasize that we make sure we
> > don't tie the Sun deploy in as something special and hidden. Language
> > can be fickle sometimes, so just being boring and confirming that.
>
> I'm not sure what you mean by "something special and hidden"
There's that fickle language - meaning I couldn't find a fitting
phrase. It's a reply to Allen's:
"Personally, I would rather wait a week after deploying to
blogs.sun.com before doing the full Roller 2.1 release to the
community."
I want to make sure that that statement really means:
[modified]: "Personally, I would rather wait a week after releasing
RC-1 before doing the full Roller 2.1 release to the community. "
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'.
The 'special' was along much the same lines; that we weren't building
a pre-RC1 test into the release plan. That it was just an RC-1 - and
wow what a lot of bug reports.
I'm sure that's how it'll be anyway; I'm here to be a worrywart.
Hen
Re: Roller 2.1 release plans
Posted by David M Johnson <Da...@Sun.COM>.
Allen commented just before I hit send and I agree with what he said.
Here are some additional comments.
On Jan 19, 2006, at 12:48 PM, Henri Yandell wrote:
> On 1/19/06, Allen Gilliland <Al...@sun.com> wrote:
>> Personally, I would rather wait a week after deploying to
>> blogs.sun.com before doing the full Roller 2.1 release to the
>> community. I just think it's such a great way to get some real
>> world testing on the release and usually if there are show
>> stopping bugs we can find them and fix them within that week.
>
> How's the codebase work for Sun? Do you have an internal version with
> changes, or do you deploy a pure Roller version?
We create our build from Roller trunk plus some custom code tied in
via the custom/*.xmlf files. We usually deploy to staging servers a
week before our production deployments.
I believe IBM and Javalobby are also using that custom/*.xmlf
facility to tie in custom stuff.
> ie: should it be:
> * Build roller-2.1-rc1 and mention on -dev.
> * Deploy that to Sun, IBM, JavaLobby, individuals, wherever.
> * Test, debug, fix.
> * Release 2.1
That sounds about right except that we won't actually deploy the RC1
build since we have our own build which is created from trunk at
(effectively) the same time as the RC1 build.
> Probably obvious that I'm wanting to emphasize that we make sure we
> don't tie the Sun deploy in as something special and hidden. Language
> can be fickle sometimes, so just being boring and confirming that.
I'm not sure what you mean by "something special and hidden"
- Dave
Re: Roller 2.1 release plans
Posted by Allen Gilliland <Al...@Sun.COM>.
On Thu, 2006-01-19 at 09:48, Henri Yandell wrote:
> On 1/19/06, Allen Gilliland <Al...@sun.com> wrote:
> > On Thu, 2006-01-19 at 05:50, David M Johnson wrote:
> > > Allen and I are planning to deploy Roller 2.1 to production sites
> > > next week, so we're going into code freeze mode today. At the same
> > > time, I'd like to try to get an "Apache Roller (incubating)" release
> > > out.
> > >
> > > I propose this plan:
> > >
> > > 1 - Write a what's new in Roller 2.1 page for the wiki
> > > 2 - Create Roller 2.1 release candidate (today or tomorrow)
> > > 3 - Testing through Thursday of next week
> > > 4 - Fix or defer remaining issues here: http://tinyurl.com/d3cwa
> > > 5 - Call for release vote late next week
> >
> > I want to make sure I understand the timing properly. Do you want to release Roller 2.1 late next week when we deploy to blogs.sun.com? or do you just want to vote then?
> >
> > Personally, I would rather wait a week after deploying to blogs.sun.com before doing the full Roller 2.1 release to the community. I just think it's such a great way to get some real world testing on the release and usually if there are show stopping bugs we can find them and fix them within that week.
>
> How's the codebase work for Sun? Do you have an internal version with
> changes, or do you deploy a pure Roller version?
We try and keep almost everything in the Roller subversion repository, as long as it's something that isn't truly unique to Sun. The only changes to a standard Roller build is some additional jsps and some changes to skin that makes up the front pages.
>
> ie: should it be:
>
> * Build roller-2.1-rc1 and mention on -dev.
> * Deploy that to Sun, IBM, JavaLobby, individuals, wherever.
> * Test, debug, fix.
> * Release 2.1
That is basically the model we have been using for quite a while now, except that we don't ask IBM or JavaLobby to deploy to their sites. I think blogs.sun.com itself provides enough of a test case to be quite sure that the release is stable enough. Plus, I believe that IBM and JavaLobby make more customizations to the build, which isn't quite as good of a test case.
>
> ?
>
> Probably obvious that I'm wanting to emphasize that we make sure we
> don't tie the Sun deploy in as something special and hidden. Language
> can be fickle sometimes, so just being boring and confirming that.
Sure, that makes a lot of sense. Deploying to blogs.sun.com isn't really a necessary step in the release cycle, we just do it because it provides a great test case and helps us find last minute bugs.
-- Allen
>
> Hen
Re: Roller 2.1 release plans
Posted by Henri Yandell <fl...@gmail.com>.
On 1/19/06, Allen Gilliland <Al...@sun.com> wrote:
> On Thu, 2006-01-19 at 05:50, David M Johnson wrote:
> > Allen and I are planning to deploy Roller 2.1 to production sites
> > next week, so we're going into code freeze mode today. At the same
> > time, I'd like to try to get an "Apache Roller (incubating)" release
> > out.
> >
> > I propose this plan:
> >
> > 1 - Write a what's new in Roller 2.1 page for the wiki
> > 2 - Create Roller 2.1 release candidate (today or tomorrow)
> > 3 - Testing through Thursday of next week
> > 4 - Fix or defer remaining issues here: http://tinyurl.com/d3cwa
> > 5 - Call for release vote late next week
>
> I want to make sure I understand the timing properly. Do you want to release Roller 2.1 late next week when we deploy to blogs.sun.com? or do you just want to vote then?
>
> Personally, I would rather wait a week after deploying to blogs.sun.com before doing the full Roller 2.1 release to the community. I just think it's such a great way to get some real world testing on the release and usually if there are show stopping bugs we can find them and fix them within that week.
How's the codebase work for Sun? Do you have an internal version with
changes, or do you deploy a pure Roller version?
ie: should it be:
* Build roller-2.1-rc1 and mention on -dev.
* Deploy that to Sun, IBM, JavaLobby, individuals, wherever.
* Test, debug, fix.
* Release 2.1
?
Probably obvious that I'm wanting to emphasize that we make sure we
don't tie the Sun deploy in as something special and hidden. Language
can be fickle sometimes, so just being boring and confirming that.
Hen
Re: Roller 2.1 release plans
Posted by Allen Gilliland <Al...@Sun.COM>.
On Thu, 2006-01-19 at 05:50, David M Johnson wrote:
> Allen and I are planning to deploy Roller 2.1 to production sites
> next week, so we're going into code freeze mode today. At the same
> time, I'd like to try to get an "Apache Roller (incubating)" release
> out.
>
> I propose this plan:
>
> 1 - Write a what's new in Roller 2.1 page for the wiki
> 2 - Create Roller 2.1 release candidate (today or tomorrow)
> 3 - Testing through Thursday of next week
> 4 - Fix or defer remaining issues here: http://tinyurl.com/d3cwa
> 5 - Call for release vote late next week
I want to make sure I understand the timing properly. Do you want to release Roller 2.1 late next week when we deploy to blogs.sun.com? or do you just want to vote then?
Personally, I would rather wait a week after deploying to blogs.sun.com before doing the full Roller 2.1 release to the community. I just think it's such a great way to get some real world testing on the release and usually if there are show stopping bugs we can find them and fix them within that week.
So I don't mind if we vote on the release late next week, but I believe the actual release day should be at the very end of January, like the 31st, or possibly the first of February.
Everything else looks good to me.
-- Allen
> 6 - Profit!
>
> I'll do 1, 2 and 5. I need help with 3 and 4.
>
> Am I leaving anything out?
>
> - Dave
>
>