[Chandler-dev] Build Policies meeting

[Alec Flett]

Philippe Bossut wrote:
> We basically have 3 competing proposals: (note I'm talking only about 
> the internal and external projects here, not chandler)
>    1- Use a dev branch (Bear / Heikki) : lib build is built from a dev 
> branch, branch is merged to trunk when lib builds go green, full build 
> from this certified trunk
>    2- Tag on the trunk (Philippe) : lib build is built from the trunk, 
> when green it's tagged, full build from the tagged version
>    3- Use build branch (Andi) : lib build is built from the trunk, 
> this is merged to a clean build branch when green, full build from the 
> build branch
>
I wasn't sure which one of these meant "spin wxPython off into a 3rd 
party product much like PyICU/PyLucene/etc" - I'm guessing this is #3? 
That would be my vote.

I think the rest of the 3rd party libraries have demonstrated good 
practices in terms of working on changes in isolation, and then rolling 
them into the 'chandler' trunk via tarball. We don't have much of this 
confusion with PyLucene/etc - Andi maintains those libraries and if he 
breaks them they don't break the main chandler trunk until the tarball 
rolls.

Further, I think this would allow David to work on changes that might, 
for instance, break Linux for a day so he can land a patch, but then he 
can fix Linux on his own without the rest of the Python developers 
asking "wait, so like, can I check in, or what?"

That also allows wxPython to have its own set of special branches when 
necessary....

Alec

Alec