zipkin-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Adrian Cole <adrian.f.c...@gmail.com>
Subject [VOTE FAILED] Release Apache Zipkin Brave Karaf (Incubating) version 0.1.2
Date Sat, 23 Feb 2019 00:50:31 GMT
This vote failed due to binaries in the distribution. Will send a new
vote shortly.

Thanks for the input, all.
-A

On Fri, Feb 15, 2019 at 7:56 AM Adrian Cole <adrian.f.cole@gmail.com> wrote:
>
> Perfectly fine naming suggestion. thanks, Dave.
>
> "Apache Zipkin Brave (incubating) for Apache Karaf"
>
> I will put that into a pull request and suspect no-one will contest it.
>
> -A
>
> On Fri, Feb 15, 2019, 7:43 AM Dave Fisher <wave@apache.org wrote:
>>
>> Hi Adrian,
>>
>> (NOTE - cross posted to private lists. Take care with replies.)
>>
>> Thanks for your patience regarding the branding issue I mentioned.
>>
>> > On Feb 14, 2019, at 4:29 AM, Adrian Cole <adrian.f.cole@gmail.com> wrote:
>>
>> <snip>
>>
>> > Finally, there was an unresolved question about branding of the repo. I
>> > dont think we should attempt another release if there is something else
>> > lurking.
>>
>> The name Apache Zipkin Brave Karaf (incubating) represents a confusion of two Apache
Brands - Zipkin an incubating podling and Apache Karaf.
>>
>> See http://www.apache.org/foundation/marks/pmcs#other
>>
>> This suggests that the proper name respecting Karaf’s brand would be "Apache Zipkin
Brave (incubating) for Apache Karaf"
>>
>> Regards,
>> Dave
>>
>> >
>> > Thanks for the help folks.
>> >
>> > -Adrian
>> >
>> >
>> > On Thu, Feb 14, 2019, 7:40 PM John D. Ament <johndament@apache.org wrote:
>> >
>> >> On Thu, Feb 14, 2019 at 6:35 AM Justin Mclean <justinmclean@me.com>
wrote:
>> >>
>> >>> Hi,
>> >>>
>> >>>> I can follow up with the developer to fix their headers via a github
>> >>> issue (if no one else gets to it before me).
>> >>>
>> >>> I already have raise it as an issue :-)  Add to it it if you want. [1]
>> >>>
>> >>>> Including prior statements about NOTICE is completely optional,
but in
>> >>> the
>> >>>> case of no SGA would be ideal.  I don't think that's a blocker for
>> >>> release …
>> >>>
>> >>> No neither do I think it is a blocker, but having a jar in a source
>> >>> release is.
>> >>>
>> >>>
>> >> And I can see in the repo that's already been resolved.  So I think
>> >> Adrian's all set to re-roll the release and put it up for a vote.
>> >>
>> >>
>> >>> Thanks,
>> >>> Justin
>> >>>
>> >>> 1. https://github.com/takari/maven-wrapper/issues/104
>> >>> ---------------------------------------------------------------------
>> >>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>> >>> For additional commands, e-mail: general-help@incubator.apache.org
>> >>>
>> >>>
>> >>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@zipkin.apache.org
>> For additional commands, e-mail: dev-help@zipkin.apache.org
>>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@zipkin.apache.org
For additional commands, e-mail: dev-help@zipkin.apache.org


Mime
View raw message