On Thu, Apr 4, 2013 at 4:53 AM, Branko Čibej <[email protected]> wrote:
> On 04.04.2013 09:56, Ryan Ollos wrote: > > On Wed, Apr 3, 2013 at 5:14 AM, Gary Martin <[email protected] > >wrote: > > > >> On 03/04/13 12:42, Marco Mangiante wrote: > >> > >>> Hello, > >>> > >>> Any way, sate is inconsistent now in installation procedure - bhsearch > >>>> should be mentioned (or not mentioned) in both files requirements.txt > >>>> and bloodhound_setup.py otherwise installation fails always. What can > >>>> we do with this? New release? > >>>> > >>>> Cheers, Andrej > >>>> > >>> in my opinion if it is possible is better a new release: the > installation > >>> guide is now not updated for the 0.5.2 . If not possible, maybe we can > >>> modify the page https://issues.apache.org/**bloodhound/wiki/** > >>> BloodhoundInstall< > https://issues.apache.org/bloodhound/wiki/BloodhoundInstall>to report > these changes (bhsearch manual installation and "virtualenv > >>> --system-site-packages bloodhound" if you install with apt). > >>> > >>> > >>> Marco > >>> > >>> > >> The wiki page is already updated to mention the manual install of search > >> for 0.5.2 and I will look at improving the psycopg installation > discussion > >> in a bit. There is also now https://issues.apache.org/** > >> bloodhound/ticket/493 <https://issues.apache.org/bloodhound/ticket/493>for > the problem with search being required. > >> > >> Cheers, > >> Gary > >> > > It sounds like I should put together a 0.5.3 release this weekend. I'm > > assuming that it will need to be voted on, the same as any other release. > > You assume correctly. But don't release from trunk, just merge the > relevant fixes onto the 0.5.x branch and release from there. This is a > bugfix release, not a feature release. > I've done some testing to reproduce the failures and then committed the suggested fixes. Everything looks good to me now, but I'll wait until morning to push out the release and call for a vote in case someone sees something I might have missed. The biggest failure here is that I as the release manager I didn't test that installation steps could be executed correctly. I had only tested the ability to install a development instance. I'll add some steps to the release process to cover a basic smoke test prior to release. - Ryan
