maintenance: plans for a new release + suggestions

[pano9000]

Hi all,

I wonder if there currently is any "path" towards the next release?
It has been a year since the last release, and I don't seem to see any path towards a new release, but an ever growing backlog of PRs of small to big size, some of which will bring a lot of improvements, but are currently a bit a pain to be merged, e.g. the effort to split the tests into separate files, or the effort to introduce an "options" object to different validators.

So my suggestion going forward would be:

1. Focus first on getting a new release ready of what we already have in master + maybe check the open PRs for some of the easy/simple "fixes" and get these in as well - this will include fixing "blocking" issues like Dependency Issue: Installation via npm fails #2123

2. Afterwards identify the "easy" "feat" and "refactor" PRs, e.g. the mostly the ones that add features to existing validators (e.g. I can see a ton of isMobilePhone PRs) - afterwards do another release

3. Work on getting these "bigger" PRs in

Pinging the current maintainers, what do you think?
@profnandaa, @tux-tn, @rubiin, @ezkemboi

If you need any help, with that, kindly let me know, happy to help here as much as I can.

[ezkemboi]

Sure, great feedback, thank you. I will consult with other maintainers and see how we can do that. Prof. Nandaa was the one who used to help on new releases

…

On Thu, Dec 8, 2022 at 12:39 PM Panagiotis Papadopoulos < ***@***.***> wrote: Hi all, I wonder if there currently is any "path" towards the next release? It has been a year since the last release, and I don't seem to see any path towards a new release, but an ever growing backlog of PRs of small to big size, some of which will bring a lot of improvements, but are currently a bit a pain to be merged, e.g. the effort to split the tests into separate files, or the effort to introduce an "options" object to different validators. So my suggestion going forward would be: 1. Focus first on getting a new release ready of what we already have in master + maybe check the open PRs for some of the easy/simple "fixes" and get these in as well - this will include fixing "blocking" issues like #2123 <#2123> 2. Afterwards identify the "easy" "feat" and "refactor" PRs, e.g. the mostly the ones that add features to existing validators (e.g. I can see a ton of isMobilePhone PRs) - afterwards do another release 3. Work on getting these "bigger" PRs in Pinging the current maintainers, what do you think? @profnandaa <https://github.com/profnandaa>, @tux-tn <https://github.com/tux-tn>, @rubiin <https://github.com/rubiin>, @ezkemboi <https://github.com/ezkemboi> If you need any help, with that, kindly let me know, happy to help here as much as I can. — Reply to this email directly, view it on GitHub <#2125>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ALVWPH7VPDL7TBEKCTVX77LWMGUDZANCNFSM6AAAAAASX5AIDE> . You are receiving this because you were mentioned.Message ID: ***@***.***>

-- Regards, Ezrqn Kemboi. <http://www.ezrqnkemboi.dev> Software Engineer | Innovator | Open Source Enthusiast

[WikiRik]

Sounds like a good plan. I'm also happy to help with initial reviews and identifying in which categories PRs fall. I think that @braaar is also willing to help and maybe @pixelbucket-dev as well (although I believe he is more interested in working on #1874 and other issues coming out of that)

[braaar]

I'm happy to help out.

I agree that it's important to get an overview of what we want to include in releases. I think we've had a pretty tight focus on backwards compatibility recently, so we can definitely do a minor version release with a lot of new features and fixes before considering a major release.

To me it seems like commit messages are a bit of a wild west right now, which must make it a bit harder to put together release notes. Maybe we could use a github action to enforce PR titles/commit messages, like this

[WikiRik]

I agree that it's important to get an overview of what we want to include in releases. I think we've had a pretty tight focus on backwards compatibility recently, so we can definitely do a minor version release with a lot of new features and fixes before considering a major release.

Recently yes, but there have been quite some PRs merged over the last year so it might be safer to just do a major release. But that's also something to consider when making the CHANGELOG

[pixelbucket-dev]

I'm happy to help out.

I agree that it's important to get an overview of what we want to include in releases. I think we've had a pretty tight focus on backwards compatibility recently, so we can definitely do a minor version release with a lot of new features and fixes before considering a major release.

To me it seems like commit messages are a bit of a wild west right now, which must make it a bit harder to put together release notes. Maybe we could use a github action to enforce PR titles/commit messages, like this

I agree here, for release note management we could consider squash and merge to have predictable merge commits.

[pixelbucket-dev]

Sounds like a good plan. I'm also happy to help with initial reviews and identifying in which categories PRs fall. I think that @braaar is also willing to help and maybe @pixelbucket-dev as well (although I believe he is more interested in working on #1874 and other issues coming out of that)

Yes, in general I am happy to help. However, I am quite new to the project, so I don't have the historic overview (yet) to judge all of the above. Let me know if I can assist in something specific, e.g. review or category identification :).

[profnandaa]

Apologies, I've been quite slow on my end in following up with the reviews but I should be getting back to form now.

Yes, reviews are highly welcome! It makes the maintainers work easier, knowing that a couple of more eyes have had a look at the PRs. So, I covet your help here @WikiRik @braaar @pixelbucket-dev and anyone else.

That said, we should be able to get out a release by mid Jan 2023. Will be nice to have the holiday season remain quiet.

Thanks for your suggestions @pano9000, we'll take that to account.

/cc. @tux-tn @ezkemboi

[profnandaa]

NB: while reviewing, those with merge conflicts on README.md, the authors don't need to change anything, I will fix those during merging and still retain the contribution credits for the authors.

[pano9000]

Hi all,

just wanted to cautiously ask about any update on this topic?
How can we help you guys?

[profnandaa]

We should do a release by end of next week. I'll just pick whatever will be ready by then; then the subsequent PRs can follow for the next release, scheduling for March 2023.

Any help on the reviews will still be appreciated.