Problem/Motivation
Preparing a new release of the DataTables module
Steps to reproduce
No need
Proposed resolution
Get together all the needed issues and update the DataTables module.
Remaining tasks
None
User interface changes
None
API changes
None
Data model changes
None
Comments
Comment #2
dqd@just-me: thanks for chiming in the project to help on further development, which is always appreciated since we maintainers have often limited time to be up-to-date on all issue queues. But can you please try to publicly report more details on your ideas, plans, thoughts and maybe about the invitation and conversations you maybe had with other maintainers which have added you to the project, to orchestrate it all more with all maintainers? Especially in case of plans for new releases and version ideas, this is really required to merge forces and to prevent users run in circles. Otherwise hard work of others could be accidently overlapping or wasted.
Example of unclarified issues: The project release states "Major Update: Vanilla JS & DataTables 2.x" but the CDN function states 1.10. - The 1.10.xx version of the library contains deprecated methods that no longer work with jQuery 4, which is what D11 core uses and the statement "vanilla JS" is confusing for users because DataTables 2.x also requires jQuery as can be read here and here. And there are several other issues to clear off before starting a new release. Especially this snapshot you provided is far too early state to be a Beta version, atm.
This is why I will disable the release for that moment until you had time to come back here with more info to prevent users getting messed up with update notifications in their projects.
Again, all help is much appreciated but needs more orchestration with other maintainers. Your work is very welcome but please try to follow some conversation and report logging standards in projects based on community efforts. Thanks for understanding my concerns.
Comment #3
dqdOpen up assignments for others to feel encouraged to chime in.
Comment #4
dqdI would actually only recommend a new Drupal module main release version in case of completely new features on Drupal module's side or on a complete refactoring already there to be testable. But not for a library update and some changed code for its implementation, which would perfectly fit into a new sub version of 2.x. From what I read on DataTables dev side the version changes are not really huge and there is already a Beta v3 up and running which we can consider for a new release then later.
Comment #5
liam morlandIf you don't want to move to a new major version, I suggest that you merge 3.x into 2.x now and then continue development on 2.x. When it is time for 3.x, merge 3.x with 2.x (it will be a fast-forward merge) and continue development. When it comes time for a release candidate, use 3.0.0-rc2.
Comment #6
dqdThanks Liam, I know how to deal with releases. As I explained in comment #2: there is/was some mess going on in a newly created 3.x branch based on not orchestrated assumptions regarding jQuery, which need clarification with others, that's is why it is stalling for that moment. I would not recommend to merge this confusion back into 2.x.
Comment #7
just-me commented@dqd, totally agree with you. Thank you for all your explanations and instructions. My bad.
I'll return here as soon as I can to resolve and update all your comments(in other issues).