FYI: The production SDS is running at svn rev 478
We will be upgrading to rev 511 You can see a summary of the changes here: http://trac.cosmos.concord.org/sds/timeline?from=02%2F19%2F2009&daysback=120&changeset=on&update=Update >From: Aaron Unger <[email protected]> >To: [email protected] >Subject: Production SDS upgrade tonight >Date: Thu, 19 Feb 2009 10:05:44 -0500 >Cc: Daniel Damelin <[email protected]>, Carolyn Staudt ><[email protected]> >Reply-To: [email protected] >Sender: [email protected] >List-Id: <cc-developers.googlegroups.com> > > >I've reviewed all of the changes to the SDS which would get moved to >the production SDS if it were updated to the current code, and almost >all of the changes revolve around the new functionality I've created >for RI-ITEST (on-the-fly workgroups and user data syncing). It's been >running well in staging, and Alex has done some testing on the new >code to make sure it's working like expected. > >I'd like to upgrade the SDS tonight at 10pm, if there are no >objections. It involves 5-10 minutes of downtime (probably less) >during which no projects will be able to launch activities. > >Dan, I'll also update the RI-ITEST DIY at the same time. > >On a dev level: >I'd also like to branch the SDS code to create a "stable" branch, and >then point the production SDS to the "stable" branch. It will 1) force >us to be more deliberate about pushing changes into production >(protecting against an accidental 'cap production deploy' with >untested code) and 2) allow us to more easily push changes to >production out of sequence (useful if we need to quickly deploy a bug >fix). > >The new development paradigm for the SDS would be: > - do all development work on trunk > - deploy those changes to the staging SDS and test > - when ready and tested, merge changes into the stable branch > - deploy stable to the production SDS, as needed > >The developer would be responsible for making sure all of their work >on trunk gets merged to stable once ready and tested. The work can >then sit in stable until there's an opportune time to update the >production SDS, but trunk and stable should never diverge very far >apart. No new code should get checked in to stable directly, if at all >possible. > >Thoughts? Comments? Alterations? Let me know- > >-- Aaron > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "SAIL-Dev" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/SAIL-Dev?hl=en -~----------~----~----~----~------~----~------~--~---
