During the first half of the week I assisted with a couple of final bugs in 
1.8. I also did some other release preparation tasks, like updating the 
djangoproject.com downloads page (which is mostly programatically 
generated) to accommodate two supported LTS versions (otherwise 1.4 would 
have appeared as “unsupported” upon the release of 1.8).

Later in the week I spent some time on other djangoproject.com issues. I 
helped Jannis Leidel rollout Elasticsearch integration for the 
documentation search page and reviewed/merged Michael Trythall’s work to 
switch the website’s SCSS compilation to libsass. The latter allowed us to 
remove the compiled CSS files from the repository and instead compile it on 
the server which should help prevent merge conflicts. I added a new 
“Supported Versions” sections to the download page 
<http://djangoproject.com/download/> to give a better overview of which 
Django versions are supported and for how long.

We’ve already merged 3 bug fixes to be released in 1.8.1. I plan to release 
that version by May 1, perhaps sooner if we accumulate a lot of fixes in 
the meantime.

Report for week ending April 3, 2015:

Triaged

-------

https://code.djangoproject.com/ticket/24565 - server_default option on 
model fields (duplicate)

https://code.djangoproject.com/ticket/24566 -MigrationWriter doesn't 
serialize timedelta (accepted) 

https://code.djangoproject.com/ticket/24567 - /admin/auth/user/add/ 
requires "auth | user | Can change user" (invalid)

https://code.djangoproject.com/ticket/24574 - 'python manage.py runserver' 
sleeps forever because of threading lock (needsinfo)

https://code.djangoproject.com/ticket/24576 - Bad cascading leads to 
non-deterministic IntegrityError (accepted)

https://code.djangoproject.com/ticket/24575 - Add an option to 
smtp.EmailBackend for DKIM signing (won’t fix)

https://code.djangoproject.com/ticket/24578 - prepare_database_save breaks 
some OneToOneField's in 1.8 (accepted)

Authored

--------

https://github.com/django/djangoproject.com/pull/421 - Added support for 
two supported LTS versions to the downloads page.

https://github.com/django/djangoproject.com/pull/424 - Fixed #390 -- Added 
release notes links to download page.

https://github.com/django/djangoproject.com/pull/428 - Added a "Supported 
Versions" table to the downloads page.

https://github.com/django/django/pull/4411 - Fixed sessions test on Python 
3.5.

Reviewed/committed

------------------

https://github.com/django/django/pull/4406 - Fixed #15590 -- Documented how 
the path of a FileField can be changed.

https://github.com/django/django/pull/4409 - Fixed #24556 -- Added reminder 
about HTTPS to passwords docs.

https://github.com/django/django/pull/4105 - Fixed #24301 -- Added 
PostgreSQL-specific aggregate functions

https://github.com/django/django/pull/4424 - Fixed behavior of 
InclusionNode.

https://github.com/django/djangoproject.com/pull/420 - Switched to Libsass 
for CSS compilation.

https://github.com/django/djangoproject.com/pull/303 - Switched search to 
Elasticsearch

https://github.com/django/djangoproject.com/pull/430 - Switched to watchdog 
for recursive CSS watching.

https://github.com/django/djangoproject.com/pull/432 - Ensured icons flip 
when they are in view.

https://github.com/django/djangoproject.com/pull/413 - Gray out unpublished 
blog entry summaries.

Reviews of core dev work

------------------------

https://github.com/django/django/pull/4408 - Fixed #24550 -- Added 
migration operation description to sqlmigrate output

https://github.com/django/django/pull/4444 - Fixed #24571 -- Restored 
testserver positional arguments parsing

https://github.com/django/django/pull/4445 - Fixed #24569 -- Made some 
translation functions accept None value

-- 
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 [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/django-developers.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-developers/305fffaf-1940-4e26-8731-703896dbdfda%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to