Re: [Vimprobable-users] Features for next version
Vimprobable is a lean web browser optimised for full keyboard control
Brought to you by:
hanness
From: Daniel C. <dan...@gm...> - 2011-08-15 11:21:22
|
Hi! > On a related note, there is the question of version numbering. Should > we have: > - Vimprobable1 1.0 and Vimprobable2 1.0 or > - Vimprobable 1.0 and Vimprobable 2.0? In my opinion vimprobable1 and vimprobable2 are two different things and not only different version of the same programm. I think vimprobable1 should be in a seperate branch with seperate version numbers. Users that like the vimprobable1 can checkout this branch and can fetch bugfixes for it and, maybe, some new fetaures. Vimprobable2/master could be the other branch and have it's own versionnumbering. For the features, it could be useful to have fetature branches (could be prefixed with feature/*), that exists until the feature is merged into the master/vimprobable1. After merging we could remove the featurebranches, to ceep the repository clean. Like mentiones in a pervious post, I would prefer to put all features into the master branch and allo them to be enabled/disabled via precompiler options. For the features the complexity with the switchable features should acceptable. I think, to have only a basic vimprobable2 and several feature branches could make it difficould for users to merge the wished browser together. For every bugfix in featurebranch the user have to merge the sources together. Sometimes merging is hard enought for developers that knew the code well, but for a user who want to build the browser it would be harder. Daniel |