How to contribute to 9.13.x ?

[adlzanchetta-trilogy]

Hi there. First-time contributor here.
I would like to contribute to the codebase of an eventual 9.13.10 version (with some code that should be also compatible with 10.0.x).
I understand that I should create a branch in my personal fork out of release/9.13.9, but, assuming develop holds the code for 10.0.x, then to which branch should I submit my PR? Back to release/9.13.9?

[bdukes]

We are not yet committed to producing a 9.13.10 release. However, if we were to do so, submitting a PR to release/9.13.9 is probably the best approach. Ideally, you could submit a PR to develop and we could cherry-pick it into a release/9.13.10 if we decide to do another 9.x release. Hope that helps!

[valadas]

It kind of also depends on what kind of contribution it would be. If it is a security one, it need to be reported by creating a security issue so it can be done on a private fork and then we will see about merging into which versions.
For a new feature/enhancement, generally speaking that would be in v10 only.
For bug fixes it kinda depends how easy/hard it is to take on both versions, but I would target develop because it is sure to make it into v10 but unsure to make it into v9...

[adlzanchetta-trilogy]

Thank you for the clarification, @valadas. I see that you already approved and redirected to PR #6531 to the develop branch. Great to see that there was no conflicts. :-D

[mitchelsellers]

As others have mentioned, I strongly feel that we will NOT be making additional 9.13.x releases, it would need to be pretty compelling I believe, so I would follow Brian's suggestion of targeting develop just like normal.

Feel free to reach out to me directly as well, I've been trying to talk to your management for months about the release cycle and they ignore us.

[adlzanchetta-trilogy]

Thanks for the openness to talk, @mitchelsellers . Sure, I would be more than happy to help with the communication. I got into my current position dealing with DNN one week ago and I am still learning how the things go. Sending an email to the address that you make public in your Github account in the next minutes...
(please also let me know if you prefer any other communication tool).