5 replaced http://cooking.stackexchange.com/ with https://cooking.stackexchange.com/
source | link

I'm going to call this a bug, pending confirmation or explanation from the dev team.

If you check the historyhistory you will see the following text:

Bounty Ended with no winning answer

The timestamp on this event is 2011-08-30 17:37. The bounty was started on 2011-08-24 18:03:36. That's actually less than 6 days and bounties should expire after 7 days.

If it does turn out to be a bug then we can refund it (I'd like to make sure first).

Update: As per Sam's comment, it was a bug.

I'm going to call this a bug, pending confirmation or explanation from the dev team.

If you check the history you will see the following text:

Bounty Ended with no winning answer

The timestamp on this event is 2011-08-30 17:37. The bounty was started on 2011-08-24 18:03:36. That's actually less than 6 days and bounties should expire after 7 days.

If it does turn out to be a bug then we can refund it (I'd like to make sure first).

Update: As per Sam's comment, it was a bug.

I'm going to call this a bug, pending confirmation or explanation from the dev team.

If you check the history you will see the following text:

Bounty Ended with no winning answer

The timestamp on this event is 2011-08-30 17:37. The bounty was started on 2011-08-24 18:03:36. That's actually less than 6 days and bounties should expire after 7 days.

If it does turn out to be a bug then we can refund it (I'd like to make sure first).

Update: As per Sam's comment, it was a bug.

4 replaced http://meta.stackexchange.com/ with https://meta.stackexchange.com/
source | link

I'm going to call this a bug, pending confirmation or explanation from the dev team.

If you check the history you will see the following text:

Bounty Ended with no winning answer

The timestamp on this event is 2011-08-30 17:37. The bounty was started on 2011-08-24 18:03:36. That's actually less than 6 days and bounties should expire after 7 days.

If it does turn out to be a bug then we can refund it (I'd like to make sure first).

Update: As per Sam's comment, it was a bugit was a bug.

I'm going to call this a bug, pending confirmation or explanation from the dev team.

If you check the history you will see the following text:

Bounty Ended with no winning answer

The timestamp on this event is 2011-08-30 17:37. The bounty was started on 2011-08-24 18:03:36. That's actually less than 6 days and bounties should expire after 7 days.

If it does turn out to be a bug then we can refund it (I'd like to make sure first).

Update: As per Sam's comment, it was a bug.

I'm going to call this a bug, pending confirmation or explanation from the dev team.

If you check the history you will see the following text:

Bounty Ended with no winning answer

The timestamp on this event is 2011-08-30 17:37. The bounty was started on 2011-08-24 18:03:36. That's actually less than 6 days and bounties should expire after 7 days.

If it does turn out to be a bug then we can refund it (I'd like to make sure first).

Update: As per Sam's comment, it was a bug.

3 Migration of MSO links to MSE links
source | link

I'm going to call this a bug, pending confirmation or explanation from the dev team.

If you check the history you will see the following text:

Bounty Ended with no winning answer

The timestamp on this event is 2011-08-30 17:37. The bounty was started on 2011-08-24 18:03:36. That's actually less than 6 days and bounties should expire after 7 days.

If it does turn out to be a bug then we can refund it (I'd like to make sure first).

Update: As per Sam's comment, it was a bugit was a bug.

I'm going to call this a bug, pending confirmation or explanation from the dev team.

If you check the history you will see the following text:

Bounty Ended with no winning answer

The timestamp on this event is 2011-08-30 17:37. The bounty was started on 2011-08-24 18:03:36. That's actually less than 6 days and bounties should expire after 7 days.

If it does turn out to be a bug then we can refund it (I'd like to make sure first).

Update: As per Sam's comment, it was a bug.

I'm going to call this a bug, pending confirmation or explanation from the dev team.

If you check the history you will see the following text:

Bounty Ended with no winning answer

The timestamp on this event is 2011-08-30 17:37. The bounty was started on 2011-08-24 18:03:36. That's actually less than 6 days and bounties should expire after 7 days.

If it does turn out to be a bug then we can refund it (I'd like to make sure first).

Update: As per Sam's comment, it was a bug.

2 added 158 characters in body
source | link
1
source | link