Environment Hub developer edition differences

I’ve noticed Developer Edition orgs aren’t as homogenous as expected. One source of variation is what template they come from. For ISV partners, the options are bifurcated from the very start:

  1. Developer Edition from developer.force.com (I refer to these as “Vanilla Developer Edition”)
  2. Partner Developer Edition from Partner Portal
  3. Developer Edition from Environment Hub (Organization Type: Release)
  4. Developer Edition from Environment Hub (Organization Type: Test)
  5. Developer Edition from Environment Hub (Organization Type: Partner)

Until Environment Hub came along, I thought 2 was the best source of truth. But now I’m not even sure that 3 is best bet as I can’t deploy Permission Sets containing ManageCssUsers now.

Would the real slim shady please stand up? Which org is best for packages? And which for playing?

environment-hub-one

environment-hub-two

Answer

Woohoo! The Winter ’15 release has brought some changes to Environment Hub that clarify this:

The Create Organization dialogue now has a Purpose field:

purpose

For ‘Development’ purpose there is only one option and this is our guy!

  • Partner Developer

development

Use a partner development organization to build, package and upload your app. Partner organizations have higher limits and other advanced features and are only available to partners. They are strictly for internal use and should not be shared with customers or prospects.

For ‘Test/Demo’ purpose (these guys are nuked after 30 days):

  • Partner Enterprise
  • Partner Professional
  • Partner Group
  • Consulting
  • Enterprise Edition
  • Professional Edition
  • Group Edition
  • Create using Trialforce Template ID

(Mostly documented here in Partner Development & Test Environments)

test/demo

Use a partner test/demo organization for testing your app’s compatibility with various editions or to demo your app to prospects. Partner organizations have higher limits and other advanced features and are only available to partners. They are strictly for internal use and should not be shared with customers or prospects.

For ‘Trialforce’ purpose (these are template orgs that stick around):

  • Enterprise Edition
  • Professional Edition

trialforce

Use a Trialforce Source Organization (TSO) for creating templates for trial organizations. Trialforce branding is not supported for TSOs you create from here. If you plan to use custom branding for your trials, create the TSO from a Trialforce Management Organization instead.

Attribution
Source : Link , Question Author : Matt and Neil , Answer Author : Community

Leave a Comment