Hi Scott, the master branch is very stable right now and I think it is very
likely that a release would come out within the next few months.  In
general to upgrade you would:

   - Install the master branch
   - Upgrade django
   - Run migrations

The one caveat is that migrations are now handled directly inside Django,
but previously in Django 1.6 we used South for migrations.  I'm not sure if
that complicated upgrading from 1.6 to 1.8.  Anyone else know?

If you don't have any content you need to save you could just wipe your
database, upgrade Mezzanine and Django and then create a new database.

Good luck!

On Tue, Jun 9, 2015 at 12:03 AM, Scott Daniels <[email protected]>
wrote:

> Hi Josh,
>
> Thanks for the tip on using the github master branch. Do you recommend
> using it over the release version? Since Django will provide the longest
> term support on version 1.8, I would love to use it. Do you know if a
> release version of the main branch is expected anytime in the next few
> months or so?
>
> Also, what would I need to upgrade from the release version to the main
> branch, besides updating Django & Mezzanine? Are there any differences in
> the settings, urls or other files generated by Mezzanine?
>
> Thanks again for the help.
>
> On Monday, June 8, 2015 at 9:51:01 PM UTC-5, Josh Cartmell wrote:
>>
>> Hi Scott, the version on pip should work with Django 1.6.11.
>>
>> You could install the master branch from Github:
>> pip install -e git+
>> https://github.com/stephenmcd/mezzanine.git@master#egg=Mezzanine
>>
>> That is very stable and I believe works with the latest Django.
>>
>> On Thu, Jun 4, 2015 at 2:30 PM, Scott Daniels <[email protected]>
>> wrote:
>>
>>> Okay, I solved the problem. I was building my project via pip
>>> requirements file which specified Django version = 1.6. I rebuilt the
>>> project using vers = 1.5, which Mezzanine replaced somehow with ver=1.6.11.
>>> This build works perfectly, so the problem seems to be an incompatibility
>>> with ver 1.6.
>>>
>>> Still not sure how to specify Django in the requirements.txt file, but
>>> at least it is up and running now.
>>>
>>> --
>>> You received this message because you are subscribed to the Google
>>> Groups "Mezzanine Users" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to [email protected].
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>>  --
> You received this message because you are subscribed to the Google Groups
> "Mezzanine Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [email protected].
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Mezzanine Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to