Skip to content

Commit

Permalink
Update changelog for version 0.36.0 (#941)
Browse files Browse the repository at this point in the history 
* Update changelog for version 0.36.0

Related to #940

---------

Co-authored-by: Itamar Turner-Trauring <itamar@itamarst.org>
  • Loading branch information
@4383 @itamarst
4383 and itamarst committed Mar 25, 2024
1 parent 3fcc9a5 commit e1afe7b
Showing 1 changed file with 11 additions and 0 deletions.
11 changes: 11 additions & 0 deletions NEWS
View file
@@ -1,6 +1,17 @@
Unreleased
==========

0.36.0
======

* [fix] Make sure asyncio hub doesn't use greendns for asyncio DNS APIs https://github.com/eventlet/eventlet/pull/938
* [fix] Make asyncio.to_thread work with the same semantics as normal asyncio https://github.com/eventlet/eventlet/pull/930
* [fix] Refactor congruence checks based on assert at runtime https://github.com/eventlet/eventlet/pull/932
* [tests] Run tests on macOS in CI, and some fixes to get it in reasonable state (#list https://github.com/eventlet/eventlet/pull/934
* [fix] Fix wsgi.server shutdown for in-flight requests https://github.com/eventlet/eventlet/pull/912
* [feature] Add debug convenience helpers - asyncio, threads https://github.com/eventlet/eventlet/pull/925
* [fix] Handle errors better. https://github.com/eventlet/eventlet/pull/923

0.35.2
======

Expand Down

2 comments on commit e1afe7b

@kloczek
Copy link
Contributor

@kloczek kloczek commented on e1afe7b Mar 25, 2024 •
edited

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

New version has been tagged as 0.36.0 and not as v0.36.0.
Is this permanent change in tagging convention or just typo? 🤔

@4383
Copy link
Member Author

@4383 4383 commented on e1afe7b Mar 26, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

At the origin it was a mistake (a typo), but since the modernization of our delivery process (#845, #843) I was also thinking to change this tag naming convention.
I don't see reasons to prefix each tag with the letter "v"...

More complexity is equal to more chances to make a mistake, my previous mistake is the proof of this. Let's stick to a more simpler convention.

Hope I answered your question.

Please sign in to comment.