GitHub issues gets more and more capable... \o/https://github.com/blog/2206-reorder-issues-within-a-milestone …
-
-
I think they work best as goals rather than releases, a milestone is longer incremental changes, not reaching v2.7
2 replies 0 retweets 0 likes -
Replying to @jamiebuilds @wycats and
I think most OSS people use them for versions, which just ends up getting abandoned
1 reply 0 retweets 0 likes -
Replying to @jamiebuilds @thejameskyle and
I've used them for planning major releases pretty successfully. Not minor or patch.
1 reply 0 retweets 2 likes -
interesting -- I more or less assume a 6-week-cycle, which makes sticking features in a bucket uninteresting
1 reply 0 retweets 0 likes -
seems like it would be even better for that.
1 reply 0 retweets 0 likes -
a way to denote which features you're planning to work on this six week cycle
1 reply 0 retweets 0 likes -
ah but 6-week-releases assume "whatever's ready", no?
1 reply 0 retweets 0 likes -
seems good to still plan and estimate IMO. But I haven't done too much of that in open source
1 reply 0 retweets 1 like
I have given up trying to control the chaos long ago. Feature flag, ship when ready, 6-week cadence ftw
-
-
how do you disconnect feature request from delivery expectation, unless you're your own client?
0 replies 0 retweets 0 likesThanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.