Changes between Initial Version and Version 1 of Ticket #764, comment 20


Ignore:
Timestamp:
07/29/14 08:56:34 (2 years ago)
Author:
annesley
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #764, comment 20

    initial v1  
    1313i expect and hope that we will be moving towards a much larger, complex multi-faceted and popular web offering over the next 5 years and so i would like to start a more controlled attitude to updates to the live system. anything *Drupal* updates that are not needed immediately by us can go in to dev and move up to live after a full testing run. and, since we are de-commissioning live we have no need to apply un-necessary Drupal updates to it currently i would suggest. 
    1414 
    15 @Paul: thanks for the insight to the manual application of Unix updates. i understand the reasoning for this and understand the points about the importance of Unix updates. let's explore the possibility of automatic updates more though. how about a cron once a week on Tuesday morning on the staging server, and on wednesday morning on live. this would give us a day to check for failures on staging. i could do a 10 minute run around the staging site each Tuesday morning until we have a rig setup. 
     15thanks for the insight to the manual application of Unix updates. i understand the reasoning for this and understand the points about the importance of Unix updates. let's explore the possibility of automatic updates more though. how about a cron once a week on Tuesday morning on the staging server, and on wednesday morning on live. this would give us a day to check for failures on staging. i could do a 10 minute run around the staging site each Tuesday morning until we have a rig setup. 
    1616 
    1717WDYT about these points?