You are not logged in. Your edit will be placed in a queue until it is peer reviewed.
We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.
Required fields*
-
7Many thanks for the summary. Could you maybe also comment on whether the extra time let you address more issues and/or more complex issues than two shorter sprints would have?– NoDataDumpNoContributionCommented Apr 21 at 17:17
-
1There is also the problem with the staging ground running empty on SO since quite some time. That is worrying. Maybe it has been forgotten?– NoDataDumpNoContributionCommented Apr 21 at 17:19
-
9It's a bit ironic that chat is not on the sidebar on MSE, and this post opens up with a mention of that feature...– TylerHCommented Apr 21 at 19:47
-
We've been talking about FRing that :D– Journeyman GeekCommented Apr 22 at 1:41
-
2meta.stackexchange.com/questions/408421/… done– Journeyman GeekCommented Apr 22 at 1:46
-
Any particular reason you are not implementing/planning either suggestion from this answer? It was the highest scoring answer (I know that that's not the only indicator for prioritizing but still) and the requests were mentioned in the previous sprint. The linked requests are not tagged status-declined either.– A-TechCommented Apr 22 at 8:30
-
1@NoDataDumpNoContribution re: more issues, we're about on the mark- this sprint saw 24 issues resolved; the 1st covered 15, and the 2nd covered 12, per their respective posts. re: complexity, to my subjective eval and to our internal marking of complexity, it looks about the same- that is, we covered proportionally more issues of about the same complexity as previous sprints, which makes sense. That said, I'm not sure of the complexity in terms of, say, dev effort per issue.– Frog StaffModCommented Apr 22 at 21:32
-
2@JourneymanGeek On the note of FRs- it would be super helpful if you and others went through the CAS requests and made posts for the ones that only ever made it to answers on those posts. It helps a ton with tracking requests– Frog StaffModCommented Apr 22 at 21:35
-
I see 3, one was mine (fixed) and I've punged the relevant users where possible.– Journeyman GeekCommented 2 days ago
-
I see. So two short sprints and one longer are largely equivalent. Approximately nothing gained, nothing lost.– NoDataDumpNoContributionCommented 2 days ago
Add a comment
|
How to Edit
- Correct minor typos or mistakes
- Clarify meaning without changing it
- Add related resources or links
- Always respect the author’s intent
- Don’t use edits to reply to the author
How to Format
-
create code fences with backticks ` or tildes ~
```
like so
``` -
add language identifier to highlight code
```python
def function(foo):
print(foo)
``` - put returns between paragraphs
- for linebreak add 2 spaces at end
- _italic_ or **bold**
- indent code by 4 spaces
- backtick escapes
`like _so_` - quote by placing > at start of line
- to make links (use https whenever possible)
<https://example.com>[example](https://example.com)<a href="https://example.com">example</a>
How to Tag
A tag is a keyword or label that categorizes your question with other, similar questions. Choose one or more (up to 5) tags that will help answerers to find and interpret your question.
- complete the sentence: my question is about...
- use tags that describe things or concepts that are essential, not incidental to your question
- favor using existing popular tags
- read the descriptions that appear below the tag
If your question is primarily about a topic for which you can't find a tag:
- combine multiple words into single-words with hyphens (e.g. stack-overflow), up to a maximum of 35 characters
- creating new tags is a privilege; if you can't yet create a tag you need, then post this question without it, then ask the community to create it for you