Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [hono-dev] Milestones in GitHub

Hi Kai,

Actually GitHub notion of "Milestone" is really "version". Don't treat it as a milestone, but rather like Jira's version :) .


śr., 24.02.2016 o 13:07 użytkownik Hudalla Kai (INST/ESY1) <Kai.Hudalla@xxxxxxxxxxxx> napisał:



that’s a great idea J However, according to the Eclipse development process we are encouraged to do milestone releases but need to indicate that it’s a milestone in the version, i.e. we should re-name the milestone to include the target version of the release and then use Mn suffixes, e.g. 0.1-M1 or 1.0-M2, to indicate the milestone number (we can have multiple milestones for a target version).


We should agree on an “initial” target version we want to prepare for. Personally, I would rather release early and often (and thus have something like a 0.1 release) instead of working for years on a 1.0 release.


What do you think?






From: hono-dev-bounces@xxxxxxxxxxx [mailto:hono-dev-bounces@xxxxxxxxxxx] On Behalf Of Henryk Konsek
Sent: Wednesday, February 24, 2016 1:00 PM
To: hono developer discussions
Subject: [hono-dev] Milestones in GitHub




I have created 0.1 Milestone [1] in GitHub. I propose to assign every GitHub issue we resolve to that milestone. It is useful for tracking what has been done in given release, for example when we would like to create release notes during 0.1 release.





Henryk Konsek

hono-dev mailing list
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
Henryk Konsek

Back to the top