Skip to content

Conversation

@nicoddemus
Copy link
Member

No description provided.

@codecov
Copy link

codecov bot commented Aug 5, 2019

Codecov Report

Merging #5699 into master will increase coverage by 0.03%.
The diff coverage is n/a.

Impacted file tree graph

@@            Coverage Diff             @@
##           master    #5699      +/-   ##
==========================================
+ Coverage   96.14%   96.17%   +0.03%     
==========================================
  Files         117      117              
  Lines       25864    25864              
  Branches     2498     2498              
==========================================
+ Hits        24867    24875       +8     
+ Misses        696      689       -7     
+ Partials      301      300       -1
Impacted Files Coverage Δ
src/_pytest/doctest.py 96.62% <0%> (+2.24%) ⬆️
src/_pytest/pastebin.py 91.22% <0%> (+3.5%) ⬆️

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update bf3aa72...f43b54a. Read the comment docs.

@blueyed
Copy link
Contributor

blueyed commented Aug 5, 2019

Will you do 5.0.2 then also?

@nicoddemus
Copy link
Member Author

I'm planning on doing 5.1 after #5605 gets merged.

@nicoddemus nicoddemus merged commit 68c486a into pytest-dev:master Aug 5, 2019
@nicoddemus nicoddemus deleted the 4.6.5-release-notes branch August 5, 2019 19:25
@blueyed
Copy link
Contributor

blueyed commented Aug 8, 2019

I'm planning on doing 5.1 after #5605 gets merged.

Ok, left some remarks there.

I've expected the 5.x series to have priority over 4.6 though - i.e. a bugfix release (5.0.2) there before / (or at least) together with 4.6.x.

@nicoddemus
Copy link
Member Author

nicoddemus commented Aug 8, 2019

I've expected the 5.x series to have priority over 4.6 though - i.e. a bugfix release (5.0.2) there before / (or at least) together with 4.6.x.

I was expecting to release 5.1 (which still had one pending issue) right after 4.6.5 (which had no other pending issues), but that plan didn't realize as I hoped. 😕

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.

2 participants