release management

[mfrey]

Is there a rationale behind the version numbers? As far as I understood, we are on 2.0.0 since a lot of code has been re-organized, rewritten, etc. I'm wondering what the next release after the "this is the last NFN-supported release" of ccn-lite would look alike.

We should define a "release management" process and document it in the wiki. I'm all in for keep it low overhead, but it should a) be clear what the version numbers mean, b) a process defined and in place how we plan our releases (e.g. a milestone per release which contains issue numbers we would like to see to be resolved in this release). Any thoughts?

[blacksheeep]

I think there wars a rational behind those numbers.
we had 0.1.0, 0.2.0, 0.3.0 as alpha releases and for feature updates.
we had first number increasing for project structure change and we got to '2' because the first version just never left alpha status.
we would increase last number for bugfixes.
next version would be 2.0.1 if only bugfixes or 2.1.0 of features changes.

This we already changed a lot, it will be 2.1.0

[blacksheeep]

That is a good question. When we finished removing NFN and improved the quality? That will also answers what will be the release. Michael Frey <[email protected]> schrieb am Mi., 16. Mai 2018, 11:06:

…

Thanks! What/when is the next release and what will it include? — You are receiving this because you were assigned. Reply to this email directly, view it on GitHub <#243 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ADeQ_Yisl-OXUHkpxRlSfev3_gc3AMQjks5ty-wegaJpZM4UA5wm> .