Percona toolkit release v3.3.2

[percona-csalguero]

This is WIP.

• Updated the changelog to reflect the current status and what's need to be completed for release.
• Updated 3.3.1 release date because it was not set by the release script
• Sorted previous releases ticket to maintain our sorting rules.

Missing things:

• [ ] Update Go dependencies

[vinzlj]

Hi @percona-csalguero, any update on this release?

I'm looking forward to trying the drop_swap method with MySQL 8+.

Thanks!

[percona-csalguero]

I cannot tell you a release date, but you can download the latest versions from the 3.x branch.

Regards

[rnovikovP]

@percona-csalguero, I see in PR for 3.3.2 in TODO issues we plan for 3.4.0 release. So I'm not very clear what we are trying to achieve with this PR

[rnovikovP]

For changelog - let's just clean up the first item description as this is very confusing. And I'm not clear why we including items we still have IN REVIEW (status like PT-1627)

[percona-csalguero]

For changelog - let's just clean up the first item description as this is very confusing. And I'm not clear why we including items we still have IN REVIEW (status like PT-1627)

I've updated the changelog and PT-1627 and PT-1398 are merged now.

[benlangfeld]

Hey guys. My team just got bit by this again yesterday. What is blocking this release?

[denisok]

@benlangfeld looks like we are now targeting 3.4 instead, there are more fixes and etc there: https://jira.percona.com/projects/PT/versions/15001 https://jira.percona.com/projects/RM/issues/RM-930

what quality do you need that fix to e, maybe we could provide RC or some custom build? CC @rnovikovP

[benlangfeld]

@denisok The problem is just the difficulty of coordinating installation of custom builds for all members of a large team, vs tracking the latest release. The fix I care about was merged 4 months ago; it doesn't seem to be necessary to have such a long release cycle for such a simple thing.

[benlangfeld]

@denisok @percona-csalguero Is it possible to just cut a release? It seems we just keep waiting to include more and more stuff and there's no cut-off.

[ryantology]

I would like to also request a bump to get this pr released: https://github.com/percona/percona-toolkit/pull/474 If it is possible to get a minor revision or RC that would be great. We are able to work around this but it does cause confusion for the team when they don't have the custom build.

[percona-csalguero]

Hi, Do you need deb or rpm packages? If not, you can download the file from the master branch.

Regards

[benlangfeld]

Hi, Do you need deb or rpm packages? If not, you can download the file from the master branch.

Regards

Hey @percona-csalguero . I think it would be really helpful if someone could explain why Percona is so resistant to releasing a new version publicly after so much time has passed. Those of us who consume these things are having a really hard time understanding what the problem is, given it seems we have a super simple solution: pull the trigger on the new version.

[percona-csalguero]

Hi, Do you need deb or rpm packages? If not, you can download the file from the master branch. Regards

Hey @percona-csalguero . I think it would be really helpful if someone could explain why Percona is so resistant to releasing a new version publicly after so much time has passed. Those of us who consume these things are having a really hard time understanding what the problem is, given it seems we have a super simple solution: pull the trigger on the new version.

Hi. We are working in a new release and the idea is to release it soon.

[denisok]

@benlangfeld https://github.com/percona/percona-toolkit/pull/539 should progress faster