1. 1 Yikes.. PATCHES! Big freakin topic, Need to organize efforts Concerned about tangents and progress Short Term and Long Term Making Progress

2. 2 Short Term Current Process (next slide) Don’t worry about what a patch is, other than a set of files with information about how to install. Must Organize them –patch repository WEBDAV? SupportForce? –categorize them in salesforce. Add “Solution” or “Patch” Categorize Patch (Product, Version, Type) Add link to real patch ( we might add gui within salesforce, no second gui) Add notes about how to install. Patch because of CASE –If it was because of a case, go to that case and link solution/patch. –If patch is specific to customer and not for the world, only make it available within a case. Should rarely be the case. When a “patch” –Anything that is an update to a stable/supported release. –From a case –Developer retrofits optimization backwards. Need to encourage some of this What a “package” –Service Pack, Release, Patch –They all need to be made avialable through the network Ant TASK to take “BUILD(tar/zip)” and push to patch repository.

3. 3 Closing Action Development Opening Action Customer Community Somebody BUILDS it Find Defect! Opens Case Post on Forum Opens JIRA Issue Developer writes code for solution Code checked into CVS on a branch Somebody pulls the changed files and zips into patch Adds File/Notes To Case Closes Case Developer Responds On Forum Notes entered in JIRA Code added to tip of major Get’s built in a minor release build Developer Code added to tip of major Get’s built in a minor release build Actor L/M/H Decision Point

4. 4 Find Defect Optimizations Code Enhancement WRITE/TEST And CHECK-IN CODE BUILD TEST CODE PROMOTE JBNet Repository SourceForge Short Form for updated Process Community Release?

5. 5 Short Term Items Create Package Repository – Frank/Eric PROMOTE TASK (Ryan?/Rich) –push build to repository –Create item in salesforce Add PATCH to salesforce (Frank/Rich) Categorization Scheme to represent in salesforce (Ivelin?) Support Process Doc (Rich/Luc)

6. 6 Long Term Build System –Build –Types of Builds –Package –Types of packages –Promote –Types of promotion Package Repository –Files –Metadata –Integration with Salesforce –How to exposte to customers Getting JBN packages –Portal, Admin Server, Command Line Unpack and Deploy –Reading a server (managing conflicts) –Moving files –Unwrapping and restart –Hot Unpacking for JBoss AS –How to support release, servicepack, patch –Order of preference –System jars vs /server directories What is a PATCH –Two Options Mature – jar with updated classes laid down Open – A replacement for something that exists What is a PACKAGE –RPM with only JAVA Commands. –JRPM Related – Dependency representation in the formats

7. 7 CVS Developer Release Patch Service Pack sourceforge Package Release Package Patch Package Service Pack Public build Private build Private Package Standard Package Release Public package Private Promote JBN Repository Salesforce jpackage Public promote

8. 8 JBN Repository Salesforce network Customer Portal Command Line Admin Server SOAP Person Some Machine Local Repository

9. 9 NodeMgr Command Line Admin Server Some Machine Local Repository SYSTEM(S) JBoss /xx/patch /xx/servicepack /xx/lib /xx/deploy /xx/conf

10. 10 Long Term Items What is a release/servicepack/patch What is a package BuildSystem - Build/Package/Promote Package Repository Portal, SOAP Integration Admin Server, Command Line Unpackage/Deploy Application Server

11. 11 Making Progress Will manage tasks within JIRA – JBN. Link to related tasks. Weekly meeting Proposal for Architecture Council – When? Short Term Changes Review to Dev and Support – When?