Release tags match v<major>.<minor>.<patch>, so just check the tag list for the most recent v1.y.z. Don't automatically go to 2.anything since releases are semantically versioned and that would indicate backward-incompatibility.
On Thu, Feb 14, 2019, 17:24 Eric S. Raymond <e...@thyrsus.com wrote: > Daniel Franke <dfoxfra...@gmail.com>: > > You probably don't want to auto-pull the latest HEAD every time it gets > an > > update; only releases get the full battery of QA. Note I'll probably be > > stamping a release this weekend since the last release from two years ago > > has a build issue with more recent OpenSSL versions. > > How do you recommend we get the latest stable version from within a CI > script? > -- > <a href="http://www.catb.org/~esr/";>Eric S. Raymond</a> > > My work is funded by the Internet Civil Engineering Institute: > https://icei.org > Please visit their site and donate: the civilization you save might be > your own. > > >
_______________________________________________ devel mailing list devel@ntpsec.org http://lists.ntpsec.org/mailman/listinfo/devel
