Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Version 8.0.0 → 9.0.0 #635

Merged
merged 3 commits into from
Jul 25, 2019
Merged

Version 8.0.0 → 9.0.0 #635

merged 3 commits into from
Jul 25, 2019

Conversation

Gabriella439
Copy link
Contributor

@Gabriella439 Gabriella439 commented Jul 11, 2019

It's been over 30 days since the last release of the standard, so I'm starting the process to cut the next release.

The one feature I definitely plan to wait for is:

... if only because I wrote the rest of the CHANGELOG assuming the feature was merged 🙂

For other changes in progress I'll include them if they make it in before that or before the waiting period is over (i.e. 3 days since last change).

Edit: Also waiting for:

@singpolyma
Copy link
Collaborator

singpolyma commented Jul 11, 2019 via email

@singpolyma
Copy link
Collaborator

Should we also standardize banning surrogates and other non-codepoints before this release? Shouldn't be a big change and goes hand-in-hand with the new \u{...} and removing mention of surrogates from ABNF that already went in.

@Gabriella439
Copy link
Contributor Author

@singpolyma: Yeah, I can include that

@Gabriella439
Copy link
Contributor Author

Alright, I'm going to cut this release in 3 days assuming no new fixes come in (and update the CHANGELOG.md in the meantime). I'm only going to ask @ocharles to hold off on merging #650 until after 8.0.0 (mainly to avoid resetting the 3-day wait after each merged change to the standard).

@ocharles
Copy link
Member

Fine with me!

@sjakobi
Copy link
Collaborator

sjakobi commented Jul 22, 2019

Should #630 be mentioned in the changelog?

@Gabriella439
Copy link
Contributor Author

@sjakobi: Yes, I plan to update the changelog before cutting the release to reflect the recently merged pull requests

@Gabriella439
Copy link
Contributor Author

@sjakobi: Alright, I updated the CHANGELOG to reflect the recent changes

Copy link
Member

@f-f f-f left a comment

Choose a reason for hiding this comment

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

Thank you! 🙂

Copy link
Collaborator

@sjakobi sjakobi left a comment

Choose a reason for hiding this comment

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

👍

@Gabriella439 Gabriella439 merged commit 6cbf57c into master Jul 25, 2019
@Gabriella439 Gabriella439 deleted the gabriel/9_0_0 branch July 25, 2019 00:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants