You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@bloodhound.apache.org by br...@apache.org on 2013/05/07 22:30:34 UTC
svn commit: r1480061 - /bloodhound/trunk/installer/README.rst
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.
Modified:
bloodhound/trunk/installer/README.rst
Modified: bloodhound/trunk/installer/README.rst
URL: http://svn.apache.org/viewvc/bloodhound/trunk/installer/README.rst?rev=1480061&r1=1480060&r2=1480061&view=diff
==============================================================================
--- bloodhound/trunk/installer/README.rst (original)
+++ bloodhound/trunk/installer/README.rst Tue May 7 20:30:34 2013
@@ -101,13 +101,13 @@ Installation and Initial Configuration
Environment setup is achieved with the following commands on linux::
$ cd bloodhound/installer
- $ virtualenv bloodhound
+ $ virtualenv --system-site-packages bloodhound
$ source ./bloodhound/bin/activate
or on windows::
$ cd bloodhound\installer
- $ virtualenv bloodhound
+ $ virtualenv --system-site-packages bloodhound
$ bloodhound\bin\activate.bat
From now on, all shell commands should be run within the activated virtualenv
Re: svn commit: r1480061 - /bloodhound/trunk/installer/README.rst
Posted by Ryan Ollos <ry...@wandisco.com>.
On Tue, May 7, 2013 at 2:13 PM, Ryan Ollos <ry...@wandisco.com> wrote:
> On Tue, May 7, 2013 at 1:50 PM, Branko Čibej <br...@wandisco.com> wrote:
>
>> On 07.05.2013 22:30, brane@apache.org 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.
Re: svn commit: r1480061 - /bloodhound/trunk/installer/README.rst
Posted by Ryan Ollos <ry...@wandisco.com>.
On Tue, May 7, 2013 at 1:50 PM, Branko Čibej <br...@wandisco.com> wrote:
> On 07.05.2013 22:30, brane@apache.org 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.
Re: svn commit: r1480061 - /bloodhound/trunk/installer/README.rst
Posted by Branko Čibej <br...@wandisco.com>.
On 07.05.2013 22:30, brane@apache.org 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.
Subversion has long followed this process to good effect. The
back-porting procedure is documented here:
http://subversion.apache.org/docs/community-guide/releasing.html#release-stabilization
and I propose all of that page is useful reading for BH developers.
Notice that on the Subversion project, we maintain a STATUS file on each
release branch which contains a list of proposed back-ports, and all
such proposals need approval from several committers. I'm not suggesting
BH should require such a formal approach for now, but it /would/ be a
good idea to track backports somewhere -- if for no other reason than to
make it easier to maintain release notes.
-- Brane
P.S.: Needless to say, for Subversion, we have a daemon running that
periodically looks at the "approved" section of the STATUS file and
automatically merges the backports for us. :)
--
Branko Čibej
Director of Subversion | WANdisco | www.wandisco.com