The only change compared to RC1 is one to a unit test which wouldn't
pass unless you already had PAX Exam in your local mvn repo.
Compress 1.20 RC2 is available for review here:
https://dist.apache.org/repos/dist/dev/commons/compress/
(svn revision 37873)
The tag is here:
https://git
> On 4 Feb 2020, at 19:36, Jochen Wiedmann wrote:
>
> On Mon, Feb 3, 2020 at 3:57 PM Gary Gregory wrote:
>
>> The commit
>> https://gitbox.apache.org/repos/asf?p=commons-lang.git;a=commit;h=2ea44b2adae8da8e3e7f55cc226479f9431feda9
>> broke
>> the Travis build due to Checktyle errors.
>
> As
On Mon, Feb 3, 2020 at 3:57 PM Gary Gregory wrote:
> The commit
> https://gitbox.apache.org/repos/asf?p=commons-lang.git;a=commit;h=2ea44b2adae8da8e3e7f55cc226479f9431feda9
> broke
> the Travis build due to Checktyle errors.
As the responsible person, I apologize for that. I am sure, that I did
I’d honestly expect that several components here are prime candidates for a
more student-heavy audience, particularly the more academic-aligned
components like the math ones in particular. The components are also low
level enough to not require experience in any specific frameworks which is
nice. I
Hello.
Is "Commons" willing to set up itself for welcoming new
people who, in order to contribute to the projects, might
need more support than the usual asynchronous review
of patches?
The ASF participates in GSoC[1] and Outreachy[2] and
some Apache projects seem well prepared for dealing with
t
On 04/02/2020 09:56, Peter Verhas wrote:
It also breaks all the pull requests and I am not sure that Travis on
GitHub gives it a try again when the master changes. What is the expected
procedure? Should I push a null change commit to the branch to trigger
Travis after the master is fixed? How s
It also breaks all the pull requests and I am not sure that Travis on
GitHub gives it a try again when the master changes. What is the expected
procedure? Should I push a null change commit to the branch to trigger
Travis after the master is fixed? How should I know when the master is
fixed? Should
Hi
Sorry for reply late, because of Spring Festival and SARI.
> Some remarks:
> * I didn't get why the "KMeansPlusPlusCentroidInitializer" class
> does not call the existing "KMeansPlusPlusClusterer".
> Code seems duplicated: As there is a case for reuse, the currently
> "private" centroid ini
