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 <[EMAIL PROTECTED]> 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
