htrace-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Colin McCabe <cmcc...@alumni.cmu.edu>
Subject Re: releasing native build artifacts
Date Thu, 23 Apr 2015 19:18:22 GMT
+1

C.

On Thu, Apr 23, 2015 at 12:15 PM, Lewis John Mcgibbney
<lewis.mcgibbney@gmail.com> wrote:
> Hi Colin,
> My understanding is that none of this is yet established on builds.a.o is
> this correct?
> https://builds.apache.org/view/H-L/view/HBase/
> Maybe it would be a nice opportunity to get that sorted out as well.
> Lewis
>
> On Thu, Apr 23, 2015 at 11:46 AM, Colin P. McCabe <cmccabe@apache.org>
> wrote:
>
>> Hi all,
>>
>> Based on the responses in the earlier thread, it sounds like it's
>> getting to be about that time again... time for a new HTrace release
>> :)
>>
>> I've been thinking about what we should do with our native build
>> artifacts.  With Java, we only ever have to build one version of
>> everything, since the jar files can run on any architecture and
>> supported OS.  But we now have a C client (which is only at an alpha
>> level of stability, but still...) and the htraced server, which is
>> also not Java.
>>
>> Do we want to do builds of this stuff for the common OS/arch
>> configurations?  If we did a RHEL6 / x86_64 build and an Ubuntu 12.04
>> / x86_64 build, that would cover most of our users, I think.  We could
>> also do 32-bit builds, but I don't think anyone is actually using
>> 32-bit any more in big data land (and if they are, they need to stop
>> :)
>>
>> This also means we would have 3 downloads available in the next release:
>> * Just jar files + source
>> * Jar files + source + RHEL6/x86_64 libhtrace.so + htraced
>> * Jar files + source + Ubuntu 12.04/x86_64 libhtrace.so + htraced
>>
>> thoughts?
>>
>> Colin
>>
>
>
>
> --
> *Lewis*

Mime
View raw message