In the https://github.com/moodlehq/moodle-behat-extension.git project we have different tags branches for each major release, for example 1.25.x for Moodle 2.5, this tags are created from different branches, one per moodle major release keeping the master branch according to the moodle master branch (1.26.x for Moodle 2.6dev for example) After releasing XY we should update composer.json to point to a new tag (from https://github.com/moodlehq/moodle-behat-extension.git master branch) according to the moodle development version (1.26.0 for Moodle 2.6dev for example)

Detailed process:

• Before each major release:
  • http://docs.moodle.org/dev/Major_release_process#One_week_before

• After each major release
  • http://docs.moodle.org/dev/Major_release_process#Post_release