Re: [Django] #23015: Don't announce Django 2.0 as a backwards-incompatible release

[Django]

#23015: Don't announce Django 2.0 as a backwards-incompatible release
-+-
 Reporter:  aaugustin|Owner:  timo
 Type:  Bug  |   Status:  closed
Component:  Documentation|  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Ready for
Has patch:  1|  checkin
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-

Comment (by Tim Graham ):

 In [changeset:"dcb1b971c254c4c23216b8335ec40abb7d30b288"]:
 {{{
 #!CommitTicketReference repository=""
 revision="dcb1b971c254c4c23216b8335ec40abb7d30b288"
 [1.7.x] Fixed #23015 -- Fixed major/minor release terminology in docs.

 Backport of dd6ef3197a from master
 }}}

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.fcb4446ba1e61f8f4be6587994088827%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23015: Don't announce Django 2.0 as a backwards-incompatible release

[Django]

#23015: Don't announce Django 2.0 as a backwards-incompatible release
-+-
 Reporter:  aaugustin|Owner:  timo
 Type:  Bug  |   Status:  closed
Component:  Documentation|  Version:  master
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Ready for
Has patch:  1|  checkin
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by Tim Graham ):

 * status:  assigned => closed
 * resolution:   => fixed


Comment:

 In [changeset:"dd6ef3197a4d10696c5ef4ddb55b0d4baaba4340"]:
 {{{
 #!CommitTicketReference repository=""
 revision="dd6ef3197a4d10696c5ef4ddb55b0d4baaba4340"
 Fixed #23015 -- Fixed major/minor release terminology in docs.
 }}}

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.7368d48cba617901d21b3bc3309b5cc6%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23015: Don't announce Django 2.0 as a backwards-incompatible release

[Django]

#23015: Don't announce Django 2.0 as a backwards-incompatible release
-+-
 Reporter:  aaugustin|Owner:  timo
 Type:  Bug  |   Status:  assigned
Component:  Documentation|  Version:  master
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Ready for
Has patch:  1|  checkin
  Needs tests:  0|  Needs documentation:  0
Easy pickings:  0|  Patch needs improvement:  0
 |UI/UX:  0
-+-
Changes (by aaugustin):

 * stage:  Accepted => Ready for checkin


Comment:

 Looks good, thank you!

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.858b544cd6a98638e46a4f2fdfa7bafd%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23015: Don't announce Django 2.0 as a backwards-incompatible release

[Django]

#23015: Don't announce Django 2.0 as a backwards-incompatible release
---+
 Reporter:  aaugustin  |Owner:  timo
 Type:  Bug|   Status:  assigned
Component:  Documentation  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+

Comment (by timo):

 Current consensus is that no such changes will occur in the foreseeable
 future. If such changes are needed at some point, then we'll cross that
 bridge when the time comes.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.96c94f1d0544264dd71f143d8b29b12c%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23015: Don't announce Django 2.0 as a backwards-incompatible release

[Django]

#23015: Don't announce Django 2.0 as a backwards-incompatible release
---+
 Reporter:  aaugustin  |Owner:  timo
 Type:  Bug|   Status:  assigned
Component:  Documentation  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+

Comment (by smeatonj):

 I think the idea here is good. But what happens in the future if some
 serious backward-incompatible changes need to land - there would be no way
 to indicate with version numbers that big shift. Or, is the idea that no
 such serious changes will ever occur all at once (similar to now, where
 there's 2 major releases to slowly deprecate functionality)?

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.87c8611a7ea5a9e351bd5cf31ad069eb%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23015: Don't announce Django 2.0 as a backwards-incompatible release

[Django]

#23015: Don't announce Django 2.0 as a backwards-incompatible release
---+
 Reporter:  aaugustin  |Owner:  timo
 Type:  Bug|   Status:  assigned
Component:  Documentation  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  1  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+
Changes (by timo):

 * has_patch:  0 => 1


Comment:

 [https://github.com/django/django/pull/2912 PR]

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.a0c0660690e902d30128ffdc01463c05%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23015: Don't announce Django 2.0 as a backwards-incompatible release

[Django]

#23015: Don't announce Django 2.0 as a backwards-incompatible release
---+
 Reporter:  aaugustin  |Owner:  timo
 Type:  Bug|   Status:  assigned
Component:  Documentation  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Accepted
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+
Changes (by timo):

 * status:  new => assigned
 * owner:  nobody => timo
 * stage:  Unreviewed => Accepted


-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.0bbbea1c85b51a23d8b8777e12f31b9d%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23015: Don't announce Django 2.0 as a backwards-incompatible release

[Django]

#23015: Don't announce Django 2.0 as a backwards-incompatible release
---+--
 Reporter:  aaugustin  |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Documentation  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--

Comment (by aaugustin):

 We should redefine "major release" in docs/internals/release-process.txt.
 Everyone considers Django 1.x, 1.y, etc. major releases.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.820086284d38600bb03e3220bd1141c9%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #23015: Don't announce Django 2.0 as a backwards-incompatible release

[Django]

#23015: Don't announce Django 2.0 as a backwards-incompatible release
---+--
 Reporter:  aaugustin  |Owner:  nobody
 Type:  Bug|   Status:  new
Component:  Documentation  |  Version:  master
 Severity:  Normal |   Resolution:
 Keywords: | Triage Stage:  Unreviewed
Has patch:  0  |  Needs documentation:  0
  Needs tests:  0  |  Patch needs improvement:  0
Easy pickings:  0  |UI/UX:  0
---+--

Comment (by aaugustin):

 Related: docs/internals/howto-release-django.txt and
 docs/releases/1.1.2.txt uses "major release" to refer to what is defined
 by docs/internals/release-process.txt as a "minor release".

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.1489c462f970a78fd6cdb13b1c9b737a%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.