Robert Collins wrote:
> Yes I do - here's my reasoning...
> I've found while working on the auth_rewrite stuff, that large scale
> changes have a tendency to break dependant modules temporarily. I.E.
> adding in a require module function. Personally, while I'm testing a new
> idea out, I don't want to be breaking everything in sight until it's
> stabilised - even if that's only a few hours work.
This I fully agree on. However, once that testing is done the changes
should be merged up to the base branch, and in the case of modules to a
new framework the module might just as well get merged up to ease
maintenance.
New experimental developments/bugfixes might of course still be
performed on the sub-branch even after the merging.
This probably also applies to the auth_rewrite / ntlm /digest branches,
unless there are changes to the framework which you are not yet sure
about.
Having many separate branches containing tested code which do belong
together the maintenance cost of the branches increases, and it gets a
bit hard to test the things together as one unit.
/Henrik
Received on Fri Jan 05 2001 - 00:01:19 MST
This archive was generated by hypermail pre-2.1.9 : Tue Dec 09 2003 - 16:13:10 MST