Use of milestones #2627
Replies: 2 comments 4 replies
-
IMO yes, as this greatly simplifies my life be looking in which release the regression was introduced or from which release some bug should be fixed.
I always do that, but I've given up asking people to use proper commit messages (including both reasoning and link to issue), if I would start asking them for using milestones I would be considered fully mad.
See https://github.com/eclipse-jdt/eclipse.jdt.core/milestone/43?closed=1
No idea |
Beta Was this translation helpful? Give feedback.
-
|
Theia project automated setting milestone on PR merge via EstherPerelman/theia@d00dca2 . With some adjustment this should be working for JDT too(I would happily copy to rest of the projects in SDK if/when someone spends the time to make it work). |
Beta Was this translation helpful? Give feedback.
-
Not sure what do you mean by that, which projects and which work? |
Beta Was this translation helpful? Give feedback.
-
|
If someone makes auto assigning milestone on merge work in e.g. JDT(core) by adopting Theia's script (or some other similar), I'll copy the approach to Platform/PDE/Equinox. |
Beta Was this translation helpful? Give feedback.
-
|
I've created eclipse-platform/eclipse.platform.releng.aggregator#2203. |
Beta Was this translation helpful? Give feedback.
-
|
closing . to be continued on aggregator |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Today, for the first time since the move to github, a bug reporter asked me which "milestone" contains a given fix.
I readily admit that I forgot to mark it on the issue.
So, how to we handle milestones?
Beta Was this translation helpful? Give feedback.
All reactions