INADA Naoki songofacandy at gmail.com
Tue Mar 28 08:49:41 EDT 2017

• Previous message (by thread): [Python-Dev] What version is an extension module binary compatible with
• Next message (by thread): [Python-Dev] Misc/NEWS entries for Python 3.7a1
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

---

Hi.

Currently, changelog of Python 3.7a1 [1] contains changes between
3.6b1 and 3.7a1.
So lot's of bugfixes are listed twice or more in changelog.
For example, "bpo-28258: Fixed build with Estonian locale..." are
listed under 3.5.3rc1,
3.6.0b2 and 3.7.0a1.

[1] https://docs.python.org/3.7/whatsnew/changelog.html#changelog

This has two problems:

  * The changelog is longer than necessary.
  * If bpo-xxxx is fixed in 3.7a1, people may think the bug exists in
3.6.0, even if the
    bug is fixed in 3.6b2 too.

Since we stopped merging 3.6 -> master, I suggest to remove such duplicates.
There are two ways:


# A: 3.7a1 -> 3.6.0 -> 3.6.0rc2 ... -> 3.6a1 -> 3.5.0 ...

This may be what people expect.
In this case, we will remove:

* 3.6.1(rc*) from changelog
* duplicated entries in 3.7.0 (which fixed before 3.6.0)


# B: 3.7a1 -> 3.6b1 -> ... 3.6a1 -> 3.5b1 ...

This reflects our branch model.
In this case, we will remove:

* All 3.6 versions after 3.6b1


How do you think?

Regards,

---

• Previous message (by thread): [Python-Dev] What version is an extension module binary compatible with
• Next message (by thread): [Python-Dev] Misc/NEWS entries for Python 3.7a1
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

---

More information about the Python-Dev mailing list