I looked at the Autoconf manual for words of wisdom. They did not have too
much to say, but they pointed me to their git repository, so I looked at
the configure.ac that they use to build autoconf.
AC_INIT([GNU Autoconf],
m4_esyscmd([build-aux/git-version-gen .tarball-version]),
[[email protected]])
Anyway, I guess that (build-aux/git-version-gen script) all gets back to
"git describe", like came up in another thread recently.
I say: it used to be easy to know what a release is: the project delivers a
set of source tarballs, and each tarball is marked by a unique increasing
release number. In that simple case, I think I would either use the fancy
mechanism like Autoconf project does, or bump up the number manually in
AC_INIT when I know I am working towards a new release. VPP is possibly
more complicated, so I have no answers -- just too much time on my hands:-)
Burt
On Wed, Jun 7, 2017 at 9:04 AM, Damjan Marion (damarion) <[email protected]
> wrote:
>
> Personally I think that jar filenames should not contain dot releases are
> bugfix-only releases as they should be drop-in replacements.
>
> If you still want to go that way, please use version script.
>
>
> On 6 Jun 2017, at 18:09, Marek Gradzki -X (mgradzki - PANTHEON
> TECHNOLOGIES at Cisco) <[email protected]> wrote:
>
> Hi,
>
> could we bump vpp version in stable/1704 branch
> to 17.04.2 in order to match next release version?
>
> Here is patch:
> https://gerrit.fd.io/r/#/c/7031/
>
> The reason is to have correct version of jvpp artifacts in nexus (more
> details below).
>
> Regards,
> Marek
>
> -----Original Message-----
> From: Marek Gradzki -X (mgradzki - PANTHEON TECHNOLOGIES at Cisco)
> Sent: 6 czerwca 2017 17:21
> To: '[email protected]' <fdio-helpdesk@rt.
> linuxfoundation.org>
> Cc: Ed Warnicke (eaw) <[email protected]>
> Subject: RE: [FD.io <http://fd.io/> Helpdesk #41302] Missing jvpp 1704
> artifacts in fd.io.snapshot repository
>
> Thanks for information! We will ask vpp and nsh projects to update version
> of jvpp artifacts to 17.04.1-SNAPSHOT
>
> Marek
>
> -----Original Message-----
> From: Andrew Grimberg via RT [mailto:[email protected]
> <[email protected]>]
> Sent: 2 czerwca 2017 16:56
> To: Marek Gradzki -X (mgradzki - PANTHEON TECHNOLOGIES at Cisco) <
> [email protected]>
> Cc: Ed Warnicke (eaw) <[email protected]>
> Subject: Re: [FD.io <http://fd.io/> Helpdesk #41302] Missing jvpp 1704
> artifacts in fd.io.snapshot repository
>
> Greetings folks,
>
> Nexus automatically cleans up _any_ snapshot for that exists in the
> snapshot repositories that has the _same_ version as a released artifact.
> This is part of the design of nexus.
>
> Since io.fd.nsh_sfc:nsh-sfc:jar:17.04 is in the release repository it
> will clean up any of the artifacts in the snapshot repository on a daily
> basis that match io.fd.nsh_sfc:nsh-sfc:jar:17.04-SNAPSHOT
>
> This goes for any other artifact that you've done a release of. Your only
> proper way forward is to either start depending on the released version
> _or_ the new SNAPSHOT version.
>
> -Andy-
>
> On 06/01/2017 10:22 PM, [email protected] via RT wrote:
>
>
> Hi,
>
> It looks like the vpp snapshots have been removed again.
>
> Any idea why it happened?
>
> Marek
>
>
> -----Original Message-----
> From: Marek Gradzki -X (mgradzki - PANTHEON TECHNOLOGIES at Cisco)
> Sent: 31 maja 2017 16:56
> To: '[email protected]'
> <[email protected]>
> Cc: Ed Warnicke (eaw) <[email protected]>
> Subject: RE: [FD.io Helpdesk #41302] Missing jvpp 1704 artifacts in
> fd.io.snapshot repository
>
> Thanks. It looks like we have the same issue with nsh:
>
> https://nexus.fd.io/content/repositories/fd.io.snapshot/io/fd/nsh_sfc/
> nsh-sfc/
>
> recheck of
>
> https://gerrit.fd.io/r/#/c/6659/2
>
> failed
>
> https://jenkins.fd.io/job/hc2vpp-verify-1704-centos7/52/console
>
> because of missing io.fd.nsh_sfc:nsh-sfc:jar:17.04-SNAPSHOT
>
> Regards,
> Marek
>
> -----Original Message-----
> From: Vanessa Valderrama via RT
> [mailto:[email protected]]
> Sent: 31 maja 2017 16:37
> To: Marek Gradzki -X (mgradzki - PANTHEON TECHNOLOGIES at Cisco)
> <[email protected]>
> Cc: Ed Warnicke (eaw) <[email protected]>
> Subject: [FD.io Helpdesk #41302] Missing jvpp 1704 artifacts in
> fd.io.snapshot repository
>
> Marek,
>
> I issued a remerge and the artifacts are in the repo. I an still
> investigating why they were removed.
>
>
> On Wed May 31 04:38:22 2017, [email protected] wrote:
>
> Hi,
>
> I've noticed that vpp 17.04 artifacts were removed from
>
> https://nexus.fd.io/content/repositories/fd.io.snapshot/io/fd/vpp/**/
>
> This causes hc2vpp stable/1704 build failures.
> Do you know why that happened and how we can prevent it from
> happening in the future?
>
> Ed: could you please remerge https://gerrit.fd.io/r/#/c/6880/ ?
>
> Regards,
> Marek
>
>
>
>
>
>
> --
> Andrew J Grimberg
> Lead, IT Release Engineering
> The Linux Foundation
>
>
> _______________________________________________
> vpp-dev mailing list
> [email protected]
> https://lists.fd.io/mailman/listinfo/vpp-dev
>
>
>
> _______________________________________________
> vpp-dev mailing list
> [email protected]
> https://lists.fd.io/mailman/listinfo/vpp-dev
>
_______________________________________________
vpp-dev mailing list
[email protected]
https://lists.fd.io/mailman/listinfo/vpp-dev
