Update news with updates Dec 2017-present

[brainwane]

https://packaging.python.org/news/ currently stops in November 2017; let's update it.

[pradyunsg]

@brainwane Would this be something for the Sprint?

[theacodes]

This is something for me to do during the sprint. (And something for me to add a build check for.)

…

On Thu, May 10, 2018, 3:37 AM Pradyun Gedam ***@***.***> wrote: @brainwane <https://github.com/brainwane> Would this be something for the Sprint? — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#474 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAPUc9pCtgxeZSNhFBrN9TLYBtL-Yd_hks5tw-4cgaJpZM4TXBkC> .

[theacodes]

This is a great issue for a first-time contributor to take on. Building a check (or using something more complex) would be a task for me.

[pradyunsg]

If you go along the route of combining smaller NEWS fragments, I suggest looking at towncrier. It's working well for pip.

[dwalkerbeta]

I could take this task, if no one else has taken it. Where would be the best place to curate the news from?

[theacodes]

@dwalkerbeta the commit log is probably the best ledger we have.

[dwalkerbeta]

Ok, that's where I've been pulling from. I'll probably have a PR out this weekend for the in-place solution and I'm currently looking into towncrier as a longer-term solution.

[theacodes]

Thank you so much!

…

On Wed, Aug 8, 2018, 2:32 PM David Walker ***@***.***> wrote: Ok, that's where I've been pulling from. I'll probably have a PR out this weekend for the in-place solution and I'm currently looking into towncrier as a longer-term solution. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#474 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAPUc6Un9dy6AKBSoMJPvbUGIFDHvuFAks5uO1j6gaJpZM4TXBkC> .

[dwalkerbeta]

I'm testing out the towncrier solution; I have a few questions. It looks like towncrier names its newsfragment files with issueid.doc or issueid.feature. Would we want to replace those with the PR numbers? Some of the PRs don't have an issue assigned to them.

Also, is there any sort of versioning that has been adopted? Right now the --draft option from towncrier looks like this with the earliest fragment from news.rst:

Finding news fragments...
Rendering news fragments...
Draft only -- nothing has been written.
What is seen below is what would be written.

Python Packaging User Guide 1.0 (2017-02-01)
============================================


Improved Documentation
----------------------

- Added :pep:`518`. (:pr:`281`) (#281)

And I can increment the version per month, or just push all past changes out under 1.0 and you guys increment from there.

Thoughts?

[theacodes]

I think PR is fine.

Release is weird. We should do calver, if anything.

[dwalkerbeta]

How would the calver be formatted? Also I figure I'll remove the duplicated PR in the ().

[theacodes]

2018.11.05 (year.month.day)

…

On Fri, Sep 7, 2018 at 1:11 PM David Walker ***@***.***> wrote: How would the calver be formatted? Also I figure I'll remove the duplicated PR in the (). — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#474 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAPUczUkLIWqUE5TdSDuFuj0C5UxywIWks5uYtL-gaJpZM4TXBkC> .