Version-16 branch

[marcramser]

Are you planning to create a version-16 branch for Frappe v16 support?

Also, any plans to start using release tags as suggested in #140?
That would make it much easier to pin stable versions.

[ed3899]

Looping back in for attention, same question as @marcramser

[BetterLuke]

Yes, we need version-16 branch to support lms integrate erpnextv16. Any update fot this issue?

[casesolved-co-uk]

Yes please, also see frappe/webshop#356

[SYSINFRACH]

Hi all, adding some concrete context from real v16 testing.

We opened two Stripe related issues that we hit while testing the official payments app in a Frappe/ERPNext v16 setup:

• Stripe: finalize_request() appends redirect_to=None to success URL, causing broken redirect and invalid docname parsing #203
• Payment Request lacks on_payment_authorized() handler for Stripe success flow, causing successful Stripe payments to remain in Requested state #204

Both are not cosmetic. They affect the actual payment completion flow and accounting consistency:

1. Stripe redirect handling can append redirect_to=None, which breaks the success flow.
2. A successful Stripe payment for Payment Request can complete on Stripe, while ERPNext still leaves the request open until patched manually.

This is exactly why a dedicated version-16 branch and proper release tags would be very valuable. Right now, it is difficult to know what commit is considered stable for production use on v16, especially for payment related functionality where regressions are serious.

Please take these issues into account in the discussion around:

• a version-16 branch
• tagged releases for stable pinning
• clearer support expectations for v16 users