Timeline for We spent a sprint addressing your requests — here’s how it went
Current License: CC BY-SA 4.0
35 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| yesterday | comment | added | Mentalist | Just wanted to say: thank you! That's all. 😄 | |
| Jul 12 at 15:58 | history | edited | JNatStaffMod | CC BY-SA 4.0 |
added one more
|
| Jul 12 at 12:35 | answer | added | Kit | timeline score: 3 | |
| Jul 9 at 18:55 | comment | added | starball | @canon I've heard stories like any good reputation of the SO/SE platform translating to why devs suggest SOfT to their bosses. | |
| Jul 9 at 13:24 | comment | added | dan1st | @canon Just say it's marketing as having an angry Community is bad for marketing I guess. | |
| Jul 9 at 12:49 | comment | added | canon | This is great! It's awesome to see some concerted effort poured into this side of the house. That said, somebody better figure out how to describe these efforts as "providing shareholder value" or I suspect we'll never get them again. | |
| Jul 9 at 12:35 | comment | added | OrangeDog | This is good and all, but a hard commitment to spend more than a week each year on this would be nice. | |
| Jul 9 at 10:56 | history | edited | JNatStaffMod | CC BY-SA 4.0 |
added another one to the list
|
| Jul 8 at 9:46 | comment | added | JNat StaffMod | The list provided in the post already provides the list of completed items, @bta — like I mentioned in the post, it is the list of issues that are marked as "done" in our internal tracking systems. For that reason, though, some that might still be getting the last touches will be added once shipped to production. | |
| Jul 5 at 17:09 | comment | added | bta | Fixes aside, I particularly appreciate how y'all are documenting and communicating this work. Any chance we could (eventually) get a complete list of the completed requests from this sprint, analogous to the release notes for a piece of software? That would not only help highlight the work you have done, but would also give us additional information to help us write better bug reports. | |
| Jul 4 at 8:43 | history | edited | JNatStaffMod | CC BY-SA 4.0 |
minor clarifications about sprint cadence
|
| Jul 3 at 20:35 | answer | added | Shadow Wizard | timeline score: 12 | |
| Jul 3 at 12:51 | answer | added | David K | timeline score: 8 | |
| Jul 3 at 11:56 | history | edited | JNatStaffMod | CC BY-SA 4.0 |
added one more that just shipped
|
| Jul 2 at 14:41 | history | edited | JNatStaffMod |
Rollback to Revision 2; was already in the list
|
|
| Jul 2 at 14:22 | answer | added | Joachim | timeline score: 5 | |
| Jul 2 at 14:17 | history | edited | SashaStaffMod | CC BY-SA 4.0 |
added 128 characters in body
|
| Jul 1 at 19:27 | answer | added | starball | timeline score: 36 | |
| Jul 1 at 19:17 | history | edited | SashaStaffMod | CC BY-SA 4.0 |
added 125 characters in body
|
| Jul 1 at 17:27 | answer | added | TylerH | timeline score: 66 | |
| Jul 1 at 16:32 | comment | added | JNat StaffMod | @gbianchi sorry for the delay! I'll reach out this week to get that sorted for you ^_^ | |
| Jul 1 at 14:57 | answer | added | Mithical | timeline score: 137 | |
| Jul 1 at 14:49 | answer | added | Journeyman Geek | timeline score: 13 | |
| Jul 1 at 14:41 | comment | added | gbianchi | What about status review on other sites?? on SO esp we ask for the IA banner 5 months ago.. and still we have no reply about it... | |
| Jul 1 at 14:15 | answer | added | curiousdannii | timeline score: -13 | |
| Jul 1 at 14:05 | comment | added | Makyen | @ShadowWizard Network policy is that bugs can be reported on any meta site. While it's probably reasonable to migrate in some limited circumstances (e.g., if the bug affects a single site which isn't the the site on which they were reported), that's not the case for bugs which are generally applicable to multiple sites. Yes, that means that bug reports are somewhat fragmented and that watching at least MSE and MSO is really required, due to the volume on both sites. But, no, we don't intend to generally migrate bug reports from MSO to MSE until and unless that network policy changes. | |
| Jul 1 at 13:59 | comment | added | Journeyman Geek | Also - I think the more informal style 'fits' meta culture better. Good meta is somewhat informal - and the title feels like it tells the story. As somewhat of an active user on meta, I think its fine | |
| Jul 1 at 13:53 | review | Close votes | |||
| Jul 1 at 16:10 | |||||
| Jul 1 at 13:39 | comment | added | Journeyman Geek | Its a little late to announce it no? | |
| Jul 1 at 13:35 | comment | added | Dan Mašek | I was wondering about a better title for this post, but then realized that this really should be two posts. For one, you're (belatedly) announcing the "Community Asks Sprint" initiative, and at the same time you're reporting results of the first such sprint. Then you'd have "New CAS initiative" and "Results of first CAS" instead of.. (dunno, something irks me about that style of headline). | |
| Jul 1 at 13:16 | comment | added | Journeyman Geek | if they're old enough, can't be migrated anyway :D | |
| Jul 1 at 13:12 | comment | added | Shadow Wizard | Well then, guess I better start a request/discussion on MSO asking the mods to migrate here bug reports and/or feature requests which are cross network. Anyway, thanks. | |
| Jul 1 at 13:09 | comment | added | JNat StaffMod | Because the initiative is not restricted to SO work — it just so happened that in this iteration a good chunk of the posts we addressed were there. | |
| Jul 1 at 13:08 | comment | added | Shadow Wizard | Most of the mentioned examples are in MSO and I've never knew they existed until seeing bug reports about the changes posted here (e.g. suddenly users could close questions with a bounty, the auto comment for dupe closure changed out of the blue, etc.) . I'm curious why posting this announcement here, and not in MSO? (It's awesome, I'm just not used for good things here.) | |
| Jul 1 at 12:39 | history | asked | JNatStaffMod | CC BY-SA 4.0 |