When contributing to apps (dependencies), I've noticed developers tend to expect a stable django release before merging in support and making a new stable release, rather than doing so before the new django release. This happened when I send patched to a few project with dj1.9 support. If the django project provided some clear guidelines in the lines of "we recommend that you make your releases during the feature freeze period", with the explanations given in this thread, it's be easier to convince those app developers to actually accept those patches and create those releases earlier, and start pushing the ecosystem in that direction. The same applies to testing vs master. Compatible [dependency] apps mean it's easier to test earlier too. Just me two cents, Cheers, On Fri, May 20, 2016, at 14:50, Tim Graham wrote: > I'm completely supportive of this effort. In past release cycles, I've > done testing with djangoproject.com and sent some PRs to its > dependencies. The blocker to upgrading is always waiting for each > project to make a release with the fixes. > > We could provide some guidance and suggest that projects should work > on adding support for the next release of Django during the alpha > period and try to make a next-Django-version compatible release by the > beta release date, but of course we can't control how people spend > their time. > > I hoped that enforcing a feature freeze at alpha rather than beta > (starting with the 1.8 release cycle) would make packages more eager > to do prerelease testing since there should be less changes between > then and the final release. I haven't seen evidence that this has > helped though. > > I'd be curious to hear from any third-party package maintainers how > they feel about it. > > On Friday, May 20, 2016 at 9:32:53 AM UTC-4, Claude Paroz wrote: >> Hi, >> >> I have the general feeling that too few people are testing the new >> Django major releases before the .0 release. The result being that >> many regressions are often reported after the release, while those >> could have been detected at alpha/beta/rc stages. >> >> I found myself in the situation where I really wanted to test my own >> projects with a fresh new Django, but couldn't because some >> dependency was not updated and was crashing the project. >> >> I wonder if it would help taking the most popular third-party >> dependencies and help those projects testing with pre-release Django. >> As an example, I added a Wiki page, >> https://code.djangoproject.com/wiki/Version1.10ThirdPartySupport (to >> be completed) as a mean to track Django 1.10 support progress in most >> popular apps. The first step would be to at least add Django 1.10 (or >> even master) as allowed_failures in Travis setups, so as 1.10 support >> is plainly visible. >> >> Thoughts? >> >> Claude > > -- > You received this message because you are subscribed to the Google > Groups "Django developers (Contributions to Django itself)" group. > To unsubscribe from this group and stop receiving emails from it, > send an email to django-developers+unsubscr...@googlegroups.com. > To post to this group, send email to django- > develop...@googlegroups.com. > Visit this group at > https://groups.google.com/group/django-developers. > To view this discussion on the web visit > > https://groups.google.com/d/msgid/django-developers/c33bf5a9-70ca-4bd9-a4c0-13ad1654d69e%40googlegroups.com[1]. > For more options, visit https://groups.google.com/d/optout. -- Hugo Osvaldo Barrera
Links: 1. https://groups.google.com/d/msgid/django-developers/c33bf5a9-70ca-4bd9-a4c0-13ad1654d69e%40googlegroups.com?utm_medium=email&utm_source=footer -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at https://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/1463817921.969445.614418497.0950C42C%40webmail.messagingengine.com. For more options, visit https://groups.google.com/d/optout.
