Thank you very much for your response! Best regards, Lauri Hyttinen
On Monday, March 12, 2018 at 11:48:22 PM UTC+2, Stephen McDonald wrote: > > On Mon, Feb 19, 2018 at 10:29 PM, Wim Feijen <w...@go2people.nl > <javascript:>> wrote: > >> Hello, >> >> I was wondering what we can do to help in the release of a new stable >> Mezzanine which supports Django 1.11 LTS or Django 2.0? >> > > Django 1.11 support has been available for the last 10 months, all you > need to do is depend on the latest explicit commit on GitHub. If you'd like > to see 2.0 support, please run the default Mezzanine project against 2.0, > test every documented feature and see if you contribute the necessary fixes > for compatibility. Once that's done and there are no issues, voila - 2.0 > will be supported. > > Unfortunately we work in an environment where stability is of much more >> importance than using a quick leading edge release. >> > > You and your team or whoever else perceives a difference between a PyPI > release and what's on GitHub, unfortunately suffers from an inaccurate > perception. > > Here's the crux of it - if we were pushing commits very frequently to > GitHub, constantly breaking things, as is the case very early on in the > development of a project, then your perception would be accurate. Picking a > commit and depending on it would be a gamble. But the commits to Mezzanine > for several years now have been infrequent and minor. Non-breaking changes, > no new features. The project (and specifically the master branch on GitHub) > is very stable. You can pick the latest commit on GitHub and add it to your > dependencies file and you're now working with the latest version. > > The only significant changes that have occurred over the years have been > updates for compatibility with the latest Django versions. These changes > are generally long-developed in a pull request on GitHub and heavily tested > and refined before being merged into the master branch. Again, the > stability of the master branch is something always striven for. > > If we were to push a build to PyPI right now, there would literally be no > difference between that and specifying an exact commit on GitHub in your > dependencies file, which is something you can do right now. The code would > function exactly the same way. > > I hope this paints a clear picture of where Mezzanine is and how you can > use the most update to date version of it with confidence. To reiterate - > commits to the master branch are *stable and infrequent*. There is no > technical or conceptual difference between a commit on GitHub and PyPI > release. Each commit to GitHub is a new version. Want the latest version? > Update the commit referenced in your dependencies. > > Why don't we just push a release? There's a lot of work involved and the > process needs a lot of improvement. The team has been recently discussing > this off-list. But the idea that the project is dead or isn't a viable > option, considering all the above, is nonsense. The project is mature, > which means development is infrequent and stable, but as active as > necessary. > > > >> We are stuck in a situation where dropping Mezzanine is actually being >> considered as an option. I would rather help the open source project >> Mezzanine forward than drop it. So that's why I feel forced to bump my >> question. Apologies for that. >> >> Best regards, >> >> Wim >> >> >> Op woensdag 10 januari 2018 17:38:07 UTC+1 schreef Wim Feijen: >> >>> Hello, >>> >>> The latest Mezzanine release 4.2.3 support Django up to Django 1.10, >>> which does not receive security updates anymore. See: >>> https://www.djangoproject.com/download/#supported-versions >>> >>> How can we help to release a new version of Mezzanine which support >>> Django 1.11 LTS or Django 2.0? >>> >>> Although I love the high quality of development branches, using a >>> development branch (git version) of Mezzanine is not possible for us, >>> because it is not stable enough. >>> >>> Best regards, >>> >>> Wim >>> >>> -- >> 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-use...@googlegroups.com <javascript:>. >> 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.
