Skip to content

MySQL community pinboard #12

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
Andersson007 opened this issue Jul 31, 2020 · 27 comments
Closed

MySQL community pinboard #12

Andersson007 opened this issue Jul 31, 2020 · 27 comments
Labels

Comments

@Andersson007
Copy link
Collaborator

Copied from ansible/community#439

We could collectively benefit from forming a Working Group related to MySQL and MariaDB integration. We have quite some contributors and users that are interested in improving this integration.

So this issue is a call to potential interested parties (earlier and existing contributors to Ansible). The benefits of having a Working Group is that members of the Working Group can:

  • test, review and add shipits to existing MySQL PRs
  • work collectively on a MySQL roadmap
  • provide a single-point-of-contact for interested MySQL contributors
  • collaborate on a MySQL-specific Wiki
@Andersson007
Copy link
Collaborator Author

@Andersson007
Copy link
Collaborator Author

@Jorge-Rodriguez
Copy link
Contributor

@Andersson007 I don't seem to be able to edit the wiki to add myself to the table.

@Andersson007
Copy link
Collaborator Author

@Jorge-Rodriguez ah, sorry, just changed settings, could you please try again

@Jorge-Rodriguez

This comment has been minimized.

@Andersson007

This comment has been minimized.

@Jorge-Rodriguez

This comment has been minimized.

@bmildren

This comment has been minimized.

@Andersson007

This comment has been minimized.

@Jorge-Rodriguez

This comment has been minimized.

@Andersson007

This comment has been minimized.

@Andersson007
Copy link
Collaborator Author

Andersson007 commented Mar 25, 2021

@Jorge-Rodriguez

  1. do you need that 2 branches https://github.com/ansible-collections/community.mysql/branches ?
  2. have you seen my email? (nothing urgent or super important)

@Jorge-Rodriguez
Copy link
Contributor

Jorge-Rodriguez commented Mar 25, 2021

@Andersson007 I don't need the branches, thank you for reminding me that they were left over, I've deleted then now. And yes, I saw your email. I've been meaning to answer but things have been quite busy on my end.

@Andersson007
Copy link
Collaborator Author

@Jorge-Rodriguez cool, thanks for the confirmation! There's even no need to answer. It was just random thoughts:) I wanted to be sure it didn't end up in a spam folder or something.

@Andersson007
Copy link
Collaborator Author

FYI: I'm releasing community.mysql 2.0.0 tomorrow morning (2021-04-15)

@Andersson007
Copy link
Collaborator Author

FYI: In addition to fully replace stopslave, startslave, etc. state values with corresponding stopreplica, etc. in community.mysql 3.0.0 next autumn, I've just announced replacement of Is_Slave with Is_Replica (I'll add a warning ASAP).

W're also gonna replace master with primary.

@Andersson007
Copy link
Collaborator Author

This is the plan for 3.0.0:

major_changes:
- mysql_replication - the return value ``Is_Slave`` and ``Is_Master`` will be replaced with ``Is_Replica`` and ``Is_Primary`` in ``community.mysql`` 3.0.0 (https://github.com/ansible-collections/community.mysql/issues/145).
- mysql_replication - the word ``master`` in messages returned by the module will be replaced with ``primary`` in ``community.mysql`` 3.0.0 (https://github.com/ansible-collections/community.mysql/issues/145).

@Andersson007
Copy link
Collaborator Author

community.mysql 2.0.0 has been released

New branch stable-2 has been created as well

It means that we have to backport to stable-2 (by cherry-picking from main) all changes we'll merge to main since now (except breaking changes!).
I created a label needs_backport_to_stable-2 - please put it on all PRs you'll merge since now, then create backports. Thanks!
Don't put this label on PRs with breaking changes! :)

I'll try to nail down ansibullbot here later to create backports automatically.

@Andersson007
Copy link
Collaborator Author

Andersson007 commented Aug 26, 2021

I'm happy to announce that the registration (free) for the Ansible Contributor Summit is open.

Which day should you attend?

  • If you are wondering what it means to "contribute" to Ansible, or if you have been using Ansible for a while and are thinking of ways to get more involved with the project and community, then Day 1 (September 28, Tuesday) is for you!
  • If you have already been contributing or participating in our previous Contributor Summits, you are still welcome to attend Day 1, however we think that Day 2 (October 1, Friday) will be more interesting for you.

Refer to the registration page for details.

See you at the summit!

@dericcrago
Copy link

Reminder - AnsibleFest and Ansible Contributor Summit are 1 week away!

In case you missed it, we will also be having a Hackathon throughout the entire Ansible Contributor Summit and AnsibleFest. This is a great opportunity to collaborate in real time with other members of the Ansible Community!

For more info and the latest updates, please see the Ansible Contributor Summit 2021.09 HackMD.

@Andersson007
Copy link
Collaborator Author

Reminder - Day 1 of the Ansible Contributor Summit and the Hackathon start tomorrow (Tuesday, 28 September 2021)!

For more info and the latest updates, please see the Ansible Contributor Summit 2021.09 HackMD.

@Andersson007
Copy link
Collaborator Author

Reminder - Day 2 of the Ansible Contributor Summit and the last day of the Hackathon start tomorrow (Friday, 1 October 2021)!

For more info and the latest updates, please see the Ansible Contributor Summit 2021.09 HackMD.

@Andersson007
Copy link
Collaborator Author

FYI: if someone else from current maintainers wants to release 3.1.1 and 2.3.4 (in other words learn how to release / become a release engineer here), I would be happy to lead you through the process. Please let me know:)

p.s. we can wait for the day / time suitable for you

@laurent-indermuehle
Copy link
Collaborator

FYI: I'm releasing community.mysql 1.4.8, 2.3.9 and 3.4.0

@laurent-indermuehle
Copy link
Collaborator

The community.mysql collection versions 1.4.8, 2.3.9 and 3.4.0 have been released.

@laurent-indermuehle
Copy link
Collaborator

The community.mysql collection version 3.8.0 has been released.

@Andersson007
Copy link
Collaborator Author

Moving to forum, closing this one. Please join the group and let's continue on the forum, thanks everyone!

@Andersson007 Andersson007 unpinned this issue Nov 9, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

5 participants