Timeline for Second-Generation Managed Package Security Review
Current License: CC BY-SA 4.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 13, 2019 at 14:21 | comment | added | BritishBoyinDC | Also, if you aren't already using it, the ISV Falcon Template makes DX work much better with 1GP: github.com/sfdx-isv/sfdx-falcon-template | |
| Jun 13, 2019 at 13:33 | comment | added | sfdcfox | @OleksandrBerehovskyi P.S. you can still install the 2GP in to the dev org that contains the managed 1GP instead of moving metadata "manually," so the new feature isn't completely useless. | |
| Jun 13, 2019 at 13:17 | vote | accept | Oleksandr Berehovskyi | ||
| Jun 13, 2019 at 12:20 | comment | added | Keith C | @OleksandrBerehovskyi Yes. But you will need the 1st generation package to go live per the above statement anyway. At least the sfdx tools are quite good now for converting formats. A colleague expressed the opinion that 2nd generation will be GA around the end of the year, but don't know what that opinion is based on. | |
| Jun 13, 2019 at 12:17 | comment | added | Oleksandr Berehovskyi | so I need to create brand new dev org, push metadata to that org, create 1-st generation package, link this org to partner org and then send to security review, am I correct? | |
| Jun 13, 2019 at 12:14 | history | answered | Keith C | CC BY-SA 4.0 |