search

mfrasca / bauble.classic

desktop version of Bauble
http://bauble.readthedocs.io
GNU General Public License v2.0
2 stars 1 forks source link

split development in 1.0 == master, 1.2, 2.0 branches #62

Closed mfrasca closed 9 years ago

mfrasca commented 9 years ago

I think I should start splitting development into branches, each corresponding to its database model. I'm about to alter the database model and I would not want to drop support for the 1.0 line, which is what would happen if I just altered the database model and kept the single 'master' branch. as of now, I have identified three different possible database models: 1.0) the current one, with maintenance.. 1.2) most requests by JBQ, except the taxonomic revolution. 2.0) the taxonomic revolution.

mfrasca commented 9 years ago

I've already implemented this workflow. you checkout the branch you want, I pull changes to the branch when ready for publication. branch bauble-1.0 is already there. when done with it, will start working at branch bauble-1.1, and so on.