On Wed, Apr 16, 2008 at 12:36 PM, Noel J. Bergman <[EMAIL PROTECTED]> wrote: > Hontvari Jozsef wrote: > > > The trunk receives all changes. It must always be in a useable state. > > Trying convincing people of that. :-) Robert, for example, explicitly > considers that to be the wrong approach, and indicates that he considers a > substantial amount of trunk to be junk. His thought is to let everyone keep > dumping code into trunk until it is so bad that we are forced to make more > and more modular packaging.
that's overstating my position (other than code i wrote or reviewed myself) i don't consider that trunk has a substantial amount of junk: just that trunk has a substantial quantity of interesting code whose production qualities are unknown. i want people to be able to try interesting and experimental ideas out on trunk without arguing. there needs to be space where we can all collaborate on innovative ideas without endangering the mature JAMES server. > I agree with the goal of modular releases, but want something that we can > work with today. So he and I agree that I'll start with something that we > know works. And as each modular piece comes out of trunk, we'll see if we > can fit it into the production branch. Slowly but surely we'll get to where > we want to be, but always try to maintain a production-ready branch, which > is what you are calling trunk. it's much easier to extract code from trunk, review then release in a modular fashion than to freeze and review trunk. anyone who really needs the feature can download and install. everyone else can wait until it's stable. > > Compatibility doesn't matter at all, you don't release more then once a > > year anyway now. > > That's a bug, not a feature. And if I don't do this, it will be another two > years before anything happens. +1 this is consensus (it's just about the only thing everyone agrees on) and i expect at least one component release a month for the next year - robert --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
