Sure I’d be happy to talk at some time tomorrow. Let me know when you’re free.
I’ll likely be in the hackathon room for a good portion of the day.
Cheers,
-Rob
> On Sep 9, 2019, at 2:47 PM, Kenneth Paskett wrote:
>
> Hi Rob -
>
> I'm here at ApacheCon this week, and would be happy to sit
Hi Rob -
I'm here at ApacheCon this week, and would be happy to sit down with you
and others from the Commons group to talk about your logo update. Let me
know what time works best for your group.
~Kenneth
On Mon, Sep 9, 2019 at 12:08 PM Rob Tompkins wrote:
>
>
> > On Sep 9, 2019, at 11:31
Le lun. 9 sept. 2019 à 21:17, Gary Gregory a écrit :
>
> The KISS solution would be to get "Central" to produce not just the Commons
> logo but one for each component and be done.
+1
Especially if the future is that "Central Services" will provide logos
for all the projects.
> The even simpler
Great! Thanks Rob.
Gary
On Mon, Sep 9, 2019, 15:39 Rob Tompkins wrote:
> Thanks….I was planning on starting a parent release after my talks today,
> FWIW.
>
> > On Sep 9, 2019, at 12:38 PM, ggreg...@apache.org wrote:
> >
> > This is an automated email from the ASF dual-hosted git repository.
>
Thanks….I was planning on starting a parent release after my talks today, FWIW.
> On Sep 9, 2019, at 12:38 PM, ggreg...@apache.org wrote:
>
> This is an automated email from the ASF dual-hosted git repository.
>
> ggregory pushed a commit to branch master
> in repository
The KISS solution would be to get "Central" to produce not just the Commons
logo but one for each component and be done. The even simpler path is to
forgo component specific logos, especially since Commons is just one Apache
project. I like simpler...
Gary
On Mon, Sep 9, 2019, 15:08 Rob Tompkins
> On Sep 9, 2019, at 11:31 AM, Gilles Sadowski wrote:
>
> Hi.
>
> Le lun. 9 sept. 2019 à 12:35, Sally Khudairi a écrit :
>>
>> Thank you, Gilles.
>>
>> I'm copying Kenneth Paskett, creative lead from Central Services. I was
>> talking to him about this opportunity yesterday: we will be
Hi.
Le lun. 9 sept. 2019 à 12:35, Sally Khudairi a écrit :
>
> Thank you, Gilles.
>
> I'm copying Kenneth Paskett, creative lead from Central Services. I was
> talking to him about this opportunity yesterday: we will be happy to explore
> options for a future design.
>
> I'm not saying "don't
Hello.
It occurred to me that if the community wants to KISS, the Commons
logo could be something like
/
/ Apache
/ Commons
/
[The slanted line is the feather. Colors, fonts, sizes variants
to be proposed by "Central Services"...]
A simple variation for a component that
No, it was more of a personal idea so far. I've been doing work in
Log4j lately in my free time, so I have no target yet.
On Mon, 9 Sep 2019 at 12:20, Romain Manni-Bucau wrote:
>
> Sounds like convergent.
>
> Any targetted deadline?
> On my side I need a PoC soon - like last week ;) - so will
Sounds like convergent.
Any targetted deadline?
On my side I need a PoC soon - like last week ;) - so will start included
in the happy but happy to catch up after.
Pushed in my todo to hack in sandbox but from scratch works too for me.
Le lun. 9 sept. 2019 à 18:10, Matt Sicker a écrit :
> We
We have scattered graph logic in Jenkins Core as well as the Pipeline
plugins. If I wanted to use a graph library in Jenkins, it would be
best to use minimal dependencies because any dependencies included
with Jenkins tend to get reused by plugins which can cause upgrade
problems later, especially
Bruno,
Thank you for your review.
I believe I addressed all of your findings in master.
Gary
On Mon, Sep 9, 2019 at 2:58 AM Bruno P. Kinoshita wrote:
> Build passing on jDK 8
> Apache Maven 3.5.4 (1edded0938998edf8bf061f1ceb3cfdeccf443fe;
> 2018-06-18T06:33:14+12:00)
> Maven home:
On Mon, Sep 9, 2019 at 10:42 AM sebb wrote:
> On Mon, 9 Sep 2019 at 14:00, Gary Gregory wrote:
> >
> > It seems like we really should put future release tags under 'rel/'
>
> Yes and no.
>
> I don't think the tag should be created before the release vote has
> succeeded.
>
What I meant is
On Mon, 9 Sep 2019 at 14:00, Gary Gregory wrote:
>
> It seems like we really should put future release tags under 'rel/'
Yes and no.
I don't think the tag should be created before the release vote has succeeded.
> It's too bad it can't simply be 'releases/' to make it clearer.
>
> Then there
On Mon, Sep 9, 2019 at 9:07 AM Mark Roberts
wrote:
> I don’t need to run jacoco to know the coverage is almost zero for the
> classes added to support the new Java 9+ attributes. I could cobble
> something up if there was some way to add a Java 11 .class file to use as
> input to a test.
>
You
I don’t need to run jacoco to know the coverage is almost zero for the classes
added to support the new Java 9+ attributes. I could cobble something up if
there was some way to add a Java 11 .class file to use as input to a test.
Mark
From: Gary Gregory [mailto:garydgreg...@gmail.com]
It seems like we really should put future release tags under 'rel/'
It's too bad it can't simply be 'releases/' to make it clearer.
Then there is the issue of moving all of our past release tags under
'rel/', another thing we should do...
Gary
On Fri, Sep 6, 2019 at 5:02 AM sebb wrote:
>
I am cancelling this VOTE.
Something got borked. Might as well clean it all up.
Gary
On Mon, Sep 9, 2019 at 2:58 AM Bruno P. Kinoshita wrote:
> Build passing on jDK 8
> Apache Maven 3.5.4 (1edded0938998edf8bf061f1ceb3cfdeccf443fe;
> 2018-06-18T06:33:14+12:00)
> Maven home:
Thank you, Gilles.
I'm copying Kenneth Paskett, creative lead from Central Services. I was talking
to him about this opportunity yesterday: we will be happy to explore options
for a future design.
I'm not saying "don't use anything that remotely looks like the feather". It's
important that
Hello.
Le sam. 7 sept. 2019 à 13:29, Sally Khudairi a écrit :
>
> Thank you, Gilles. I appreciate you reaching out.
>
> Normally I encourage PMCs to not re-orient or "spindle" the feather where
> possible, but I understand that some legacy logos have a bit of a problem
> with positioning. For
Le lun. 9 sept. 2019 à 11:06, Rob Vesse a écrit :
> Playing Devil's advocate:
>
> I am always curious when folks complain about a "huge" dependency stack
> (for a start the term huge is inherently subjective). This is pretty much
> the reality of the modern OSS ecosystem, people (yourself
Playing Devil's advocate:
I am always curious when folks complain about a "huge" dependency stack (for a
start the term huge is inherently subjective). This is pretty much the reality
of the modern OSS ecosystem, people (yourself included) try to avoid
reinventing the wheel and want to focus
The following votes were cast:
Binding:
+1: markt, kinow, chtompki, ggregory
No other votes were cast.
The vote therefore passes.
Thanks to everyone who contributed to this release.
Mark
On 05/09/2019 21:39, Mark Thomas wrote:
> A couple of regressions have been identified in the 1.2.0
Build passing on jDK 8
Apache Maven 3.5.4 (1edded0938998edf8bf061f1ceb3cfdeccf443fe;
2018-06-18T06:33:14+12:00)
Maven home: /opt/apache-maven-3.5.4
Java version: 1.8.0_222, vendor: Private Build, runtime:
/usr/lib/jvm/java-8-openjdk-amd64/jre
Default locale: en_NZ, platform encoding: UTF-8
OS
25 matches
Mail list logo
