| Re: [hono-dev] Milestones in GitHub |
Henryk,
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?
Regards,
Kai
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
Hi,
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.
Cheers!
--
Henryk Konsek
_______________________________________________
hono-dev mailing list
hono-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/hono-dev