Timeline for Managed Package Upgrade Strategy for Beta Versions or Promote Version
Current License: CC BY-SA 4.0
16 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Oct 30, 2023 at 12:26 | history | edited | Phil W | CC BY-SA 4.0 | How we work (summary) |
| Oct 30, 2023 at 11:54 | comment | added | vctqs1 | oohh create new development org per Jira issue kept it 2 weeks as a sprint sound like interesting for me. Do you have any specific reason or advances behind that why u decided to do that? | |
| Oct 30, 2023 at 11:10 | comment | added | Phil W | We always use scratch orgs for all package development and testing - there's no worry about whether the package is beta or not that way. For our "development orgs" - we have one per work item (we use Jira, so we have one per dev per Jira issue) - we use namespaced scratch orgs that are typically kept for 2 weeks (length of a sprint), and our "staging environments" are namespaced scratch orgs per work item created by QA (or PM, in principle). For regression testing, QA creates no-namespaced scratch orgs and install the (beta) package. We have test and demo data tooling. | |
| Oct 30, 2023 at 10:26 | comment | added | vctqs1 | with mine, development org is a place will be deployed if having any PR merged for developer testing staging environment like place PM and QA go there to do some demo and explore the features | |
| Oct 30, 2023 at 10:25 | comment | added | vctqs1 | Ohmm, so what do you do to handle your development workflow with 2GP package in development environment and staging environment. | |
| Oct 30, 2023 at 10:25 | comment | added | vctqs1 | Ohm I see, thank you | |
| Oct 30, 2023 at 7:13 | comment | added | Phil W | Yeah, it's quite confusing. And then to find a known issue - just makes packages harder to handle... | |
| Oct 30, 2023 at 3:04 | comment | added | vctqs1 | salesforce.stackexchange.com/questions/412458/… | |
| Oct 30, 2023 at 3:03 | comment | added | vctqs1 | salesforce.stackexchange.com/questions/317448/… I found your issue here, I also meet that, but just one small issue. even with create major version with ancestorId setted, this also found issue with package validation like u | |
| Oct 30, 2023 at 2:44 | comment | added | vctqs1 | ohmm, but my app have not distributed in AppExchange yet, we still need to contact Salesforce Support to do that? | |
| Oct 28, 2023 at 19:03 | comment | added | Phil W | And yes, patching is enabled by Salesforce Support and you do this through a case. But only after passing security review. | |
| Oct 28, 2023 at 19:02 | comment | added | Phil W | Yes, patches are also created as betas that must be promoted (2GP). | |
| Oct 28, 2023 at 18:16 | comment | added | vctqs1 | Patch versions can be treated identically, using betas initially and subsequently promoting the fix version. so it mean with patch version, we still need to do something like sf package version promote, is it? | |
| Oct 28, 2023 at 18:15 | comment | added | vctqs1 | NB: Patching 2GPs requires the package to have passed security review, since Salesforce Support will only enable this capability once it has been through that review process. So this mean we can not do patch update unless we contact Salesforce support to enable, is it? | |
| Oct 26, 2023 at 7:48 | history | edited | Phil W | CC BY-SA 4.0 | mention patching |
| Oct 26, 2023 at 7:37 | history | answered | Phil W | CC BY-SA 4.0 |