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
