We have to do create a new repository (or branch) every time we switch a version to maintenance mode. Otherwise we couldn't do real corrective maintenance. It allows to start working on the next version and do major changes without hesitation and without the necessity of merging the new development branch with the stable branch because that would represent too much work. And that is the only way I know to keep maintaining a version while working on a new one and releasing on both branches.
-Pierre Le 20 janv. 2012 à 20:07, Steve <[email protected]> a écrit : > Why are multiple repos being used? This seems detrimental to long > term maintenance and version tracking. Can we avoid this practice in > the future? > > On Jan 20, 9:19 am, Steve <[email protected]> wrote: >> Yeah, I found the tag in V20... Is that a subrepo or what? >> >> On Jan 19, 4:31 pm, anatoly techtonik <[email protected]> wrote: >> >> >> >> >> >> >> >>> This is correct venue, but tracing the exact Mercurial revision is a >>> challenge. If you can tell the revision (I guess the start is version 2.0.8 >>> athttp://code.google.com/p/spyderlib/source/list?name=v2.1.0&r=e7288521...) >>> then there is no problem in creating it. I suspect that 'hg bisect' and >>> 'diff' can somehow help here. >> >>> But it also may happen that these releases were made to fix some bugs in a >>> separate branch, which was never merged back to trunk/ > > -- > You received this message because you are subscribed to the Google Groups > "spyder" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/spyderlib?hl=en. > -- You received this message because you are subscribed to the Google Groups "spyder" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/spyderlib?hl=en.
