nGrinder git branching policy

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

nGrinder git branching policy

Mavlarn

Hi all,


Now we are developing 3.1 version, and maintaining 3.0 version at the same time. So we need brabching for them. And the branching policy will be as below:

We will work on master for 3.1 version, and create a branch for 3.0 version.

And if only we fix some bug and release, we will merge this into master.



For 3.0 maintaining, according to the importance and difficulty, we will release a patch version in 1~4 days.

Reply | Threaded
Open this post in threaded view
|

Re: nGrinder git branching policy

Mavlarn
Version policy:
In ngrinder, there will be several kinds of  version used:
X.0:
It should be significant upgrade and must follow the full developing process, with phase of alpha, beta. Like 3.0 version.
X.x:
It should be the version of some bug fix and function improvement. To release this version, we should follow the QA test and get QA's verification to release.
X.x.x
It will be some little bug fix, and will be release as soon as possible if only user posted some bugs. For this version, we will release it without QA's verification.