[Ns-developers] Request to commit -fvisbility=hidden pythonbindings patch

[craigdo@ee.washington.edu]

> I don't have lots of experience with this kind of issues, so 
> maybe there
> is something I'm missing... Why don't you use a separate branch when
> this kind of merge happens? I.e. having a merge branch where you
> selectively apply and test each new feature separately?

We are merging private branches into the main development branch, which then
becomes a release candidate, which then becomes a release.  It is the main
development branch we want to make sure works.  It's hard to test a moving
target, so during the time when lots of things are being merged into
ns-3-dev, it is useful to have some controls in place regarding who is doing
what.

Now, you could take a snapshot of the development branch and call it a
pre-release branch, but then you run into coherency problems, with bug fixes
applied to one branch and not the other, or bug fixes in one branch
depending on other things not applied to the other.  It's up to the release
manager how he wants to deal with this.  I chose to have one real working
branch named ns-3-dev.

-- Craig