5

How do I determine when the "next deploy" will happen?

This is more of a general question than asking for literally the next deploy-date.

It came up because of this question: JavaScript error preventing vote-to-close dialog closing

In which the answer says the problem will be fixed "in the next deploy"... but there's no indication of when that would be or how one would go about finding out. The FAQ is silent on the topic, and a search on the phrase "next deploy" also turns up nothing of obvious interest:

https://meta.stackoverflow.com/search?q=next+deploy&submit=search

Am I missing something obvious to others? is there a way to find out when the deploys happen?

Improve this question
7
  • 1
    I guess they happen when they happen, when things are done. Commented Nov 28, 2011 at 23:12
  • 2
    Probably... but if somebody gives "next deploy" as an answer... it'd be nice to know when that is. Is there a changelog? Commented Nov 28, 2011 at 23:13
  • 3
    If someone gives "next deploy" as an answer, it means the change will most likely be visible within a few hours or days. I guess making a more detailed estimate is most often impossible - having to publicly state ETAs for every little job they're doing would drive people crazy. But I assume you are asking about seeing when a deploy has happened after the fact? Commented Nov 28, 2011 at 23:17
  • 1
    Ah - but I was unaware that the deploys were multiple times a day when I asked. If the deploys were, say, once a week/fortnight/month - then posting deploy-info might actually make sense... Commented Nov 28, 2011 at 23:19
  • 1
    ah, fair enough. Commented Nov 28, 2011 at 23:19
  • 3
    in b4 "six to eight weeks" Commented Nov 28, 2011 at 23:34
  • It's not uncommon for multiple deploys to roll out each day. Most of the time it's seamless and the only thing noticeable is the version footer changing. Somtimes the sites may go offline but they're back up quick after. Commented Nov 29, 2011 at 8:37

1 Answer 1

Reset to default
8

There are usually several deploys a day. Here's how to find out if a new one is happened:

  • Look in the footer where it says rev yyyy.mm.dd.nn
  • The year, month, and day are in UTC. The nn refers to the deploy that day. Write that number down or memorize it.
  • Come back in a few hours. Has the number changed? If so, a new deploy has happened. If not, wait a few more hours and repeat this step.

So the issue you mentioned should be resolved by now. If it's still happening for you, and no one replies to your comment, it might be worth it to raise a new bug.

Improve this answer
6
  • it won't be considered a duplicate? Commented Nov 28, 2011 at 23:16
  • 2
    @TarynEast Given that (as far as I can tell) it's on a different page and the original bug was fixed, probably not. Commented Nov 28, 2011 at 23:17
  • 1
    Here's a link to the pod cast where they mention their deployment process blog.stackoverflow.com/2011/10/se-podcast-24 Commented Nov 28, 2011 at 23:25
  • hmmm Heisenbug... now that I go to see if I can get a copy of the error message in the console, the problem has disappeared. I swear it was a bug only thirty minutes ago! :P Commented Nov 28, 2011 at 23:26
  • @waiwai933 I opened a question about a bug that was already reported in another question that is marked as "status-complete"; the bug is still present, but my question has been closed as duplicate. Commented Nov 28, 2011 at 23:31
  • Welp - can't seem to reproduce it anymore... maybe a deploy happened in the meantime ;) Commented Nov 28, 2011 at 23:32

You must log in to answer this question.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.