TeamPass versions / releases. about teampass HOT 3 CLOSED

Well the question is good.

I'm a new comer to Github and just start working with it. I'm actually quite lost because I'm used to CVS.
Nevertheless I now see how to play with branches and merges, so things will become more clear in how I will work.

What I've got in mind is to provide in "master branch", always the latest release to use.
I'm creating also branches in which I implement bugs corrections. Once corrected, the "correction branch" is merged into "master branch".

My versioning rule is the next:
-> 2.X indicates a main release.
-> 2.X.Y indicates a patch release (bug correction) of main release 2.X.

Of course, when someone is indicating me a blocking bug, I will provide a quick correction and implement it in the master. So that users can download it. Of course, it is not mandatory for you to upgrade each time if the bug is not a problem for you (depending on the impact).

You can take a look to the existing branches => https://github.com/nilsteampassnet/TeamPass/branches.

I'm still not fully satisfied of the "trunk" for patches but I will improve that.

Note: in order to know what is your version, just take a look in the footer ;-)

Is it more clear for you?

from teampass.

Yes, thanks very much!

I just needed these words the get some sort of trust level for this project. Some kind of assurance.

Before we take it into production I will do some testing. I am curious if some bugs I found in cPassMan 1.82 where fixed :)

from teampass.

Sorry for not answering before ... my internet was broken at home!

So please don't hesitate to ask if you have some questions.

from teampass.