> Am 24.09.2017 um 02:50 schrieb Rob Tompkins :
>
> The following votes were case:
>
> Gary Gregory +1 (binding)
> Oliver Heger +1 (binding)
> Rob Tompkins +1 (binding)
>
> Thus, the vote passes.
>
> Many thanks to all who voted. I will proceed with the release processing.
Good job! Sorry, I
Am 24.09.2017 um 18:31 schrieb sebb:
The document is missing a step (just added).
Thanks!
I have added the same redirects for commons discovery.
Cheers,
Pascal
-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For
On 24 September 2017 at 13:35, Pascal Schumacher
wrote:
> Am 24.09.2017 um 14:31 schrieb sebb:
>>>
>>> to:
>>> https://svn.apache.org/repos/asf/commons/dormant/launcher
>>>
>>> Synchronization of the git mirror
>>> (git://git.apache.org/commons-launcher.git) has been deactivated.
>>>
>>> The websi
Github user arunvinudss commented on the issue:
https://github.com/apache/commons-text/pull/64
Hey @PascalSchumacher! In my understanding we didn't make a decision yet. A
part of the reason is that it was exposed as a public method and since
consumers would potentially lose a function
Github user arunvinudss commented on the issue:
https://github.com/apache/commons-text/pull/65
Hey @PascalSchumacher ! I looked at a couple of other commons projects but
seems like we don't have and/or follow a standard for pom files. Each have
their own way of listing things.
Github user PascalSchumacher commented on the issue:
https://github.com/apache/commons-text/pull/64
Thanks for the pull request.
Imho we should make it absolutely clear that users should not use this
method. Therefore I'm against making the formulation "softer".
---
---
Github user PascalSchumacher commented on the issue:
https://github.com/apache/commons-text/pull/65
Thanks for the suggestion, but I'm against merging this, as this makes the
order different from other commons projects.
Replacing `/>` with `>` makes no sense imho (why make xml
Github user coveralls commented on the issue:
https://github.com/apache/commons-text/pull/65
[](https://coveralls.io/builds/13407074)
Coverage remained the same at 98.236% when pulling
**d293d605353509f88b0468
GitHub user arunvinudss opened a pull request:
https://github.com/apache/commons-text/pull/65
Sort pom file
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/arunvinudss/commons-text sort-pom-file
Alternatively you can review and
Github user coveralls commented on the issue:
https://github.com/apache/commons-text/pull/64
[](https://coveralls.io/builds/13407041)
Coverage remained the same at 98.236% when pulling
**f972a5b87f57ac93476bf3
GitHub user arunvinudss opened a pull request:
https://github.com/apache/commons-text/pull/64
Minor JavaDoc change for deprecated isDelimiter
@chtompki Please review and merge.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/arunv
Le 24/09/2017 à 14:28, sebb a écrit :
> I would be inclined to leave it open.
> Might be useful to collect reports against the component, even if
> nothing is planned to be done with them at present.
+1
Emmanuel Bourg
-
To unsu
Infra deactivated the github mirror a few weeks ago.
Cheers,
Pascal
Am 21.08.2017 um 08:34 schrieb Benedikt Ritter:
Am 20.08.2017 um 12:30 schrieb Pascal Schumacher :
Hello everybody,
there is a jira issue https://issues.apache.org/jira/browse/TRANSACTION-39 from
2010 with the steps to move
Am 24.09.2017 um 14:31 schrieb sebb:
to:
https://svn.apache.org/repos/asf/commons/dormant/launcher
Synchronization of the git mirror
(git://git.apache.org/commons-launcher.git) has been deactivated.
The website has moved from:
http://commons.apache.org/proper/commons-launcher/
There ought to b
commons discovery already had this JIRA description:
"RELEASE PLAN: Project considered to be dormant - no release planned. "
I copied this for commons launcher.
Am 24.09.2017 um 14:28 schrieb sebb:
The Attic is only for TLPs, not components of a TLP.
It's up to the Commons PMC whether or not
On 24 September 2017 at 13:12, Pascal Schumacher
wrote:
> Hi,
>
> since no development has happened for a long while, the Apache Commons
> Launcher component
> has been moved to dormant. No further development is expected.
>
> The SVN location has changed from:
> https://svn.apache.org/repos/asf/c
The Attic is only for TLPs, not components of a TLP.
It's up to the Commons PMC whether or not JIRA should be made read-only.
I would be inclined to leave it open.
Might be useful to collect reports against the component, even if
nothing is planned to be done with them at present.
Perhaps update
Hi,
since no development has happened for a long while, the Apache Commons
Launcher component
has been moved to dormant. No further development is expected.
The SVN location has changed from:
https://svn.apache.org/repos/asf/commons/proper/launcher
to:
https://svn.apache.org/repos/asf/commons/
Hi,
since no development has happened for a long while, the Apache Commons
Discovery component
has been moved to dormant. No further development is expected.
The SVN location has changed from:
https://svn.apache.org/repos/asf/commons/proper/discovery
to:
https://svn.apache.org/repos/asf/commons/
Hi,
since no development has happened for a long while, the Apache Commons
Discovery component
has been moved to dormant. No further development is expected.
The SVN location has changed from:
https://svn.apache.org/repos/asf/commons/proper/discovery
to:
https://svn.apache.org/repos/asf/common
I think dormant means no activity, but anyone could try to restart work on the
component (tho I could be wrong).
So maybe we should do it when moving to the attic instead?
Bruno
Sent from Yahoo Mail on Android
On Sun, 24 Sep 2017 at 21:42, Pascal Schumacher
wrote: Hello everybody,
my un
Hello everybody,
my understanding is that the JIRA of dormant components should be made
read-only.
Is that correct? (I'm asking because
https://commons.apache.org/releases/moving-to-dormant.html does not
mention this.)
Thanks,
Pascal
-
As announced on the list, I would like to release the [jcs] component to
resolve a cdi performance issue (
https://issues.apache.org/jira/browse/JCS-183).
Maven artifacts are at:
https://repository.apache.org/content/repositories/orgapachecommons-1269/
The Subversion tag is:
http://svn.apache.o
23 matches
Mail list logo
