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

Release/v0.36.0 #2340

Merged
merged 2 commits into from
Jan 24, 2022
Merged

Release/v0.36.0 #2340

merged 2 commits into from
Jan 24, 2022

Conversation

oleiade
Copy link
Member

@oleiade oleiade commented Jan 17, 2022

This PR adds release notes for the upcoming 0.36.0 version of K6.

To compile them, I went through the commit history from 0.35.0 up to the current state of master, and looked at/experimented with most PRs that went through during this period. I might have missed things, overlooked overs, left changes so small that I didn't find them too relevant for release notes.

Please let me know if you think I've forgotten anything, explained something wrong, or didn't follow the existing template close enough. This is my first time, and I'm looking to get as much feedback as possible 🐻

Not being too familiar with SourceMaps myself, I could definitely use your help @mstoykov when it comes to describing and demonstrating the feature. Could you support me with that? 😸

Copy link
Contributor

@codebien codebien left a comment

Choose a reason for hiding this comment

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

I spot some but not all, generally, we should exec s/K6/k6/ for branding consistency.

release notes/v0.36.0.md Outdated Show resolved Hide resolved
release notes/v0.36.0.md Outdated Show resolved Hide resolved
release notes/v0.36.0.md Outdated Show resolved Hide resolved
release notes/v0.36.0.md Outdated Show resolved Hide resolved
release notes/v0.36.0.md Outdated Show resolved Hide resolved
release notes/v0.36.0.md Outdated Show resolved Hide resolved
Copy link
Contributor

@yorugac yorugac left a comment

Choose a reason for hiding this comment

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

👏 I've noticed some simple improvements but also added a couple of more complex suggestions: please see.

Also, 27 closed issues! 😲 They accumulated probably (like abort test) but still, that's almost twice more than prev time.

release notes/v0.36.0.md Outdated Show resolved Hide resolved
release notes/v0.36.0.md Outdated Show resolved Hide resolved
release notes/v0.36.0.md Outdated Show resolved Hide resolved
release notes/v0.36.0.md Outdated Show resolved Hide resolved
release notes/v0.36.0.md Outdated Show resolved Hide resolved
release notes/v0.36.0.md Outdated Show resolved Hide resolved
release notes/v0.36.0.md Outdated Show resolved Hide resolved
release notes/v0.36.0.md Show resolved Hide resolved
release notes/v0.36.0.md Outdated Show resolved Hide resolved
release notes/v0.36.0.md Show resolved Hide resolved
release notes/v0.36.0.md Outdated Show resolved Hide resolved
release notes/v0.36.0.md Outdated Show resolved Hide resolved
@na-- na-- added this to the v0.36.0 milestone Jan 18, 2022
release notes/v0.36.0.md Outdated Show resolved Hide resolved
release notes/v0.36.0.md Outdated Show resolved Hide resolved
release notes/v0.36.0.md Outdated Show resolved Hide resolved
Copy link
Contributor

@yorugac yorugac left a comment

Choose a reason for hiding this comment

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

Thanks, @oleiade, for the update! I think with link to the docs, new interfaces in Extensions section are just right.

Just a few re-phrasing suggestions from my side 🙂

release notes/v0.36.0.md Outdated Show resolved Hide resolved
release notes/v0.36.0.md Outdated Show resolved Hide resolved
release notes/v0.36.0.md Outdated Show resolved Hide resolved
release notes/v0.36.0.md Outdated Show resolved Hide resolved
release notes/v0.36.0.md Outdated Show resolved Hide resolved
@oleiade oleiade force-pushed the release/v0.36.0 branch 2 times, most recently from e01c0c0 to bdf8030 Compare January 19, 2022 15:45
release notes/v0.36.0.md Outdated Show resolved Hide resolved
release notes/v0.36.0.md Outdated Show resolved Hide resolved
release notes/v0.36.0.md Outdated Show resolved Hide resolved
release notes/v0.36.0.md Outdated Show resolved Hide resolved
@oleiade oleiade force-pushed the release/v0.36.0 branch 2 times, most recently from 9b064ec to f261286 Compare January 20, 2022 09:43
release notes/v0.36.0.md Outdated Show resolved Hide resolved
release notes/v0.36.0.md Outdated Show resolved Hide resolved
release notes/v0.36.0.md Outdated Show resolved Hide resolved
release notes/v0.36.0.md Outdated Show resolved Hide resolved
release notes/v0.36.0.md Outdated Show resolved Hide resolved
@na--
Copy link
Member

na-- commented Jan 20, 2022

LGTM overall, these are the only nitpicks I have

@codebien codebien self-requested a review January 20, 2022 14:01
Copy link
Contributor

@codebien codebien left a comment

Choose a reason for hiding this comment

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

Small things

release notes/v0.36.0.md Outdated Show resolved Hide resolved
release notes/v0.36.0.md Outdated Show resolved Hide resolved
release notes/v0.36.0.md Outdated Show resolved Hide resolved
release notes/v0.36.0.md Outdated Show resolved Hide resolved
release notes/v0.36.0.md Outdated Show resolved Hide resolved
release notes/v0.36.0.md Outdated Show resolved Hide resolved
Copy link
Contributor

@codebien codebien left a comment

Choose a reason for hiding this comment

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

@oleiade LGTM, thanks for doing it 👏

We should link grafana/k6-docs#556 and grafana/k6-docs#559 when they will be merged

release notes/v0.36.0.md Outdated Show resolved Hide resolved
release notes/v0.36.0.md Outdated Show resolved Hide resolved
release notes/v0.36.0.md Outdated Show resolved Hide resolved
release notes/v0.36.0.md Outdated Show resolved Hide resolved
na--
na-- previously approved these changes Jan 24, 2022
Copy link
Member

@na-- na-- left a comment

Choose a reason for hiding this comment

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

LGTM besides the minor nitpicks

@oleiade
Copy link
Member Author

oleiade commented Jan 24, 2022

This PR can now be considered ready to merge. To proceed, we should ensure to rebase --autosquash the fix up commits first.

yorugac
yorugac previously approved these changes Jan 24, 2022
Copy link
Contributor

@yorugac yorugac left a comment

Choose a reason for hiding this comment

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

LGTM 👍

release notes/v0.36.0.md Outdated Show resolved Hide resolved
mstoykov
mstoykov previously approved these changes Jan 24, 2022
Copy link
Contributor

@mstoykov mstoykov left a comment

Choose a reason for hiding this comment

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

LGTM apart from the ... more accurate wording of why 'optional chaining' isn't usable.

In this case I mean that if you just have var something = {"something": {}}; console.log(something?.something?.else?.third); will work as babel is not used at all. But needing babel, usually for import/export, means that you can't use it.

@mstoykov mstoykov merged commit ff3f8df into master Jan 24, 2022
@mstoykov mstoykov deleted the release/v0.36.0 branch January 24, 2022 09:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants