Norman Maurer wrote:
> > And that's the core issue: aggressive development vs disciplined release
> > management, and it will effect the next major release as much as it did
> > JAMES 2.3. The solution is to properly fork things in SVN at the right
> > times so that the release branch can stabilize while people continue to
> > develop in trunk. And to use a sandbox for more experimental things.
> Like i said sometimes ago.. im using trunk in a production for one
> domain here (my domain) ... And i update the server once the week if
> some stuff was add to trunk. So i think thats more testin then most of
> us did with 2.3.0. Sure i can't use all of the components at the same
> time but i can say for the components i use it works.. I also do some
> testing at the moment with the imap stuff and it seems to work so far..
Right, but you're there and you can watch it. And you don't use everything.
And I'm concerned about people who want to put it into a release that isn't
babysat, and they just want it to be stable for long periods of unattended
time. Those are the people whom I worry for all the time.
> We can't be compatible for ever.. At least if we want to push james
> forward.. I understand why you want to be compatible. But can't you
> understand me point ?
LOL Actually, I'm the one who is willing to make the next major release
less compatible than Stefano at the moment. :-) I'm just talking about 2.x
being compatible with itself; 3.x compatible with itself; etc.
--- Noel
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
