use maintenance versions (6.6.1, 6.6.2) for critical patches

From NWChem

Viewed 611 times, With a total of 1 Posts
Jump to: navigation, search

Clicked A Few Times
Threads 6
Posts 21
The current 6.6. version lists 17 patches to be applied by users to fix various major issues.
6.5. also has 17 distinct patches to be applied. It is not undoable, but certainly not the ideal way.
I think this could be improved by introducing maintenance versions (i.e. 6.6.1).
I understand that NWChem uses SVN, yet i think one could apply a similar developing model to Gitflow Workflow http://nvie.com/posts/a-successful-git-branching-model/ .

One could probably do it the following way with SVN:

-->patch1 -> patch2 -> patch3 (6.6) -> patch4 -> patch5 -> patch6 (critical bug) -> patch7 ->...
                           \
                            \
                              --> patch6 (6.6.1)


i.e. keep track of [major.minor] revision branch with critical fixes applied without the whole development going on in master.

Also see these Stackoverflow questions for a suggestion on how to do it with SVN: http://stackoverflow.com/a/11558770
http://stackoverflow.com/questions/4904508/how-to-setup-svn-repo-for-emergency-fixes

Regards,
Denis.
Edited On 3:02:21 PM PDT - Wed, Aug 24th 2016 by Den59

Forum Vet
Threads 7
Posts 1355
Thanks for the feedback


Forum >> NWChem's corner >> Feedback



Who's here now Members 0 Guests 0 Bots/Crawler 1


AWC's: 2.5.10 MediaWiki - Stand Alone Forum Extension
Forum theme style by: AWC