function readOnly(count){ }
Starting November 20, the site will be set to read-only. On December 4, 2023,
forum discussions will move to the Trailblazer Community.
+ Start a Discussion
kent.chenkent.chen 

Asking for a best practice of development lifecycle (An organization as an ISV )

Hi,

  Our company will serve as an ISV.  

  We'll provide managed packages for our partners.

  However, the development of such packages should go through dev->qa->stage->prod processes.  The Dev team/QA team/Distribution Team are independent from each other.

 What's the best practice of the development lifecycle in this case?  Or, which books should I read?  

Best Answer chosen by Admin (Salesforce Developers) 
BoSoxFanBoSoxFan

Check out the link below which has some good content on "Team Development". The key in this process is to used DE Orgs and not Sandbox Orgs since only DE Org allow you to create a Managed Package.

 

 

1) Dev Team uses 1 or more DE Org to build the solution

2) Dev Team promotes releases to (1) Master DE

3) Master DE Org is where you create your Managed Package and new versions

4) Create a Managed Beta Package in the Master DE Org for testing purposes

5) QA team uses 1 or more test Orgs (e.g. EE, PE) and uses the install link from the Master DE Beta Managed Package to install the current solution

6) QA finishes and some creates a Managed Release version of the package in your Master DE for customers

 

Note: Don't forget about the Security Review

 

Hope that helps

 

 

http://wiki.developerforce.com/index.php/Introduction_to_Developing_Commercial_Apps_on_Force.com

All Answers

BoSoxFanBoSoxFan

Check out the link below which has some good content on "Team Development". The key in this process is to used DE Orgs and not Sandbox Orgs since only DE Org allow you to create a Managed Package.

 

 

1) Dev Team uses 1 or more DE Org to build the solution

2) Dev Team promotes releases to (1) Master DE

3) Master DE Org is where you create your Managed Package and new versions

4) Create a Managed Beta Package in the Master DE Org for testing purposes

5) QA team uses 1 or more test Orgs (e.g. EE, PE) and uses the install link from the Master DE Beta Managed Package to install the current solution

6) QA finishes and some creates a Managed Release version of the package in your Master DE for customers

 

Note: Don't forget about the Security Review

 

Hope that helps

 

 

http://wiki.developerforce.com/index.php/Introduction_to_Developing_Commercial_Apps_on_Force.com

This was selected as the best answer
kent.chenkent.chen

Thank you, BoSoxFan