It has to do with "Branching", which is a critical part of the software engineering process.
We use a piece of software for storing our source files called "Subversion" or "svn". Subversion (and most source-control software) uses the metaphor of tree branches to describe versions of the project. Up until now, Slimserver 6.5 development has been happening in "trunk" (sometimes called "main"). This has its positives and negatives. On the positive side, it means that changes or bug fixes only need to be made in one place. On the negative side, if there are risky changes that should be added for a release after 6.5, they have to be set aside and cannot be "checked in". This makes life a hassle when these changes have to be reconciled later. However, as you noticed, over the weekend we branched 6.5. Now there is also a version 7.0. Initially, the branch is a perfect copy of the trunk. Moving forward, large changes can be made to the 7.0 branch without affecting the stability of 6.5, which is due to be released in a matter of weeks. This is good. On the downside, fixes will often need to be made to both branches, which grows more difficult as the branches diverge. I hope this explanation is helpful. Please let me know if there are additional questions! -- ChrisOwens Christopher Owens QA Manager [EMAIL PROTECTED] (650) 210-9400 x717 ------------------------------------------------------------------------ ChrisOwens's Profile: http://forums.slimdevices.com/member.php?userid=4240 View this thread: http://forums.slimdevices.com/showthread.php?t=26818 _______________________________________________ beta mailing list beta@lists.slimdevices.com http://lists.slimdevices.com/lists/listinfo/beta
