Re: Removal of stale branches for apache/james projects

2021-06-02 Thread Jean Helou
On Wed, Jun 2, 2021 at 9:54 AM btell...@apache.org wrote: > > A bit of house cleaning might be beneficial Without objections, I > will clean these brnches in a few days. > +9001 (cuz it's over 9000) ! > Furthermore the following projects do not have code associated to them: > > -

Re: Removal of stale branches for apache/james projects

2021-06-02 Thread Rene Cordier
+1 Rene. On 02/06/2021 14:54, btell...@apache.org wrote: Hello all, While having a look at branches built by the ASF CI when switching the tokens I noticed we have many stale, meaningless branches on some of our repositories. This includes:  -

Removal of stale branches for apache/james projects

2021-06-02 Thread btell...@apache.org
Hello all, While having a look at branches built by the ASF CI when switching the tokens I noticed we have many stale, meaningless branches on some of our repositories. This includes:  - https://github.com/apache/james-project/branches/all     - cassandra-blobstore-cl-one (merged)     -

Re: Major bug: Camel mailet container and partial matches.

2021-06-02 Thread btell...@apache.org
Hello dear James committers, In the absence of further feedback I will proceed with sanitizing the [1] proof of concept, to turn it into a full removal of Camel. Cheers, Benoit On 24/05/2021 11:50, Rene Cordier wrote: > Hi Benoit, > > Thanks for raising this concern it's rather interesting,

Re: Github token for Apache JAMES ASF build

2021-06-02 Thread btell...@apache.org
Sure, this should be the explanation. I will switch the tokens today. Cheers, Benoit On 28/05/2021 14:28, Jean Helou wrote: >> I just set up additional builds for JSPF, JSPF, JSIEVE and MIME4J >> projects, and successfully used the asf-ci tokens. >> >> Is there any reasons not to switch these