Now that master is cross-compatible, the py2 and 3 branches can probably go away

[clbarnes]

Just to cut down on confusion

When the BCT moves to github, we could do a stable and dev branch as they will probably have. We can probably set up the CI so that a test fails if BCT has been updated since bctpy was updated last, although that might get annoying.

[leotrs]

The original BCT is moving to Github?

[clbarnes]

I discussed it with @mikarubi and it seemed like there were a lot of advantages, so there's an 'unofficial' repo under his account which may become the master version pending acceptance by the other maintainers.

[leotrs]

I don't think the proposed CI scheme won't be that annoying. BCT doesn't look to be updated that regularly anyway.

[mikarubi]

I think we might maintain BCT in its current form alongside github which will have faster updates. Mika

On 12 August 2016 at 09:17, Leo Torres [email protected] wrote:

I don't think the proposed CI scheme won't be that annoying. BCT doesn't look to be updated that regularly anyway.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/aestrivex/bctpy/issues/42#issuecomment-239443415, or mute the thread https://github.com/notifications/unsubscribe-auth/AJo0sFBHiAQZ-mqI2YF0yhIGYXdVBxPPks5qfHJrgaJpZM4IaiFZ .