-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On Wed, Aug 28, 2019 at 01:59:01PM +0800, wd wrote:
> >
> > As a concrete example, consider a moment in time halfway between the
> > release of Django 5.1 and 5.2. At this point in time:
> >
> >- Features will be added to development master, to
>
> As a concrete example, consider a moment in time halfway between the
> release of Django 5.1 and 5.2. At this point in time:
>
>- Features will be added to development master, to be released as
>Django 5.2.
>- Critical bug fixes will be applied to the stable/5.1.x branch, and
>
Oh yes there it is explained in depth
https://docs.djangoproject.com/en/dev/internals/release-process/#supported-versions
ke 28. elok. 2019 klo 8.12 Jani Tiainen kirjoitti:
> It's not weird at all. Django has 8 month release cycle. Usually only bugs
> that are security issues or causes data
It's not weird at all. Django has 8 month release cycle. Usually only bugs
that are security issues or causes data loss are backported to older
releases.
I think this procedure is documented somewhere...
ke 28. elok. 2019 klo 8.06 wd kirjoitti:
> It's so weird, the code is already in master 7
It's so weird, the code is already in master 7 months, but still not
released yet?
On Wed, Aug 28, 2019 at 6:09 AM John MacLaughlin <
john.maclaugh...@carbonlighthouse.com> wrote:
> I see this ticket was addressed, fixed, and merged. However, it's not in
> the latest release (2.2.4)
>
> Ticket:
I see this ticket was addressed, fixed, and merged. However, it's not in
the latest release (2.2.4)
Ticket: https://code.djangoproject.com/ticket/29393
PR: https://github.com/django/django/pull/10730
How can I find out when this fix will be released?
--
You received this message because you
6 matches
Mail list logo
