Changes between Version 1 and Version 2 of Version3.2Roadmap


Ignore:
Timestamp:
05/13/2020 08:54:55 AM (3 months ago)
Author:
Adam (Chainz) Johnson
Comment:

s/commit/merge/

Legend:

Unmodified
Added
Removed
Modified
  • Version3.2Roadmap

    v1 v2  
    1111=====================================
    1212
    13 Whatever gets committed by the alpha feature freeze!
     13Whatever gets merged by the alpha feature freeze!
    1414
    15 Django 3.2 will be a time-based release. Any features completed and committed
     15Django 3.2 will be a time-based release. Any features completed and merged
    1616to master by the alpha feature freeze deadline noted below will be included.
    1717Any that miss the deadline won't.
     
    2222shepherd for your feature.
    2323
    24 Minor features and bug fixes will be committed as they are completed. If you
     24Minor features and bug fixes will be merged as they are completed. If you
    2525have submitted a patch, be sure the flags on the Trac ticket are correct such
    2626that it appears in the "Patches needing review" filter of the `Django
    2727Development Dashboard <https://dashboard.djangoproject.com/>`_. Better yet,
    2828find someone to review your patch and mark the ticket as "Ready for checkin".
    29 Tickets marked "Ready for checkin" are regularly reviewed by committers.
     29Tickets marked "Ready for checkin" are regularly reviewed by mergers.
    3030
    3131Schedule
     
    5858------------------------
    5959
    60 All major and minor features must be committed by the Alpha 1 deadline. Any
     60All major and minor features must be merged by the Alpha 1 deadline. Any
    6161features not done by this point will be deferred or dropped. At this time, we
    6262will fork ``stable/3.2.x`` from ``master``.
    6363
    6464After the alpha, non-release blocking bug fixes may be backported at the
    65 committer's discretion.
     65merger's discretion.
    6666
    6767Beta 1
Back to Top