How to break down milestones?

[seporaitis]

Currently it's done by version, but maybe MySQL statement based milestones would make more sense? E.g. have a milestone for 'ALTER TABLE' support and break it down into the different bits from alter_specification in the docs.

Why I like the idea is that it would be possible to roughly, but accurately, say how much of MySQL statement syntax is covered.

Why I dislike the idea is that I don't plan to work on e.g. full support of CREATE TABLE statement, so these milestones wouldn't have a due date and would just drag along.

Why this is a problem at all? Because, as I understand it, issue can have only one milestone assigned to it. So that leaves us with either:

• not doing this at all;
• doing statement based milestones & having a label for versioned release (losing due dates & if this continues to grow - having loads of short lived, not used, labels);
• leaving semantic versioning milestones & having statement based labels (allows due dates, but loses the "% of syntax supported").

So yeah... any suggestions - most welcome.