3.5 release next steps: Code freeze Monday 5/17

[hexfusion]

etcd 3.5 has seen a tremendous amount of new features bug fixes and performance and stability improvements. At this time I would like to thank everyone for the hard work and dedication. As per the community meeting on May 6th we have outlined Monday, May 17th as code freeze for the 3.5 release. Below are the proposed series of events for input.

Steps:

• cut release-3.5 branch from master (now main). All future merges to main will be 3.6 moving forward (Monday AM 5/17).
• cut new v3.5.0-beta.3
• cut new modularized release v3.5.0-beta.3 (Monday AM 5/17).
• begin correctness and performance/stress testing (ideas, ownership?)

After testing and validation of the beta, we can consider a sequential beta release or move towards a v3.5 release candidate.

Your input is greatly appreciated.

cc @xiang90 @wenjiaswe @ptabor @gyuho @jingyih @lilic @jpbetz @spzala

[wenjiaswe]

Thank you very much @hexfusion !

begin correctness and performance/stress testing (ideas, ownership?)

Would you mind putting together a "gift registry" so we could plan and start pick up?

[gyuho]

cut release-3.5 branch from master (now main). All future merges to main will be 3.6 moving forward (Monday AM 5/17).

As we discussed, @hexfusion @lilic will take ownership on the release management, right?

begin correctness and performance/stress testing (ideas, ownership?)

We have some in-house component that does this, but I believe our continuous functional tests are good enough.

Please chime in if you have better ideas.

[gyuho]

@hexfusion Please feel free to email and ping other maintainers via etcd-dev mailing list.

[ptabor]

• Try to stabilize (official versions) our dependencies:
  • Release bbolt 1.3.6 (bbolt 1.3.6 release plan bbolt#278)
  • Zap (1.17 release uber-go/zap#942)
• Verify: Migrate cluster attributes to use v3 backend #11427 (comment)
• When beta is out we can ask k8s to incorporate update etcd, grpc, protobuf dependencies kubernetes/kubernetes#100488 (@liggitt ).
  This will allow us to get CI feedback from k8s.
• When branch --release-3.5 is tagged, we will run our in-house tests
• Functional tests are a little flaky (not more than release-3.4), but if that's the main signal, someone should dig in
• Blog-post was started by @gyuho (https://docs.google.com/document/d/1F2p2LVPo4gj3n8XFMd4QrlarbCdJrbd-pNrT3XLYXmM/edit?usp=sharing)
• Investigate the deadlock in example: integration/clientv3/examples test flakes frequently #12983

[hexfusion]

As we discussed, @hexfusion @lilic will take ownership on the release management, right?

correct

[lilic]

Functional tests are a little flaky (not more than release-3.4), but if that's the main signal, someone should dig in

If no one is looking into this, I can have a look end of this week. @ptabor do you have a list of these? Otherwise I can have a look at previous CI runs.

[serathius]

I would be happy to help

[hexfusion]

Red Hat team was preparing to cut the release-3.5 branch at approximately 8:00am EDT. If we have a need to hold this please reach out.

cc @ptabor @gyuho @lilic

[ptabor]

@hexfusion: I think we can tag the branch.

• I suspect Migrate cluster attributes to use v3 backend #11427 (comment) will require a patch, but its OK.
• I still have some hope to merge Split etcdctl into etcdctl (public API access) & etcdutl (direct surgery on files) #12971 into. But this requires your approval.

[ptabor]

Functional tests are a little flaky (not more than release-3.4), but if that's the main signal, someone should dig in

If no one is looking into this, I can have a look end of this week. @ptabor do you have a list of these? Otherwise I can have a look at previous CI runs.

I've seen them on CI, but unfortunately I didn't collected the links and its not easy to search by 'jobs' currently. Running in a forloop locally mightbe an option as well.

[hexfusion]

I still have some hope to merge #12971 into. But this requires your approval.

complete