I believe that both Scala and Kotlin have been approved by various PMC
members here, though no contributions have been made related to either yet.
Though I haven’t used Scala actively in a couple years, I can help review
code and such still.
On Thu, Sep 17, 2020 at 14:47 Oliver Heger
wrote:
>
Branches have green checks on them too. Every commit does unless you push
more than one at a time to a single branch (then they’re batched). This
applies to both Jenkins and GH Actions.
On Thu, Sep 17, 2020 at 19:39 Gary Gregory wrote:
> On Thu, Sep 17, 2020 at 12:23 PM Matt Sicker wrote:
>
>
On Thu, Sep 17, 2020 at 12:23 PM Matt Sicker wrote:
> Do they show up as branches before or after the PR? If it’s before, maybe
> we can disable the PR and just use the branches.
>
We need to keep PRs IMO: Getting a PR is the main benefit here because a
human can verify that there is a matching
Hi all,
once we had a discussion (it must be one or two years ago) whether
Commons could support components in other (JVM) languages, too. IIRC,
there were no strong objections, but there has never been a follow up.
For a project in Scala, I needed some limited functionality to process
command
I can confirm that PR https://github.com/apache/commons-net/pull/59
fixes the regressing bug in Apache Commons VFS master tests in
**org.apache.commons.vfs2.provider.ftps.test** which was introduced by
Commons Net 3.7.
The PR does not have a test though.
Gary
On Thu, Sep 17, 2020 at 12:14 PM
Do they show up as branches before or after the PR? If it’s before, maybe
we can disable the PR and just use the branches.
On Wed, Sep 16, 2020 at 20:53 Gary Gregory wrote:
> On Wed, Sep 16, 2020 at 8:53 PM Matt Sicker wrote:
>
> >
>
> > Don’t Dependabot PRs show up as branches in each git
Connecting dots FTR: https://issues.apache.org/jira/browse/NET-687
On Fri, Sep 11, 2020 at 9:46 AM Gary Gregory wrote:
>
> Hi All:
>
> Updating Commons VFS from Commons Net 3.6 to 3.7 causes failures. Please see:
>
> https://github.com/apache/commons-vfs/pull/128
>
> For example:
>
>
On Thu, Sep 17, 2020 at 6:47 AM sebb wrote:
>
> Does VFS actually *need* the latest version of NET?
Sigh, that's irrelevant as you can't control downstream stacks. This
is a regression from the user's point of view.
> i.e. does it fix a bug or a security issue that impacts VFS?
I hope that's a
Does VFS actually *need* the latest version of NET?
i.e. does it fix a bug or a security issue that impacts VFS?
If not, then downdate until such time as the issue can be fixed.
It would be helpful to have a simple test case that shows the issue.
On Tue, 15 Sep 2020 at 14:08, Gary Gregory
