[Clam-devel] Branches again?
parumi at iua.upf.edu
Fri Apr 13 08:44:45 PDT 2007
but xavi, last two years we proved how we can make huge changes to the
framework in a controlled way and small steps --executing automatic
tests in every commit was key here.
i think there is a misunderstanding here. i'll try say my point in other
i'm not asking that each change needs a patch to be discussed
(commiters/core developers already share the global architecture and a
set of practices)
i was saying that if anyone have a bunch of local changes with
integration issues, is better to discuss how to integrate it the sooner
the better. commit is not an option since it would make break many
things. but using branches will only increase that delta, so let's only
use them as the last resort.
on a side note, i'm for giving commit access to new developers after a
time of experience with both the clam design and development methodology
please let's stop this unproductive discussions and as someone said:
"show me da code". yeah!
En/na Xavier Amatriain ha escrit:
> When you are refactoring the Spectrum class there is no way you can
> avoid having "a bunch of local changes".
> I see your point in the proposed working method based on patch but I
> think you are forgetting that CLAM is a
> framework, not a single app. If I am working in my particular app, which
> uses and may extend the framework
> (be it a real-time gender change, a plugin, or neural networks), having
> to work over a long discussion every time
> I do a small increment is not very functional.
> That's when I see branches being useful.
> Pau Arumí wrote:
>> Just a small follow up:
>> En/na Xavier Amatriain ha escrit:
>>> now that we are all much more educated it wouldn't hurt (at least not
>>> as much as me having my local sanbox with
>>> a bunch of code I can't commit anywhere :)
>> But why keeping a bunch of local changes? If you see integration
>> issues, don't commit them, send a patch to discuss it first.
>> But please let's put high priority (and i commit to it) on keeping all
>> sandboxes in sync with svn. and of course, don't wait to have "a lot"
>> of changes to do this...
>> Clam-devel mailing list
>> Clam-devel at llistes.projectes.lafarga.org
> Clam-devel mailing list
> Clam-devel at llistes.projectes.lafarga.org
More information about the clam-devel