The invalid has imho to do with, yahoo. You should be able to use a
apache.org address, if you have commiter status. Just configure an alias
on your email client.
Am 13.06.20 um 06:06 schrieb Miguel Munoz:
When I send an email to this list, my email address shows up in the archive as
ending
When I send an email to this list, my email address shows up in the archive as
ending with .INVALID. Is there anything I can do about this? (I submitted an
ICLA, so that shouldn't be the problem.)
-- Miguel Muñoz
-
To
Oh.
Then I guess work in this thread is already done.
Oh wait.
You might need this:
https://github.com/apache/commons-graph/pull/2
Gilles Sadowski 于2020年6月13日周六 上午10:11写道：
> 2020-06-13 4:05 UTC+02:00, Xeno Amess :
> >> This discussion requires another thread.
> >
> > Well I don't think so, as I
2020-06-13 4:05 UTC+02:00, Xeno Amess :
>> This discussion requires another thread.
>
> Well I don't think so, as I think this thread aims for making travis-ci can
> pass.
No; this thread was about setting up Travis (as asked by Amey).
> [...]
> This discussion requires another thread.
Well I don't think so, as I think this thread aims for making travis-ci can
pass.
And test failures are the reason why it cannot pass ci for now.
I don't see the value in creating another thread.
Btw: I tested (if my memory are correct, as I didn't make
2020-06-13 1:43 UTC+02:00, Xeno Amess :
> Done.
> Environment win10, jdk8.
> Due to the binary search, the last pr in this repo who can pass all junit
> tests is commit 967b9bed79f51040597d68ef98512a24b0e94e41 , which is at
> 6/11/2011,10:43PM
> Suggest revert all changes after that time point,
Just checking in on the status of the 1.1 release.
-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org
Done.
Environment win10, jdk8.
Due to the binary search, the last pr in this repo who can pass all junit
tests is commit 967b9bed79f51040597d68ef98512a24b0e94e41 , which is at
6/11/2011,10:43PM
Suggest revert all changes after that time point, and track them one by one.
A project which can never
Two failures and one error actually.
I will try to fetch the latest commit who CAN pass junit test, using binary
search.
Will send mail when I finish.
Gilles Sadowski 于2020年6月13日周六 上午6:21写道：
> Hi.
>
> 2020-06-12 21:43 UTC+02:00, Amey Jadiye :
> > On Fri, Jun 12, 2020 at 4:40 PM Gilles Sadowski
Here are several suggestions about usage of travis-ci (or github ci or
other ci like appveyor).
It is not legal or must do or something, but just several simple rules that
make everybody be happier when dealing with ci.
*1. Always have all LST versions tested from project.source to ea.*
For
Hi.
2020-06-12 21:43 UTC+02:00, Amey Jadiye :
> On Fri, Jun 12, 2020 at 4:40 PM Gilles Sadowski
> wrote:
>
>> 2020-06-12 12:32 UTC+02:00, Xeno Amess :
>> > Hi.
>> > I see the current travis-ci scripts.
>> > Do we really care only jdk8?
>> > Should we also add at some other jdk versions, at least
On Fri, Jun 12, 2020 at 4:40 PM Gilles Sadowski
wrote:
> 2020-06-12 12:32 UTC+02:00, Xeno Amess :
> > Hi.
> > I see the current travis-ci scripts.
> > Do we really care only jdk8?
> > Should we also add at some other jdk versions, at least adding openjdk11,
> > as it is a stable version?
> > Or
On 2020-06-12, Gilles Sadowski wrote:
> 2020-06-12 15:52 UTC+02:00, Xeno Amess :
>> But if Apache Commons is thought to be a whole project, I do think
>> the relationship between each of its components should be enforced.
The Commons project is the legal entity that binds people with similar
On 2020-06-12, Xeno Amess wrote:
> Hi.
>>> 2. How are commons projects related?
>> They are not necessarily related. Usually it is considered
>> a feature if a component has zero dependency (as it is was
>> easier to avoid "JAR hell").
>> However, there are also drawbacks, e.g. duplicating
2020-06-12 16:14 UTC+02:00, Xeno Amess :
>> Well, you had quite a few responses from me, for PRs
>> pertaining to "Commons Math"
> Indeed. And I think I learned a lot from you too. Thanks.
And I look forward to you staying around... :-)
>> even though that one I
>> qualify as a "zombie" project!
> Being on the PMC means that your VOTE is _binding_
> I think you are assuming that there is a lot of hierarchy, structure, and
> formalities that are just not here ;-)
Yep, indeed.
Gary Gregory 于2020年6月12日周五 下午10:34写道：
> On Fri, Jun 12, 2020 at 10:22 AM Xeno Amess wrote:
>
> > >> Speaking
On Fri, Jun 12, 2020 at 10:22 AM Xeno Amess wrote:
> >> Speaking for myself, as a volunteer here, I do what I can, when I can,
> with
> >> a eye toward using my time wisely while balancing many other
> >> responsibilities.
> >> Commons has over 20 components, some I use at work, some I used at
>> Speaking for myself, as a volunteer here, I do what I can, when I can,
with
>> a eye toward using my time wisely while balancing many other
>> responsibilities.
>> Commons has over 20 components, some I use at work, some I used at play,
>> some I do not use.
>> I do my best to pick low hanging
Hi.
2020-06-12 15:52 UTC+02:00, Xeno Amess :
>> Some terms:
>> - Apache Commons is an Apache _project_.
>> - Apache Commons Lang is a _component_ of the _project_.
>
>> Each component has its own level of functionality and granularity. Some
> are
>> lower level, like Commons Lang and Commons IO
> Well, you had quite a few responses from me, for PRs
> pertaining to "Commons Math"
Indeed. And I think I learned a lot from you too. Thanks.
> even though that one I
> qualify as a "zombie" project! [How it came to that
> state is told in the "dev" ML.]
Ah, I thought it be among the alive
Hi.
2020-06-12 15:44 UTC+02:00, Xeno Amess :
>>> 8. What should we do when we have a pr delayed for a long time? And how
>>> long is thought to be an unusual long time for waiting? 3 days.1 week,or
> 1
>>> month?
>
>> They might have been forgotten, or there may other issues.
>> Examples?
>
> for
> Speaking for myself, as a volunteer here, I do what I can, when I can,
with
> a eye toward using my time wisely while balancing many other
> responsibilities.
> Commons has over 20 components, some I use at work, some I used at play,
> some I do not use.
> I do my best to pick low hanging
> Hopefully we mean the same thing, but this is not
> true: Only those components for which a git repository
> was set up have their SVN set as read-only (by INFRA).
> See also my recent post asking how to finalize the
> move (to the "read-only area") of [Graph].
And maybe this is kind of off
On Fri, Jun 12, 2020 at 9:44 AM Xeno Amess wrote:
> >> 8. What should we do when we have a pr delayed for a long time? And how
> >> long is thought to be an unusual long time for waiting? 3 days.1 week,or
> 1
> >> month?
>
> > They might have been forgotten, or there may other issues.
> >
> Some terms:
> - Apache Commons is an Apache _project_.
> - Apache Commons Lang is a _component_ of the _project_.
> Each component has its own level of functionality and granularity. Some
are
> lower level, like Commons Lang and Commons IO and do not depend on
anything
> at runtime.
> Others
2020-06-12 15:36 UTC+02:00, Gary Gregory :
> On Fri, Jun 12, 2020 at 9:07 AM Gilles Sadowski
> wrote:
>
>> Hello.
>>
>> Le ven. 12 juin 2020 à 13:51, Xeno Amess a écrit :
>> >
>> > 1. How can a project *** becomes commons-***, or how did a commons-***
>> > project started? What is the actual
>> 8. What should we do when we have a pr delayed for a long time? And how
>> long is thought to be an unusual long time for waiting? 3 days.1 week,or
1
>> month?
> They might have been forgotten, or there may other issues.
> Examples?
for 1 year example:
On Fri, Jun 12, 2020 at 9:30 AM Xeno Amess wrote:
> Hi.
>
> >> 2. How are commons projects related?
>
> > They are not necessarily related. Usually it is considered
> > a feature if a component has zero dependency (as it is was
> > easier to avoid "JAR hell").
> > However, there are also
On Fri, Jun 12, 2020 at 9:07 AM Gilles Sadowski
wrote:
> Hello.
>
> Le ven. 12 juin 2020 à 13:51, Xeno Amess a écrit :
> >
> > 1. How can a project *** becomes commons-***, or how did a commons-***
> > project started? What is the actual procedural?
>
> For new components, this list would be
>> Are they under a same (or at least
>> similar) management mechanism? Or just sharing a common prefix?
> Do you mean the development tools (maven, git)?
> There some measure of "standardization" through the parent POM
> file, but nothing is really enforced. The code style depends on the
>
Hi.
>> 2. How are commons projects related?
> They are not necessarily related. Usually it is considered
> a feature if a component has zero dependency (as it is was
> easier to avoid "JAR hell").
> However, there are also drawbacks, e.g. duplicating functionality
> (and work) needed by several
Hello.
Le ven. 12 juin 2020 à 13:51, Xeno Amess a écrit :
>
> 1. How can a project *** becomes commons-***, or how did a commons-***
> project started? What is the actual procedural?
For new components, this list would be the place to make the
proposal. A discussion would decide if "Apache
1. How can a project *** becomes commons-***, or how did a commons-***
project started? What is the actual procedural?
2. How are commons projects related? Are they under a same (or at least
similar) management mechanism? Or just sharing a common prefix?
3. How is commons projects' version
On Fri, 12 Jun 2020 at 12:10, Gilles Sadowski wrote:
> 2020-06-12 12:32 UTC+02:00, Xeno Amess :
> > Hi.
> > I see the current travis-ci scripts.
> > Do we really care only jdk8?
> > Should we also add at some other jdk versions, at least adding openjdk11,
> > as it is a stable version?
> > Or
2020-06-12 12:32 UTC+02:00, Xeno Amess :
> Hi.
> I see the current travis-ci scripts.
> Do we really care only jdk8?
> Should we also add at some other jdk versions, at least adding openjdk11,
> as it is a stable version?
> Or this repo has some known bug on jdk11?
>
Before refining, we should
On Fri, 12 Jun 2020 at 11:33, Xeno Amess wrote:
> Hi.
> I see the current travis-ci scripts.
> Do we really care only jdk8?
> Should we also add at some other jdk versions, at least adding openjdk11,
> as it is a stable version?
> Or this repo has some known bug on jdk11?
>
Targeting the LTS
I made a minor change to the documentation. I'm not sure if I should have left
the issue open or marked it "Resolved." Right now, it's marked Resolved,
although "Patch Available" would be more appropriate, but I can't figure out
how to specify that resolution.
-- Miguel Munoz
Hi.
I see the current travis-ci scripts.
Do we really care only jdk8?
Should we also add at some other jdk versions, at least adding openjdk11,
as it is a stable version?
Or this repo has some known bug on jdk11?
38 matches
Mail list logo
