Open chris-b-pacon opened 1 year ago
Milestones would be something like:
(1-3) would be a major release.
(4) would be another major release.
Since you are maintainer of this product I suggest that you define the milestones. You can do it right here in Github (and I am convinced you already know that), and then we can discuss what is viable and what not.
Ah, ok, I'll look where to enter the milestones.
Milestone should be associated to a (sub)version number like 2.6.7
Please don't ask about details, because I know little about this, since we didn't use this at my company until recently. I am going to read about it, but appreciate your thoughts about it.
I suggest to define milestones by version numbers, and then assign features to them.
You have some ideas for the future of this project.
We should create milestones to define some goals.