Why master not up to date

[barbazul]

Last commit to the master branch was 2 years ago.

What is the recommended stable branch to use? Is it still master?

@IvanChepurnyi You could probably add some instructions regarding stability in the readme file or I could do it and make a PR if you provide the necessary information.

[barbazul]

One year later. Same question

[barbazul]

Follow up on this.

Switched to dev branch on some installations and it doesn't look all that stable. There are a bunch of weird warnings after all tests and regarding session writing that do not happen on the master branch.

However, all tests (a testsuite of 250+ tests) are working as expected, so I guess the switch is overall safe.

Travis reports that dev branch does not build, but seems to be related to the build script and not any health checks (such as tests).

We also found a bug (I made a separate report on it #284) but it was already present in master branch.

So.... I guess the right way to go in all cases is to use the dev branch as it is stable-ish ?

[IvanChepurnyi]

You are free to submit a pull request to fix build scripts, I don't maintain this extension anymore in favor of pure unit tests writing and acceptance tests using Behat/Codeception.

[barbazul]

I'll give it a try then. But does this mean that the project is abandoned?

[barbazul]

AFAIK this pull request should fix the issue with the failed downloads

EcomDev/MageCI#15

[barbazul]

I can say I successfully ran the whole travis file (by hand) with the changed mage-ci script and it finished successfully (running and passing tests and all).

[barbazul]

@IvanChepurnyi