none
Following Friday's API Update Debacle...

    General discussion

  • I've already contacted my customer service rep and suggest any enterprise customers contact their representative to write in demanding the following:

    1) Notification by e-mail that a change will occur, along with the date in which this change is scheduled to take place

    2) An explanation of what will change with the next release

    3) Ample time to test applications vs. the development url which will have the new code in place a reasonable amount of time beforehand

    I would follow these rules for code in use by the company that I work for and certainly should not expect less from Microsoft. These 'ninja' updates are simply unacceptable.


    Sasha dos Santos Software Engineer 3M Electronic Monitoring http://www.3M.com/electronicmonitoring

    Monday, March 12, 2012 1:26 PM

All replies

  • I just read another thread and would add:

    4) Updates should be released on a Monday if possible. A Friday update should be avoided, as a hotfix might not be available before the start of the weekend. And developers should be able to leave work knowing their sites are working

    (I left Friday not knowing what would happen and my company runs 24/7)


    Sasha dos Santos Software Engineer 3M Electronic Monitoring http://www.3M.com/electronicmonitoring

    Monday, March 12, 2012 1:35 PM
  • Many of the things you have mentioned in terms of improvements we are well aware of and are working on improving. I agree outages should be the last thing that should occur and there is room for improvement.

    In regards to number 4, from my experience as a consultant it was found that Thrusday and Friday releases were the prefered time by customers. Should an outages over a weekend they are less impactful than an outage during the week as web traffic is general tends to be 3 to 4 times more during the week.


    http://rbrundritt.wordpress.com

    Monday, March 12, 2012 2:51 PM
  • I, as well as many other developers, look forward to seeing these improvements with future releases of the API. Thank You.

    Sasha dos Santos Software Engineer 3M Electronic Monitoring http://www.3M.com/electronicmonitoring

    Monday, March 12, 2012 3:43 PM