pytest 6.1?

[nicoddemus]

Hi all,

The only issue still on the milestone for 6.1 is #6324, but I don't think that's a blocker and can be postponed.

Thoughts?

Also, would @bluetech like to do the honors for this release? 😁

[nicoddemus]

Actually we probably should include #7695 as well.

[bluetech]

Also, would @bluetech like to do the honors for this release?

I haven't had much luck with pytest-django but I can try :) I can handle all of the steps except for the Twitter one.

I don't remember if we landed on regarding release candidates - for major releases only or also minor?

[nicoddemus]

I can handle all of the steps except for the Twitter one.

The tweet is usually done from your personal account, or the problem is that you don't have a twitter account?

I don't remember if we landed on regarding release candidates - for major releases only or also minor?

Just major releases, because of potential breakages.

[bluetech]

The tweet is usually done from your personal account, or the problem is that you don't have a twitter account?

I don't.

Just major releases, because of potential breakages.

OK, got it.

[nicoddemus]

I don't.

No worries, we can ask @hackebrot @The-Compiler @pfctdayelise to tweet the release from the official pytest account then. 👍

Btw perhaps makes sense to do a 6.0.2 as well? We do have a few bugs fixed there.

[bluetech]

@pytestbot please prepare release from 6.0.x.

[bluetech]

Bad dot bot!

@pytestbot please prepare release from 6.0.x

[bluetech]

@pytestbot please prepare release from 6.0.x

[bluetech]

I jinxed it. Will try to figure out the problem tomorrow.

[nicoddemus]

Heh! I will try to take a look as well.

[nicoddemus]

I've fixed it in #7719, and while at it opened the PR for 6.0.2.

Thanks for the backports! 👍

[nicoddemus]

As per #7718 (comment), let's hold a bit to implement at least some basic plugin integration testing.

[pfctdayelise]

Am standing by for tweeting duties 👀🐦
(BTW Bruno would be even better to tag @pytestdotorg in release tweets, then I will actually get notified, not just happen to notice them :))

[nicoddemus]

BTW Bruno would be even better to tag @pytestdotorg in release tweets,

Noted, thanks Brianna!

[bluetech]

Now that the plugin smoke test is in, and the problem discovered there is fixed, I intend to release 6.1 next weekend. If there are any blockers, let me know.

[nicoddemus]

Sounds good, thanks for stepping in! 👍

[bluetech]

@pytestbot please prepare release from 6.1.x

[pytestbot]

Found features or breaking changes in 6.1.x, and feature releases can only be
created from master.":

• 5585.breaking.rst
• 7667.feature.rst

[bluetech]

Oh pytestbot, what did I ever do to you??? Let's see what this is about.

[bluetech]

@pytestbot please prepare release from master

[pytestbot]

As requested, opened a PR for release 6.1.0: #7797.

[bluetech]

Note: the script is out of tune with RELEASING -- the script only allows minor releases from master but RELEASING says it should be from a (newly-created) 6.1.x branch. For now I tricked the script by opening against master and switching the PR target branch from master to 6.1.x. Will follow up later.