function readOnly(count){ }
Sign Up ›
Starting November 20, the site will be set to read-only. On December 4, 2023,
forum discussions will move to the Trailblazer Community.
Learn More

Browse by Topic
ShowAll Questionssorted byDate Posted
+ Start a Discussion
dfcdfc 

Supporting Patch and Major Releases in one DE

The fact that a given managed package can be owned and developed in one and only one DE has many side effects that make it different from typical custom software development.  Can you help me with this one?

 

 

(1) A managed package is developed and released from a DE instance with a namespace.  There are many classes and custom objects, so the namespace is highly embedded in code and meta-data.

 

(2) After release 1.0 of the managed package is uploaded to the AppExchange, work begins on release 2.0 in the same DE instance.  Assume that Eclipse IDE and SVN are used to archive and source manage all code versions.

 

(3) Many changes are made while 2.0 development is in progress.  New fields are added to custom objects, for example.  It is not complete, however, when...

 

(4) Suddenly, an emergency patch release (1.1) is needed, for the 1.0 release has a major bug that is just discovered that affects several Apex classes and custom objects.

 

(5) Here's the question:  The DE instance is loaded with in-progress release 2.0 work.  The SVN repository has a snapshot of the code as of release 1.0, but it cannot overwrite the ongoing 2.0 work in progress in the DE instance, right?  How can you produce a 1.1 patch without seriously screwing up your DE instance that contains release 2.0 work in progress?!

 

Thanks!

 

Dave

 

aztockaztock

Dave,

 

Consider using 2 development environments. PDE-1 for Development/QC, and PDE-2 for Official Release Version.

 

  • Develope / Test in PDE-1
  • When done move to PDE-2
  • Package and release from PDE-2
  • Continue working on Release V2 in PDE-1
  • Use PDE-2 to keep Official Release and for Support.

 

When urgent patch required, you will have to apply fixes in both environments:

  1. Update PDE-1
  2. Update PDE-2
  3. Package PDE-2 a minor version release from PDE-2
    1. The minor patch release becomes the official release
    2. Make sure to maintain the minor patch release version in SVN.

When Release 2 is ready you, repeat the steps, move PDE-1 code to PDE-2, package, rlease.

Both are in sync again.