New Milestone Categories

[Archmonger]

With our upcoming switch to semantic versioning, I have modified our milestone categories.

Experimental/Theoretical
Issues that are potentially not technologically feasible, or would require a lot of engineering to accomplish.
Luxury
Issues that would make developing in IDOM easier, but have pre-existing workarounds.
Essential
Issues that have an existing impact on the user's capability to develop.

cc: @rmorshea

[rmorshea]

I'm good with these. With that said, do you think we should make the first release of reactpy 1.0 or continue with 0 versioning for a while longer there.

[Archmonger]

I think it should be 1.0 to signify a production/stable release.

[rmorshea]

Renamed the last one to "Speculative"

[rmorshea]

Now that I'm thinking about it, these categories don't really seem any different from our priority labels.

[rmorshea]

Perhaps we should just create milestones for the next foreseeable versions. This might also be useful since we'll want to decouple the js and py package releases in order to allow them to evolve independently.

[rmorshea]

I created release-* labels for patch/minor/major. We can use these to organize things into genuine version milestones as we go.

[Archmonger]

We might want to take a look at some bigger projects and see how they organize their GitHub milestones and labels.