Project Status Update

[nodivbyzero]

Hi @deankarn ,

Contributors are submitting PRs nearly every day.
Currently, the go-playground/validator repository has 84 open PRs, and the backlog continues to grow.
Some of these PRs are valuable and have already been approved.

I’d like to ask:

1. Who is responsible for deciding which PRs to merge?
2. How frequently should we aim to merge new PRs?

Looking forward to your thoughts.

[deankarn]

Thanks for bringing this up @nodivbyzero

I was planning in giving you and perhaps a few others after the amazing job you’ve been doing ❤️ the permissions to merge and cut releases.
I just caught the flu and been/am out of action as a result, sorry for the delay.

will try to answer regardless:

1. Up until now I have been the sole person, but as noted above would like to add you and perhaps some others to the list.

2. I think it depends on the reason: for security or fixes I would day after ensure no breaking changes within days if not asap, for added features or validations anywhere from a day to a couple weeks, to vet and ensure the logic is sound and no breaking changes.

Not sure a scheduled release cadence is required, WDYT?

[deankarn]

I’ve invited you to the maintainers team @nodivbyzero , let me know if you have any issues joining.

[nodivbyzero]

Thanks for the update!
Really appreciate you considering me for merge and release permissions.
I'm happy to help out.

Regarding release cadence, your approach makes sense to me. Prioritizing security fixes and critical updates ASAP while giving features and validations a bit more time for review seems like a solid balance.

I don’t think a strict schedule is necessary either, but maybe having some loose guidelines could help align expectations.

Would love to hear others’ thoughts as well!

[MadsRC]

Hope it is okay if I chip in here. Personally I don't think there needs to be a schedule - This is an Open Source project being run by people in their free time, so I think it is unreasonable for anyone to expect things run on a schedule. What I think is more important is that the project appears to be active - which is why I'm happy to hear that @nodivbyzero and others have been granted release permissions!