Thanks Graham - I guess it mostly involves working with a virtualenv for each Django version, as well as using pip in each of those to install Mezzanine directly from Github or BitBucket. There's probably a ton of info online that better describes how to do that.
With that in place, next step is to create a project in each, run them, do things to them. Wild things. Try and break it. Use your existing projects. Use all the features from an end use perspective. Make custom content types, the works. I really can't be too prescriptive here, all I'd do is repeat my own process which would be redundant. Be creative. On Sun, Apr 5, 2015 at 3:02 PM, Graham <greenbay.gra...@gmail.com> wrote: > Hi Stephen > When you say > 'Again, could *really* use help in testing the current dev branch against > Django 1.7 and 1.8' > Is there anything I can look at to know how to do this? > TIA > Graham > > > On 05/04/15 16:59, Stephen McDonald wrote: > > Just a status update on the next release. > > I've just removed all support for South and Django 1.6 and earlier. > Please help me with a review and fixing anything I may have overlooked: > > > https://github.com/stephenmcd/mezzanine/commit/955488361b17959df80ae64e2cb9a2830d7f4540 > > https://github.com/stephenmcd/mezzanine/commit/90912aff8a2858ac4466d8d4677e5be5d9da149f > > I'm currently getting an error with the `createdb` command against 1.8 > (but not 1.7) - if anyone wants to try and work that out it'd be awesome. > > Again, could *really* use help in testing the current dev branch against > Django 1.7 and 1.8 - let's get this next release bullet proof against them! > > Once the above is sorted, I'll release the official new version, > supporting Django 1.7 and 1.8. Perhaps we'll call it Mezzanine 4 rather > than 3.2, it feels large enough to warrant a magical bump in the major > version number. > > > > On Wed, Mar 25, 2015 at 1:47 PM, Stephen McDonald <st...@jupo.org> wrote: > >> Apologies for the delay, I'm currently on vacation overseas with my wife >> and children over the next month. >> >> >> On Tue, Mar 24, 2015 at 10:06 AM, elguavas <elgua...@gmail.com> wrote: >> >>> given that django 1.8 will be released soon, how are things going for a >>> new pip installable release of mezzanine that supports django 1.7? >>> >> >> >> The so-far skipping of an official release against Django 1.7 is a valid >> concern. Basically as Ed mentioned, the breaking changes from Django 1.6 to >> 1.7 were much larger than normal. I vaguely recall that around the time the >> first Django 1.8 alpha release was made, we still had outstanding 1.7 >> incompatibilities, so at that point the question (in my head at least) was >> raised around how worthwhile it would be to spend time on working toward an >> official release against 1.7 given that the 1.8 release would be coming >> soon. The alternative being that we just focus effort on compatibility with >> 1.8, and hopefully everything would line up compatibility-wise in time for >> the official 1.8 release. As of a few weeks ago, we actually have 1.8 >> compatibility working - that may have changed since then, but given that >> sign, it appears that the transition from 1.7 to 1.8 will require much less >> effort. >> >> As Ken said this would normally not be a consideration right now, but >> given how things have turned out, we will most likely release Mezzanine 3.2 >> with support for Django 1.7 and 1.8, along with the new modeltranslation >> work, right after the release of Django 1.8. >> >> >> >>> >>> i'm also very interested in the new fabfile stuff for shared host >>> installs. >>> >>> i'm also wondering, with mezz almost missing a whole django version >>> without a pip installable release, are things on the mezz release front >>> likely to continue to be very slow in staying up to date with changes in >>> mezz git? >>> >>> not intending to be critical, not at all, just looking for an honest >>> assessment of how the project is faring with respect to official releases. >>> cheers. >>> >> >> I don't mean to sound critical either, and I appreciate the desire for >> some clarity here, but I always find this type of question misguided. >> >> There's no corporate entity behind Mezzanine with a fixed schedule of >> time and resources that can be dedicated to it, which is precisely what >> would be required to answer this question definitively. Its development >> relies on the always-varying amount of free time myself and the other >> contributors can make available to it. I simply don't have a crystal ball I >> can peek into to provide you with any more clarity than that. >> >> As mentioned above, the move from Django 1.6 to 1.7 required a >> non-trivial amount of effort, which was a huge setback. Meanwhile the move >> from 1.7 to 1.8 has been almost seamless. So really you could flip a coin >> as to what the future looks like - we're really at the mercy of Django's >> development. >> >> That said, there are a couple of things *you* can do to make our >> timelines less erratic. As often requested, please help out in resolving >> these incompatibilities when new alphas/betas/RCs of Django are made >> available. If enough people were to identify and resolve these issues >> earlier on, sailing would be much smoother. Another idea is that we only >> really see these problems very late into the Django development cycle. What >> we really need is a voice within the Django development space - if someone >> was there early on enough to say "hey this is going to be a huge breaking >> change", perhaps more care for backward compatibility could be taken. I >> hope this doesn't sound like a criticism of Django, they can't know what >> they're breaking if no one tells them. >> >> Thanks for bringing this up - I hope I've been able to make things a >> tiny bit clearer for everyone who has been questioning the lapse in >> releasing. >> >> >> >>> >>> -- >>> 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 mezzanine-users+unsubscr...@googlegroups.com. >>> For more options, visit https://groups.google.com/d/optout. >>> >> >> >> >> -- >> Stephen McDonald >> http://jupo.org >> > > > > -- > Stephen McDonald > http://jupo.org > -- > 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 mezzanine-users+unsubscr...@googlegroups.com. > 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 mezzanine-users+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. > -- Stephen McDonald http://jupo.org -- 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 mezzanine-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
