Timeline for Improving SFDC release management
Current License: CC BY-SA 3.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Sep 1, 2015 at 9:43 | answer | added | Jason M | timeline score: 2 | |
| Aug 31, 2015 at 15:42 | answer | added | Niranjan | timeline score: 0 | |
| Oct 3, 2014 at 21:26 | answer | added | MeighanRocksSF | timeline score: 5 | |
| Nov 6, 2013 at 10:59 | comment | added | Samuel De Rycke | Can you update your question (edit?) That'll be more readable and easier to answer. | |
| Nov 6, 2013 at 9:47 | comment | added | Ghary | want to know how we can improve the SFDC release process. What r best practices to achieve seamless process where we hav dployments going to prod every 20-30 mins for small changes. Currently the challenge here might not be technical but also from operational level. So want to know if there is any best process people follow in their organization. To be more specific: 1)our deployments to prod are taking too long, sometimes it even runs for whole day. 2)Is there any better way developer can keep track of changes manually fr the components which are not available in API? concerns like this... | |
| Nov 6, 2013 at 7:22 | comment | added | Samuel De Rycke | Welcome to salesforce.stackexchange Ghary. We aim to provide good answers, which is usually only possible to subject specific questions. There are many ways to do release management and organise development, so this will be highly subjective and may not lead to any "true" rewarding answers. Any chance you could rephrase your question to be more specific ? | |
| Nov 6, 2013 at 6:14 | review | First posts | |||
| Nov 6, 2013 at 7:22 | |||||
| Nov 6, 2013 at 5:59 | history | asked | Ghary | CC BY-SA 3.0 |