http://www.rasadacrea.comrss feed aggregated news on web services and technologies by RasadaCrea France : Category en_search engine indexingThu, 20 Aug 2026 15:31:28 GMTPyRSS2Gen-1.0.0http://blogs.law.harvard.edu/tech/rsshttps://www.djangoproject.com/weblog/2026/aug/05/django-61-released/The Django team is happy to announce the release of Django 6.1. The release notes offer a harmonious mélange of new features and usability improvements. A few highlights are: Model field fetch modes for configuring on-demand fetching behavior Database-level delete options for ForeignKey.on_delete Dictionary-based email settings You can get Django 6.1 from our downloads page or from the Python Package Index . The PGP key ID used for this release is Jacob Walls: 131403F4D16D8DC7 With the release of Django 6.1, Django 6.0 has reached the end of mainstream support. The final minor bug fix release, 6.0.8 , which was also a security release, was issued yesterday, Aug. 4, 2026. Django 6.0 will receive security and data loss fixes until April 2027. All users are encouraged to upgrade before then to continue receiving fixes for security issues. See the downloads page for a table of supported versions and the future release schedule.Wed, 05 Aug 2026 19:30:00 GMThttps://www.djangoproject.com/weblog/2026/jul/22/django-61-rc-1-released/Django 6.1 release candidate 1 is now available. It represents the final opportunity for you to try out the version that offers a harmonious mélange of new features and usability improvements , before Django 6.1 final is released. The release candidate stage marks the string freeze and the call for translators to submit translations . Provided no major bugs are discovered that can't be solved in the next two weeks, Django 6.1 will be released on or around August 5. Any delays will be communicated on the Django forum . Please use this opportunity to help find and fix bugs (which should be reported to the issue tracker ), you can grab a copy of the release candidate package from our downloads page or on PyPI. The PGP key ID used for this release is Jacob Walls: 131403F4D16D8DC7Wed, 22 Jul 2026 20:00:00 GMThttps://www.djangoproject.com/weblog/2026/jun/25/how-the-django-software-foundation-became-a-cna/Why the DSF pursued CNA status Django has a long history of responsible security practices: a dedicated, private security mailing list, clear advisory policies, and predictable security releases. Even so, we relied on external organizations to assign CVE IDs (Common Vulnerabilities and Exposures) . This sometimes introduced administrative delays and extra coordination overhead. Becoming a CNA (CVE Numbering Authority) allows the DSF to: Assign CVEs ourselves for vulnerabilities in Django and selected community projects. Publish advisories more efficiently and in closer alignment with Django's established release workflow. Maintain strong independence in how Django handles security incidents. The initial exploration The process began with internal discussions within the DSF Board and Django Security Team . We evaluated: Whether our existing security process already met CNA expectations. Whether we had the organizational stability to take on long term responsibility for CVE assignment. The scope of projects we would cover. How to ensure we could meet the operational requirements without overloading volunteers and Django Fellows . After confirming that our policies were mature and that the administrative .. cntdThu, 25 Jun 2026 11:00:00 GMThttps://www.djangoproject.com/weblog/2026/jun/24/django-61-beta-1-released/Django 6.1 beta 1 is now available. It represents the second stage in the 6.1 release cycle and is an opportunity to try out the changes coming in Django 6.1. Django 6.1 offers a harmonious mélange of new features and usability improvements, which you can read about in the in-development 6.1 release notes . Only bugs in new features and regressions from earlier Django versions will be fixed between now and the 6.1 final release. Translations will be updated following the "string freeze", which occurs when the release candidate is issued. The current release schedule calls for a release candidate in about a month, with the final release scheduled roughly two weeks later on August 5. Early and frequent testing from the community will help minimize the number of bugs in the release. Updates on the release schedule are available on the Django forum . As with all alpha and beta packages, this release is not for production use. However, if you'd like to try some of the new features or help find and fix bugs (which should be reported to the issue tracker ), you can grab a copy of the beta package from our downloads page or on PyPI. The PGP key ID used for this release is Jacob Walls: 131403F4D16D8DC7Wed, 24 Jun 2026 17:00:00 GMT