Migrate Milestones to be theme-based

[rnystrom]

Instead of just bundling a bunch of stuff into a release, I want to move towards packaging relevant stuff into a single release. I'm trying to do this w/ 1.18 to make it about PRs (reply to comments and merging, would have loved to get reviews but that's for later).

Maybe we can reorganize milestones based on bundles of stuff and then prioritize them, working on features serially so we can release updates that have a theme.

Some seed ideas:

• Repositories
  • Star button + count
  • Unsubscribe
  • Milestone, label management
  • Better filters for issue/PR
• Search
  • Search ppl
  • Search issues
  • Hashtag autocomplete
• People
  • Native people VC
  • Profile tab
• Polish
  • Custom refresh control + animation
  • UI enhancements
• Performance
  • Optimize memory
  • Scroll performance boosts
• Automation
  • Canned replies
  • Workflow integration?
  • More "speed up" ideas
• etc etc

[BasThomas]

Love it. Makes it also easier to get used to new features, instead of new things all over the place that don't get noticed because of it. Would also make more sense to with versioning like 2.0, 2.1, 2.2, 3.0 etc., instead of being "stuck" at 1.whatever.

Plus it should be easier to market!

[rnystrom]

I've been holding off on a big 2.0 to collect a bunch of cool features and then push on Hacker News, Product Hunt, etc. I really wanted to get a profile tab in there for 2.0.

[SD10]

So, can I still queue up PRs for this stuff even if they don’t get merged until their respective versions? I need stuff to work on still 😐

_{Sent with GitHawk}

[rnystrom]

@SD10 haha of course! This will just give everyone a better sense of priority (faster reviews, etc).

_{Sent with GitHawk}

[SD10]

We could also try using the GitHub project management board. However, I’ve never had it work out on anyway of my projects yet

_{Sent with GitHawk}

[rnystrom]

I’m definitely open to trying it, just unclear he value it provides over issues/milestones.

_{Sent with GitHawk}

[SD10]

I actually prefer issues and milestones. I guess the board is only helpful if we had different stages of development like: backlog, in progress, under review, testing, etc. We’re not that organized (yet) maybe one day when we replace the GitHub web app? 😬

_{Sent with GitHawk}

[rizwankce]

Love the whole idea!

Regarding the versioning, guess we are still following Semantic versioning. 🧐

P.S: Back in India - will spend some time for Githawk

[BasThomas]

For those interested, I tried to do this with the 2.0 milestone mainly focusing on pull request reviews!