branch structure conforming to orientdb

[luigidellaquila]

OrientDB main repo has a branch structure like following:

• master: last stable release
• 2.0.x: hotfix branch for release 2.0
• 2.1.x: hotfix branch for release 2.1 ...
• develop: branch for next (major or minor) release

plus, final releases are tagged with "2.1.0", "2.1.1" etc.

It would be good to have the same branch structure here, to make dependencies clearer.

[Ostico]

HI @luigidellaquila ,
i think that this kind of structure is not easy to maintain.
You should decide branches name and mail the developers to keep the version updated when you change some thing on the naming.

By the way on the repo:
https://github.com/mogui/pyorient

you can see releases ( tag ) and branches on which we are working.

Python repository is automatically updated.
https://pypi.python.org/pypi/pyorient

Same thing for the Php driver.
https://github.com/Ostico/PhpOrient

The codebases on the forked repositories by Orient Technologies are updated together with the parent one but they have not Tags nor releases. The master branch, as i wrote, is every time updated to the LATEST STABLE VERSION of the driver.