Repository navigation
Announcement: Driving towards zero 2.0 bugs by May 10 (ZBB) #20809
Description
As we are getting closer to .NET Core 2.0 Preview and .NET Standard 2.0 Preview ship dates, we would like to drive 2.0.0 bugs down to 0 by May 10 (see milestone details) = ZBB (zero bug bounce) date.
We would like to encourage and ask our contributors to help us drive towards that goal. Be part of .NET Core 2.0 release!
How can you, the CoreFX contributors, help?
- If you're picking up issues to work on, prefer issues marked as 2.0.0 bugs (some are even up-for-grabs).
- If you spot something in Future milestone that should be part of 2.0, please say so and explain why (loop in @karelz). Conversely if there's something in 2.0 that perhaps is not as significant as it seems.
- We strive to deliver high-quality product, so impactful bugs, compatibility, reliability and performance issues are top priority. Migration to .NET Core 2.0 from .NET Core 1.1 or from .NET Framework is one of the key priorities.
- Adding additional new APIs, fixing pre-existing bugs or fixing corner-case issues with lower impact and with existing workaround is lower priority, not tracked as 2.0.
- Issues with no milestone - we expect to set their milestone in upcoming weeks (part of ongoing "triage"), so if you see something must-have for 2.0 there, please say so and explain why (loop in @karelz).
- Watch for upcoming official preview announcements (on .NET blog or on dotnet/Announcements repo) to help validate and dogfood the end-to-end .NET Core 2.0 experience before final release.
- Note: You can dogfood even our daily builds - see dogfooding steps
Not surprisingly, to deliver overall end-to-end .NET Core 2.0 experience, similar ZBB efforts happen in our sister repos like CoreCLR, core-setup, etc. - we will welcome help in those as well, if you're interested.
Twitter announcement: https://twitter.com/ziki_cz/status/846839252629385216
Activity
karelz commentedon Mar 28, 2017
cc'ing recently active contributors (in random order)
@hughbe @justinvp @JonHanna @xoofx @AlexRadch @stephenmichaelf @nietras
@benaadams @fujiy @jamesqo @SamuelEnglard @couven92 @tintoy @sparraguerra @vcsjones
@bartdesmet @lmolkova @dnickless @bbowyersmyth @matekm @fitzchak @omajid
@seanshpark @hseok-oh @ofirmakmal @hqueue @chunseoklee @Gregory-Bell @jcouv
@Clockwork-Muse @jyoungyun @odyth @lemmaa @kant2002 @lucenticus @bmeverett @ViIvanov @craigajohnson @tdupont750 @KirillOsenkov @svick @jirisykora83
@parjong @tralivali1234 @shrah @khellang @cshung @nikitozz @andrewlock @CesarBS
karelz commentedon Mar 28, 2017
@roji @alaatm @cakine @TiagoSoczek @BRFalcon @ChrisEelmaa @Arc001 @thiagocamargos
@mramosMS @anthonylangsworth @borgdylan @SteveDesmond-ca @StanislavUshakov @tuespetre @rionmonster @jesperll @kwaazaar @onovotny @NickCraver @cod7alex @IvanKishchenko @daflame76 @cydhaselton @pdeligia @patryk9200 @attilah @reaction1989 @mikedn @Jaedson33 @jaredcnance @TylerBrinkley @darxis @msalsbery @dhoehna @manofstick @FireAlkazar @SWY1985 @willdean @tmds @WinCPP @dcwuser @dennisdietrich @tinchou @the-dwyer @TMiNus @yaakov-h @ofirmakmal
[-]Announcement: Driving towards zero 2.0 bugs by 5/10 (ZBB)[/-][+]Announcement: Driving towards zero 2.0 bugs by May 10 (ZBB)[/+]ctolkien commentedon Mar 29, 2017
milestone detailslinks to the edit page (which non owners can't access) should be: https://github.com/dotnet/corefx/milestone/4danmoseley commentedon Mar 29, 2017
Thanks @ctolkien I fixed the link. As you see from that list we have a lot to do :)
tarekgh commentedon Apr 12, 2017
@karelz we are keeping this issue just for announcing and no action needed against this issue. right?
karelz commentedon Apr 12, 2017
Yep, I'd like to keep it opened until 5/10. I can move it into Future milestone, so it doesn't affect our bug count and reports ;-)
karelz commentedon Apr 22, 2017
FYI if you're not on Twitter:
Here's progress we're making on CoreFX, CoreCLR, core-setup and WCF repos towards 2.0: https://twitter.com/ziki_cz/status/854409726754299904 (as of Tuesday 4/18)
Huge thanks to all contributors who jumped in and actively help us drive the 2.0 bugs!
karelz commentedon Apr 25, 2017
Announcement: For next 2.5 weeks (until May 10) all API additions and larger changes will get more scrutiny. If they are risky and non-essential for .NET Core 2.0, we may delay merging PR until post-5/10.
Also note that release/2.0.0 branch is now created and will receive last full integration from master on 5/10. Changes after 5/10 will be cherry-picked from master to release/2.0.0 branch.
New update on Twitter with latest progress on 2.0 bugs: https://twitter.com/ziki_cz/status/856692569492774912 (as of Monday 4/24)
karelz commentedon Apr 28, 2017
Another update on remaining issues: https://twitter.com/ziki_cz/status/858042980673957889 (as of couple of hours ago)
Huge progress in both fixes and triage!
Note that we have new Post-ZBB label to mark issues which are important for 2.0, but don't affect product source code (e.g. documentation bugs, infrastructure issues), so they will be exempt from ZBB rule (so far only 9 across all 4 repos).
karelz commentedon May 2, 2017
Another update on remaining issues: https://twitter.com/ziki_cz/status/859459337042837504
Only 1 week and 1 day left before 5/10
Great progress on issues without milestone (potential work).
So far only 13 bugs are marked as Post-ZBB (documentation bugs, infrastructure issues).
We will likely slip a few Networking issues past 5/10.
karelz commentedon May 8, 2017
Another update: https://twitter.com/ziki_cz/status/861641617865711616
Only 3 days left before 5/10 (end of day)
So far only 15 bugs are marked as Post-ZBB (documentation bugs, infrastructure issues and couple of late small features based on feedback from community).
We will slip few Networking issues past 5/10.
karelz commentedon May 8, 2017
Quick update on our short-term plans:
karelz commentedon May 10, 2017
We are very close to ZBB - few more hours left.
Remaining: 27 bugs for ZBB: CoreFX 13 + CoreCLR 1 + core-setup 6 + WCF 7
90 issues have ZBB exception from theses reasons:
Only 14 issues without milestone - except one, all of them created in last 24 hours.
3 remaining items
garfbradaz commentedon May 11, 2017
404 on link :)
tarekgh commentedon May 11, 2017
@garfbradaz I fixed the link.
karelz commentedon May 11, 2017
Last 5 issues for ZBB (queries restricted to issues created before 5/10). Almost there!
karelz commentedon May 13, 2017
Last 3 issues for ZBB (queries restricted to issues created before 5/10). Getting closer and closer!
karelz commentedon May 13, 2017
Here are 2.0 bugs filed after 5/10 - some of them by community and some of them even fixed right away!
Community contributions (excluding Microsoft and Samsung employees):
tarekgh commentedon May 13, 2017
dotnet/coreclr#11578 (@slozier) still opened because we need to add the test for the fixed case. We are waiting to get successful coreclr package in corefx repo.
karelz commentedon May 16, 2017
We have hit ZBB (zero 2.0 bugs filed before 5/10) !!! Hooray!!!
Congratulations to the teams driving hard to get here! And to all contributors submitting fixes and helping us validate the bits!
Announced here: https://twitter.com/ziki_cz/status/864614714847903744
Pretty graphs here: https://twitter.com/ziki_cz/status/864679857472454656 (note graphs capture also 20 extra wcf bugs in milestone S118 which are not part of 2.0 - the graphs will be adjusted in next update)
We awarded a few exceptions along the way (one-off Post-ZBB label, and 3 areas: Networking, Infrastructure and Tizen). Here are details:
work:
Infrastructure - 2
Tizen - 1
Tizen - 9
Tizen - 3
We also started receiving high-value bug reports from people trying out Preview 1 - thanks everyone for your help!
What's next for .NET Core?
We are in "ask mode" until 5/26 (1.5 weeks), i.e. high-impactful bug fixes can get in, we have to ask shiproom (risk vs. value will be assessed).
Starting 5/27, we will be in "Escrow mode", i.e. the bar for bug fixes goes even higher (to stabilize) and only truly important fixes (show-stoppers) will get in.
Every change will require shiproom discussion if taking it is worth the risk of "resetting Escrow". In practice it means rel/2.0.0 branch will be locking down for final release.
karelz commentedon May 23, 2017
Latest update on 2.0 bugs -- see graphs in https://twitter.com/ziki_cz/status/866981185267707904
Last week of Ask mode, then we are in Escrow mode (i.e. truly impactful bugs only, the bar will be high)
Thanks everyone for filing great bugs! Highlights:
System.Data.SqlClient, we adjusted investment in the area and asked everyone for help -- see dotnet/corefx#19970 for details.Overall 2.0 bugs filed by community:
System.Net(HttpListener) - 24 bugsSystem.Data.SqlClient- 8 bugsSystem.Net- 4 bugsSystem.Security- 3 bugsSystem.Runtime- 3 bugsyaakov-h commentedon May 24, 2017
@karelz that twitter link 404s.
karelz commentedon May 24, 2017
I deleted the original tweet couple of minutes after posting the GitHub reply, I immediately retweeted it with fixed typo.
I updated GH to the new link right away, so you likely clicked the old link from email notification. Here it is again: https://twitter.com/ziki_cz/status/866981185267707904
karelz commentedon Jun 25, 2017
Thanks everyone for your help with ZBB and post-ZBB work. We are now deep in Escrow - i.e. taking only the most critical bug fixes.
I don't think we need this announcement issue around anymore.