Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [jaxrs-dev] GitHub milestones
AFAIK you still can assign issues to closed milestones. Closed milestones just don't show up by default any more and you have to switch to the "Closed" tab to see them.

Am Do., 29. März 2018 um 19:54 Uhr schrieb Markus KARG <markus@xxxxxxxxxxxxxxx>:

+1 for closing old milestones, but only if it keeps possible to add issues to that milestones still. The reason is that we detected several issues which had been open but in fact are fixed in 2.1 already, and I want to be able to still collect those issues in that closed milestones then. At least until we found the time to read all the open issues.

-Markus

 

From: jaxrs-dev-bounces@xxxxxxxxxxx [mailto:jaxrs-dev-bounces@xxxxxxxxxxx] On Behalf Of Christian Kaltepoth
Sent: Donnerstag, 29. März 2018 06:34
To: jaxrs developer discussions
Subject: [jaxrs-dev] GitHub milestones

 

Hi all,

 

I just saw that the GitHub migration script created milestones for all the past releases (2.0, 2,1, etc) but didn't close them. I guess we should do so now. Any objections?

 

Christian

 

--

_______________________________________________
jaxrs-dev mailing list
jaxrs-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/jaxrs-dev


--
Christian Kaltepoth
Blog: http://blog.kaltepoth.de/
Twitter: http://twitter.com/chkal
GitHub: https://github.com/chkal

Back to the top