I totally understand the need for maintenance. And I totally understand working on a tight budget. And I totally understand things taking longer than expected. I work in IT, and totally hate having to work on servers, and especially production servers with the pressure of knowing there are people waiting for them to come back up.
What I'm not too happy about is that the last two outages have not been announced accurately. Plus, it would be better for us users if you could "under-promise and overdeliver", rather than the other way around. For this one, instead of saying "intermittent outages Friday and Saturday", it would have been better to let us know you were doing some "major" systems work, and that BGG would likely be down "most of Friday and Saturday". Then, if it happened to only take a few hours, we would all be thrilled and praising you for working so quickly. To me, "intermittent" sounded like it might be down a few minutes at a time, or maybe a couple hours here, and a couple hours there. In the previous outage, you referred to it as "scheduled maintenance", but since it was only scheduled less than a day in advance, that's not the term I would have used. I would have referred to it as "emergency maintenance" or "necessary repairs". So, in the future please: 1. Let us know in advance the scope of the work being done 2. Overestimate how long it will take, and hopefully come back earlier than expected 3. Fix the subscriptions bug so I actually get notified of outages in advance Thanks, Kevin On Mar 22, 6:35 am, Scott Alden <[email protected]> wrote: > It obviously took a lot longer to get what we wanted working... I > blame Sackson (the server... not the man). -- You received this message because you are subscribed to the Google Groups "BGG Down" 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/bgg_down?hl=en.
