You need to sign in to do that
Don't have an account?
jeremyy
Maint. releases to v1 while v2 under development?
Hi,
I'm about to release v1 of a managed package. Once this package is in the wild, I'll need to make bug fixes and do maintenance releases. At the same time, I will be building v2 in a separate code base / branch.
I initially thought package extensions might be a way to accomplish this, but there are some issues:
- If customer wants v2, they must install v1 first. This gets worse as new major releases are completed.
- The DE org(s) for major releases after v1 would each create a new namespace prefix.
It looks like a Patch Organizization (ch. 8 of Developing Packages for Distribution) would be the best tool for this problem. Can anyone with some experience with Patch Orgs confirm this? Any additional advice or opinions are welcome and appreciated.
Jeremy
Patch orgs are the way to go. Log a case in the partner portal to get this feature enabled for you.
There are a number of limitations with Patch org. (Stated Below)
The way I would suggest is: Create Multiple Orgs.
Can someone comment on this:
http://boards.developerforce.com/t5/Apex-Code-Development/Pushing-Managed-Package-Upgrades/td-p/348313