Salesforce IdeaExchange
Pre-release improvements
The current pre-release process is broken in a few ways
1. No code freeze
The pre-release environment is very different from the eventual release. When we find a bug in pre-release, we're never certain if it's an artifact of pre-release or if it's actually a new bug.
Conversely - and much, much worse - things that work perfectly in pre-release suddenly break when the new release actually goes live because salesforce's developers are adding new features & new code long after pre-release is available.
2. Namespace changes
Changing the namespace of our code makes it much more difficult to actually develop or bugfix on pre-release. We would have to fork our existing code with the new namespace, and then eventually merge changes back into the mainline while being careful not to bring the mangled namespace back with.
3. Inability to test packaging
I want to be able to build a package in pre-release, upload it to a private AppExchange package, and then install it onto a separate org (maybe sandbox?) to test that entire cycle.
The Winter09 release in particular has shown just how important each of these items is, as many partners and ISVs have had to deal with a two week period of breakage since the release.
These past two weeks have entailed a lot of late nights for partners and for salesforce's own developers; this could have been avoided with a better pre-release process.
track comments for this idea
- michaellatideas
- axxxv
- gmp_process
- tmusantesforce
- KevinEdelmann
- jimson
- xpat
- arlon_wilber
- maksim
- ddkpe
- paul_weeden
- andreas_krebs
- benjamin
- TehNrd
- CKA
- Francesco23
- craskulinecz
- cic
- foster
- jeff333
- ad75
- jackjordan
- AlexCRMmanager
- tt
- Jakester
- JeanC
- RodbCA
- ejw
- TimAlsop
- dchasman
- jhart
POST IDEA