On Tue, May 7, 2013 at 2:13 PM, Ryan Ollos <[email protected]> wrote:
> On Tue, May 7, 2013 at 1:50 PM, Branko Čibej <[email protected]> wrote: > >> On 07.05.2013 22:30, [email protected] wrote: >> > Author: brane >> > Date: Tue May 7 20:30:34 2013 >> > New Revision: 1480061 >> > >> > URL: http://svn.apache.org/r1480061 >> > Log: >> > * installer/README.rst: Bring the note about using the >> --system-site-packages >> > option with virtualenv from the 0.5 branch back to trunk. >> >> I happened to notice that the installation instructions on trunk were >> out of date with regard to the latest release. That made my hair stand >> on end. :) >> >> I suggest that the normal process for updating release branches should >> be to make the change on trunk /first/, and then merge it onto the >> relevant release branch. If we do it this way, mishaps like this one >> cannot happen; and it's even more important to do this for bug fixes >> than documentation fixes. >> > > Thank you for fixing that. I completely agree that changes should be made > on the trunk and then merged into the release branch. That is the process I > usually follow, but I must have not have been paying enough attention to > what I was doing in this instance. > > Similarly, the RELEASE_NOTES on the trunk are out of sync with those on the 0.5-stable branch (caused by my committing to the 0.05-stable branch rather than the trunk), an issue which I'll fix now.
