Re: [VOTE] Traffic Control RELEASE-1.8.0-RC2

[David Neuman]

If I remember correctly, the RPMs were included as a convenience.  I am ok
with not including them, if someone wants an RPM they are easy enough to
build with the build script.

On Thu, Dec 1, 2016 at 1:40 PM, Dan Kirkwood  wrote:

> I'd also love to ditch the RPMs,but I'll abstain from voting since
> it directly impacts me immediately (less work for me!).
>
> Would anyone else like to weigh in on this?
>
> Dan
>
> On Thu, Dec 1, 2016 at 12:52 PM, Leif Hedstrom  wrote:
> >
> >> On Dec 1, 2016, at 12:46 PM, Phil Sorber  wrote:
> >>
> >> http://www.apache.org/dev/release-signing.html#basic-facts
> >>
> >> Missing checksums for the artifacts.
> >>
> >> And for the record, I am still not liking the RPM's as release
> artifacts,
> >> but I'll let the IPMC weigh in on that.
> >
> >
> > If I had a vote, now that you have the tar-ball, I’d ditch all he RPMs.
> If someone needs the RPMs, make a Makefile target such that someone can
> produce those source RPMs (shouldn’t they be .srpm) from the tar-ball.
> >
> > Cheers,
> >
> > — Leif
> >
>

Re: [VOTE] Traffic Control RELEASE-1.8.0-RC2

[Dan Kirkwood]

I'd also love to ditch the RPMs,but I'll abstain from voting since
it directly impacts me immediately (less work for me!).

Would anyone else like to weigh in on this?

Dan

On Thu, Dec 1, 2016 at 12:52 PM, Leif Hedstrom  wrote:
>
>> On Dec 1, 2016, at 12:46 PM, Phil Sorber  wrote:
>>
>> http://www.apache.org/dev/release-signing.html#basic-facts
>>
>> Missing checksums for the artifacts.
>>
>> And for the record, I am still not liking the RPM's as release artifacts,
>> but I'll let the IPMC weigh in on that.
>
>
> If I had a vote, now that you have the tar-ball, I’d ditch all he RPMs. If 
> someone needs the RPMs, make a Makefile target such that someone can produce 
> those source RPMs (shouldn’t they be .srpm) from the tar-ball.
>
> Cheers,
>
> — Leif
>

Re: [VOTE] Traffic Control RELEASE-1.8.0-RC2

[Leif Hedstrom]

> On Dec 1, 2016, at 12:46 PM, Phil Sorber  wrote:
> 
> http://www.apache.org/dev/release-signing.html#basic-facts
> 
> Missing checksums for the artifacts.
> 
> And for the record, I am still not liking the RPM's as release artifacts,
> but I'll let the IPMC weigh in on that.


If I had a vote, now that you have the tar-ball, I’d ditch all he RPMs. If 
someone needs the RPMs, make a Makefile target such that someone can produce 
those source RPMs (shouldn’t they be .srpm) from the tar-ball.

Cheers,

— Leif

Re: [VOTE] Traffic Control RELEASE-1.8.0-RC2

[Phil Sorber]

http://www.apache.org/dev/release-signing.html#basic-facts

Missing checksums for the artifacts.

And for the record, I am still not liking the RPM's as release artifacts,
but I'll let the IPMC weigh in on that.

On Thu, Dec 1, 2016 at 12:36 PM Leif Hedstrom  wrote:

>
> > On Nov 30, 2016, at 10:56 AM, Dan Kirkwood  wrote:
> >
> > Hello All,
> >
> > I've prepared a release for v1.8.0 (RC2)
> >
> > Changes since 1.7.0:
> >
> https://github.com/apache/incubator-trafficcontrol/compare/RELEASE-1.7.0...RELEASE-1.8.0-RC2
> >
> > This corresponds to git:
> > Hash: 8766dbcb38105fbc97b955b4733defe40c83db00
> > Tag: RELEASE-1.8.0-RC2
> >
> > Which can be verified with the following:
>
>
> Minor (nit-pick) detail: Why does the tar-ball unpack into a directory
> named “workspace”? I would have expected it to be
> incubator-trafficcontrol-1.8.0.4567.8766dbcb .
>
> Also, why the UUID in the release name? Is that something the incubator
> wants now?
>
> Cheers,
>
> — leif
>
>

Re: [VOTE] Traffic Control RELEASE-1.8.0-RC2

[Dan Kirkwood]

ahh..thanks,  Leif..I didn't realize it got the workspace in
there..That's a relic of our Jenkins CI build -- it clones into a
"workspace" dir.   Looks like I'll need to modify the build script to
be explicit when creating the tarball..

As for including the git hash in the file name,  we've been following
that convention in the rpm name for a while.   Do you think it should
be dropped from the tarball?   That's written to BUILD_NUMBER before
it's created..

-Dan

On Thu, Dec 1, 2016 at 12:35 PM, Leif Hedstrom  wrote:
>
>> On Nov 30, 2016, at 10:56 AM, Dan Kirkwood  wrote:
>>
>> Hello All,
>>
>> I've prepared a release for v1.8.0 (RC2)
>>
>> Changes since 1.7.0:
>> https://github.com/apache/incubator-trafficcontrol/compare/RELEASE-1.7.0...RELEASE-1.8.0-RC2
>>
>> This corresponds to git:
>> Hash: 8766dbcb38105fbc97b955b4733defe40c83db00
>> Tag: RELEASE-1.8.0-RC2
>>
>> Which can be verified with the following:
>
>
> Minor (nit-pick) detail: Why does the tar-ball unpack into a directory named 
> “workspace”? I would have expected it to be 
> incubator-trafficcontrol-1.8.0.4567.8766dbcb .
>
> Also, why the UUID in the release name? Is that something the incubator wants 
> now?
>
> Cheers,
>
> — leif
>

[VOTE] Traffic Control RELEASE-1.8.0-RC2

[Dan Kirkwood]

Hello All,

I've prepared a release for v1.8.0 (RC2)

Changes since 1.7.0:
https://github.com/apache/incubator-trafficcontrol/compare/RELEASE-1.7.0...RELEASE-1.8.0-RC2

This corresponds to git:
Hash: 8766dbcb38105fbc97b955b4733defe40c83db00
Tag: RELEASE-1.8.0-RC2

Which can be verified with the following:

git tag -v RELEASE-1.8.0-RC2

My code signing key is available here:
  http://keys.gnupg.net/pks/lookup?search=0x4587A8F0=vindex

Make sure you refresh from a key server to get all relevant signatures.

RPMs for all products are available here:
https://dist.apache.org/repos/dist/dev/incubator/trafficcontrol/1.8.0/RC2/

The vote is open until Wednesday, December 7, 2016.

Thanks!