Comments on: Maintenance release uploaded http://www.dbdesc.com/blog/archives/maintenance-release-uploaded document your database! Wed, 27 Apr 2011 16:58:33 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: JAG http://www.dbdesc.com/blog/archives/maintenance-release-uploaded/comment-page-1#comment-75 JAG Thu, 08 Dec 2005 08:34:27 +0000 http://dbdesc.com/blog/?p=18#comment-75 Yes you are right. I created a new branch in version 1.2 but I simply didn't commit those bug fixes to that branch. At least I included the bug in the bug tracking database so it was easy to find and fix. Anyway, the next version is almost ready so... Yes you are right. I created a new branch in version 1.2 but I simply didn’t commit those bug fixes to that branch. At least I included the bug in the bug tracking database so it was easy to find and fix.

Anyway, the next version is almost ready so…

]]> By: Baruch http://www.dbdesc.com/blog/archives/maintenance-release-uploaded/comment-page-1#comment-74 Baruch Wed, 07 Dec 2005 22:47:56 +0000 http://dbdesc.com/blog/?p=18#comment-74 <em>The problem was that I did not even ask to myself those questions. I’ve just fixed and committed the change to my source code repository together with other changes related with the next version of dbdesc that I was working on and I forget about it until today, when someone who was trying dbdesc reported it to me!</em> That's why you use branches in your VCS to maintain updates. You simply must ensure that any update to a released version is done off the branch of that version. So that if you released version 1.0, create a branch for it and when it's time to release 1.1 you know it was done off the 1.0 branch and doesn't contain the shiny features intended for version 2.0. The problem was that I did not even ask to myself those questions. I’ve just fixed and committed the change to my source code repository together with other changes related with the next version of dbdesc that I was working on and I forget about it until today, when someone who was trying dbdesc reported it to me!

That’s why you use branches in your VCS to maintain updates. You simply must ensure that any update to a released version is done off the branch of that version. So that if you released version 1.0, create a branch for it and when it’s time to release 1.1 you know it was done off the 1.0 branch and doesn’t contain the shiny features intended for version 2.0.

]]>