Request Development Outside of Master

[getSurreal]

Request Development Outside of Master

[jonashauge]

From what I understand there is still a few missing features before 1.2 will be release (see issue #52).

From that point there should be a release-1.2 branch which only gets updated with bugfixes and small tested changes. Master will then be cutting edge with the possibility for errors which arrises during development. Then Miha should be decide at a point to do a release-1.3 (or 2.0) with a subset of new features and so on...

For now I would say we should focus on adding the last features for 1.2 and help each other with QA test of the master branch.

[getSurreal]

Release branches are great, but anyone wondering into the github project would most likely download the master branch since it's the default. To ensure a good user experience you'd need to change the default branch to be that release branch for every new release. A reliable master would still be a good thing in my opinion.

Anyway, it looks like you guys have a plan. Just my two cents.

[jonashauge]

You have a point regarding the default when accessing the github page. I admit that I'm very new to github but I can see that you can alter the default branch for the repository. I don't know if this has consequences but my thought would be to alter the default to release-1.2 and keep master as bleeding edge.

[getSurreal]

A look at some Git best practices shows master should be the latest stable release.

[phpipam]

Agreed, after 1.2 release master will be last stable release.