Am 13.05.19 um 11:35 schrieb Matthias Welwarsky:
On Samstag, 11. Mai 2019 10:50:03 CEST Liviu Ionescu wrote:
> > On 11 May 2019, at 10:47, [email protected] wrote:
> >
> > I think we're more than ripe for a new release,
>
> super!
>
> > but there's one patch series ... and a few kinks ...
>
> sure, I don't think there's a real rush, when you think the code is ready
> for a new release, just let us know.
>
> ---
>
> what do you think about making periodic releases and possibly adopting
> semantic versioning (semver)?
Hm. That has a lot of implications.
I cannot see openocd doing major/minor releases, let alone patches. There is no
roadmap, no
definition of what major/minor would mean. Given our contribution model, it
doesn't seem viable.
Contributions will hardly ever match up with features on a roadmap. We just
have to take what's coming.
Patch releases imply that a "stable" version exists to receive these patches. I
don't see that
happening. I'm all for increasing the release frequency, though. But a single,
incremental version
number is IMHO good enough for our release model. What about the next version just being
"11"
followed be "12" half a year later?
Automatic nightly builds for the supported platforms would be nice and will
make openocd more
accessible between releases.
I'm ok with it. Or we can use just use year and month of release:
2019.05.0.
It will be easy to recognize how old is the version and make communication on
IRC even more funny:
2032.03.12 12:12 <aaa>: hi, my OpenOCD version 1976.02.0 is not working
properly, can you please
help me?
--
Regards,
Oleksij
_______________________________________________
OpenOCD-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/openocd-devel
