Release neqo v0.8.2

[mxinden]

• Fix empty UDP datagram handling fix(udp): ignore empty datagram #2044.
• I would like to enable ECN support on Firefox Nightly. For that I need feat(transport): Use a shorter ECN probe threshold initially #1964.

Any objections to me "uplifting" a new neqo version into mozilla-central? Since #2025 I should have permissions to do so myself.

[KershawChang]

I would like to enable ECN support on Firefox Nightly. For that I need #1964.

Any objections to me "uplifting" a new neqo version into mozilla-central? Since #2025 I should have permissions to do so myself.

No objections. Thanks for doing this!

[mxinden]

I assume it is as easy as:

1. Bump the workspace version in the root ./Cargo.toml through a pull request.
2. Once merged, tag the merge (or squash) commit and push the tag.
3. Vendor in mozilla-central as https://phabricator.services.mozilla.com/D217271 did via version bump and ./mach vendor rust.

Am I missing something @KershawChang?

[KershawChang]

I assume it is as easy as:

1. Bump the workspace `version` in the root `./Cargo.toml` through a pull request.

2. Once merged, tag the merge (or squash) commit and push the tag.

Note that when creating a new tag, I always select Set as a pre-release , but I think it doesn't matter.

3. Vendor in mozilla-central as https://phabricator.services.mozilla.com/D217271 did via version bump and `./mach vendor rust`.

Am I missing something @KershawChang?

Yeah, that's all the steps.
Thanks.

[mxinden]

For the record, mozilla-central uplift: https://phabricator.services.mozilla.com/D218637

[mxinden]

Note that when creating a new tag, I always select Set as a pre-release , but I think it doesn't matter.

I tagged as pre-release. Though I don't understand why. Given that releases are used in production, i.e. Firefox, why tag them as pre-release? I suggest not doing so for future releases. Objections @KershawChang?

[KershawChang]

Note that when creating a new tag, I always select Set as a pre-release , but I think it doesn't matter.

I tagged as pre-release. Though I don't understand why. Given that releases are used in production, i.e. Firefox, why tag them as pre-release? I suggest not doing so for future releases. Objections @KershawChang?

Good point. We can use releases in the future.