So the current management process in JIRA is a bit rusty, but is intended
to be (as in I used to do it that way but no reason why anyone else should):
New issue comes in (Version Unscheduled)
We assign it to a future version. We use 3.2 for 'yes, soon' and 3.x for
'later'.
It gets done with said
On 13/10/2013 23:59, sebb wrote:
On 13 October 2013 20:47, Phil Steitz phil.ste...@gmail.com wrote:
On 10/13/13 8:09 AM, James Carman wrote:
Well, it has been 72 hours, so let's tally up the votes. As I see it
(counting votes on both lists):
+1s
James Carman
Romain Manni-Bucau
Matt
On 14/10/2013 02:55, Henri Yandell wrote:
On Tuesday, October 8, 2013, Benedikt Ritter wrote:
Hi,
one of the points that seem to always come up once in a while is the
process of releasing components. I've never done it myself so I'm asking
people who have done it:
I find myself
On 14/10/2013 05:26, Stefan Bodewig wrote:
On 2013-10-14, sebb wrote:
On 9 October 2013 05:43, Stefan Bodewig bode...@apache.org wrote:
why vote on Nexus staged artifacts if the tarball is fine? I'm not
talking about releasing to MC directly but rather about not pushing
anything to Nexus
Le 14/10/2013 07:45, Henri Yandell a écrit :
On Sun, Oct 13, 2013 at 9:12 PM, Phil Steitz phil.ste...@gmail.com wrote:
Could be I am misunderstanding the proposal. Do you mean a) RM is
not obligated to do anything but tag a release and create tarballs
or b) RM should just be trusted to do
Le 14/10/2013 03:55, Henri Yandell a écrit :
I find myself wondering why a release vote is anything more than:
I propose that r6525 of dir be tagged as 3.2. What say ye all?
+1, assuming the revision has almost everything ready for a release (at
least up to date release notes).
That may
Le 14/10/2013 02:48, Gary Gregory a écrit :
One small step for man, one giant leap backward for mankind ;)
Should we vote to migrate back to Bugzilla then ? ;)
Emmanuel Bourg
-
To unsubscribe, e-mail:
Le 14/10/2013 08:06, Henri Yandell a écrit :
What do others think?
I quite like triaging the feature requests with a 'n.x' version and a
'(n+1).0' version. The former indicates that the request can be
implemented in a compatible manner, and the latter indicates this can't
be done without a
Le 14/10/2013 07:54, Henri Yandell a écrit :
Not all are open, I know #1 is in the code but I don't know how to close
the requests.
Excellent question. It seems the apache group on Github has no member:
https://github.com/apache?tab=members
I wonder if it's possible to add members while
On 2013-10-14, Henri Yandell wrote:
These are all sitting in our pull request queue:
https://github.com/apache/commons-lang/pulls?direction=descpage=1sort=createdstate=open
Not all are open, I know #1 is in the code but I don't know how to close
the requests.
In a similar situation in Ant
On Mon, Oct 14, 2013 at 12:16 AM, Mark Thomas ma...@apache.org wrote:
On 14/10/2013 02:55, Henri Yandell wrote:
On Tuesday, October 8, 2013, Benedikt Ritter wrote:
Hi,
one of the points that seem to always come up once in a while is the
process of releasing components. I've never
On Mon, Oct 14, 2013 at 1:19 AM, Emmanuel Bourg ebo...@apache.org wrote:
Le 14/10/2013 08:06, Henri Yandell a écrit :
What do others think?
I quite like triaging the feature requests with a 'n.x' version and a
'(n+1).0' version. The former indicates that the request can be
implemented in
On Mon, Oct 14, 2013 at 1:04 AM, Emmanuel Bourg ebo...@apache.org wrote:
Le 14/10/2013 02:48, Gary Gregory a écrit :
One small step for man, one giant leap backward for mankind ;)
Should we vote to migrate back to Bugzilla then ? ;)
Stick a big banner on the Apache JIRA saying Wow, this
On 14/10/2013 09:41, Henri Yandell wrote:
On Mon, Oct 14, 2013 at 12:16 AM, Mark Thomas ma...@apache.org wrote:
On 14/10/2013 02:55, Henri Yandell wrote:
On Tuesday, October 8, 2013, Benedikt Ritter wrote:
Hi,
one of the points that seem to always come up once in a while is the
process
Wearing my old Attic fart hat - something is dead when there is no one left
to turn the light out. Something is inactive when it couldn't pass a vote
to keep the project alive (ie: 3 +1s).
So that's one way to do this. Make a file in SVN. Put each component in it
(include the sandbox perhaps).
+1
Emmanuel Bourg
Le 09/10/2013 17:21, Emmanuel Bourg a écrit :
This is a vote to release Apache Commons JCI 1.1 based on RC1.
This is a bug fix release and an update to work with more recent
versions of its dependencies.
Tag:
This vote passes with five +1 votes from the following people:
Olivier Lamy
James Carman
Torsten Curdt
Matt Benson
Emmanuel Bourg
Thank you for your reviews, I'll proceed with the release.
Emmanuel Bourg
Le 09/10/2013 17:21, Emmanuel Bourg a écrit :
This is a vote to release Apache Commons
Thanks to the infra team we now have JIRA and svn commit notifications
on the channel. Enjoy :)
Emmanuel Bourg
Le 10/10/2013 18:15, James Carman a écrit :
As a reminder, we do have an IRC channel set up on freenode. It's
#asfcommons. Matt Benson and I are usually the only ones hanging out
On 14 Oct 2013, at 15:34, Emmanuel Bourg wrote:
Thanks to the infra team we now have JIRA and svn commit notifications
on the channel. Enjoy :)
boah thats cool! Thanks for organizing that! (assuming oyu did!)
Emmanuel Bourg
Le 10/10/2013 18:15, James Carman a écrit :
As a reminder, we
What (free) IRC client do you recommend for Windows (7)?
Gary
On Mon, Oct 14, 2013 at 9:34 AM, Emmanuel Bourg ebo...@apache.org wrote:
Thanks to the infra team we now have JIRA and svn commit notifications
on the channel. Enjoy :)
Emmanuel Bourg
Le 10/10/2013 18:15, James Carman a écrit :
I use X-Chat for Linux [1] and Windows [2]
[1] http://xchat.org
[2] http://www.silverex.org/news/
Bruno
From: Gary Gregory garydgreg...@gmail.com
To: Commons Developers List dev@commons.apache.org
Sent: Monday, October 14, 2013 10:53 AM
Subject: Re: Apache
Le 14/10/2013 15:53, Gary Gregory a écrit :
What (free) IRC client do you recommend for Windows (7)?
I just use Chatzilla, it's good enough for chatting. I bookmarked
irc://barjavel.freenode.net/asfcommons to join easily from Firefox.
https://addons.mozilla.org/en-US/firefox/addon/chatzilla/
There is an #apache-commons channel that was created a long time ago
when the previous Apache Commons project started. Daniel Gruno from
infra can manage to transfer is to us.
Channels prefixed with #asf are usually more foundation oriented, and
those with the #apache- prefix are usually for
wow, didn't know that... when Simo and I created the current channel (I'll
take blame here) I elected to call it asf-commons simply due to it's
being shorter than apache-commons and simply commons being too generic.
My vote is whatever. :)
Matt
On Mon, Oct 14, 2013 at 9:31 AM, Emmanuel Bourg
I don't really understand the difference to be honest... what would you
discuss on a more foundation related channel? I'm happy with #asfcommons
:-)
2013/10/14 Matt Benson gudnabr...@gmail.com
wow, didn't know that... when Simo and I created the current channel (I'll
take blame here) I
Well, e.g. #asfinfra and #asftac are committees under the foundation
hierarchy, as opposed to being tied to a PMC.
Matt
On Mon, Oct 14, 2013 at 10:18 AM, Benedikt Ritter brit...@apache.orgwrote:
I don't really understand the difference to be honest... what would you
discuss on a more
On 10/14/13 3:50 AM, ma...@apache.org wrote:
Author: markt
Date: Mon Oct 14 10:50:28 2013
New Revision: 1531846
URL: http://svn.apache.org/r1531846
Log:
Add CGLib proxy implementation and test.
Added:
Hi Hen,
anything that makes working through the issues easier is good. But I think
i don't understand your proposal completely. Do you want to create a new
version that is called feature requests? That would feel like duplicating
information available as ticket type.
As far as I understand
The said contributor was asked, but didn't respond. I guess we have to ask
infra or live with it :-)
2013/10/14 Stefan Bodewig bode...@apache.org
On 2013-10-14, Henri Yandell wrote:
These are all sitting in our pull request queue:
Just a couple of immediate thoughts (just starting to look things over...)
In SevenZFile.java
Constructor...
1) Close file on exception instead of the current technique of keeping
a succeeded flag.
2) Move setting the password to the last line of the constructor so
that it isn't stored if an
org.apache.commons.compress.compressors.lzma.LZMACompressorInputStream#read()
Current: count(ret == -1 ? -1 : 1);
Change: count(ret == -1 ? 0 : 1);
On Mon, Oct 14, 2013 at 12:17 AM, Stefan Bodewig bode...@apache.org wrote:
I think enough issues have been identified to warrant a second RC.
On Mon, Oct 14, 2013 at 12:03 PM, dam6923 . dam6...@gmail.com wrote:
Just a couple of immediate thoughts (just starting to look things over...)
In SevenZFile.java
Constructor...
1) Close file on exception instead of the current technique of keeping
a succeeded flag.
2) Move setting the
On 10/14/13 2:04 AM, Henri Yandell wrote:
Wearing my old Attic fart hat - something is dead when there is no one left
to turn the light out. Something is inactive when it couldn't pass a vote
to keep the project alive (ie: 3 +1s).
So that's one way to do this. Make a file in SVN. Put each
The nice thing about Hen's solution is, that I expect it to be better
structured. When 20 people begin voting on 30 different components it will
get confusing in that thread. Having one single file which contains the
result of the vote would be very easy.
How do you want to reach non commons
org.apache.commons.compress.archivers.ar.ArArchiveInputStream#getNextArEntry()
The code to skip to the next available entry looks a bit inefficient
because it reads one byte at a time in a loop. Consider using
org.apache.commons.compress.utils.IOUtils.skip(InputStream, long)
Consider using
On 10/14/13 9:18 AM, Benedikt Ritter wrote:
The nice thing about Hen's solution is, that I expect it to be better
structured. When 20 people begin voting on 30 different components it will
get confusing in that thread. Having one single file which contains the
result of the vote would be very
+1 to Phil's +1 meaning. :)
On Monday, October 14, 2013, Phil Steitz wrote:
On 10/14/13 9:18 AM, Benedikt Ritter wrote:
The nice thing about Hen's solution is, that I expect it to be better
structured. When 20 people begin voting on 30 different components it
will
get confusing in that
On 14 October 2013 11:50, ma...@apache.org wrote:
Author: markt
Date: Mon Oct 14 10:50:28 2013
New Revision: 1531846
URL: http://svn.apache.org/r1531846
Log:
Add CGLib proxy implementation and test.
Added:
Hi all,
Please welcome Ate Douma and Woonsan Ko as a new committers of the
Apache Commons project. The Commons PMC has voted to grant committership
to them and they accepted.
Both accounts have already been set up and they can begin working
on the Commons components.
Ate and Woonsan, welcome to
Welcome aboard Ate and Woonsan!
Gary
On Mon, Oct 14, 2013 at 1:51 PM, Luc Maisonobe l...@spaceroots.org wrote:
Hi all,
Please welcome Ate Douma and Woonsan Ko as a new committers of the
Apache Commons project. The Commons PMC has voted to grant committership
to them and they accepted.
Congratulations to Ate Douma and Woonsan Ko!
Adrian Crum
Sandglass Software
www.sandglass-software.com
On 10/14/2013 10:51 AM, Luc Maisonobe wrote:
Hi all,
Please welcome Ate Douma and Woonsan Ko as a new committers of the
Apache Commons project. The Commons PMC has voted to grant
Welcome, guys!
Matt
On Mon, Oct 14, 2013 at 1:10 PM, Adrian Crum
adrian.c...@sandglass-software.com wrote:
Congratulations to Ate Douma and Woonsan Ko!
Adrian Crum
Sandglass Software
www.sandglass-software.com
On 10/14/2013 10:51 AM, Luc Maisonobe wrote:
Hi all,
Please welcome Ate
Hey,
please review http://svn.apache.org/r1532011
I was thinking about deprecating Validate.notNull(T) as well because we now
have Objects.requireNotNull(Object). The problem is that Validate has
notNull(T, String, Object...) which does substitution in the message, while
Objects only has
Hi Benedikt, see inline:
On Mon, Oct 14, 2013 at 1:15 PM, brit...@apache.org wrote:
Author: britter
Date: Mon Oct 14 18:15:39 2013
New Revision: 1532011
URL: http://svn.apache.org/r1532011
Log:
Deprecate methods that are available in Java 7's java.lang.Objects
Modified:
Thank you all for the trust and the warm welcome!
Regards, Ate
On 10/14/2013 07:51 PM, Luc Maisonobe wrote:
Hi all,
Please welcome Ate Douma and Woonsan Ko as a new committers of the
Apache Commons project. The Commons PMC has voted to grant committership
to them and they accepted.
Both
2013/10/14 Matt Benson gudnabr...@gmail.com
Hi Benedikt, see inline:
On Mon, Oct 14, 2013 at 1:15 PM, brit...@apache.org wrote:
Author: britter
Date: Mon Oct 14 18:15:39 2013
New Revision: 1532011
URL: http://svn.apache.org/r1532011
Log:
Deprecate methods that are available in
Hi Matt,
(fired the last one without adding my comment :-)
2013/10/14 Benedikt Ritter benerit...@gmail.com
2013/10/14 Matt Benson gudnabr...@gmail.com
Hi Benedikt, see inline:
On Mon, Oct 14, 2013 at 1:15 PM, brit...@apache.org wrote:
Author: britter
Date: Mon Oct 14 18:15:39
Can someone add my wiki name (AteDouma) to the Contributors Group page [1]?
Thanks, Ate
[1] https://wiki.apache.org/commons/ContributorsGroup
-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional
Hi All,
Thank you so much for your warm welcome and allowing me to work for Apache
Commons.
I hope to help revive SCXML project and build a strong community around it.
Cheers,
Woonsan
On Monday, October 14, 2013 1:52 PM, Luc Maisonobe l...@spaceroots.org wrote:
Hi all,
Please welcome
On 14/10/2013 17:59, sebb wrote:
Added:
commons/proper/pool/trunk/src/main/java/org/apache/commons/pool2/proxy/CglibProxyHandler.java
URL:
http://svn.apache.org/viewvc/commons/proper/pool/trunk/src/main/java/org/apache/commons/pool2/proxy/CglibProxyHandler.java?rev=1531846view=auto
Thoughts? Maybe this should be renamed to isOneTrue(boolean...) in the
next major release?!
-- Forwarded message --
From: brit...@apache.org
Date: 2013/10/14
Subject: svn commit: r1532031 -
/commons/proper/lang/trunk/src/main/java/org/apache/commons/lang3/BooleanUtils.java
To:
Hi Commons team,
Can someone grant me, and likewise for Woonsan, committer karma in JIRA for at
least Commons SCXML so we can start picking up and assigning issues?
Thanks, Ate
-
To unsubscribe, e-mail:
On 10/14/2013 09:23 PM, Ate Douma wrote:
Hi Commons team,
Can someone grant me, and likewise for Woonsan, committer karma in JIRA for at
least Commons SCXML so we can start picking up and assigning issues?
Forgot to mention my ASF JIRA handle is: adouma
and for Woonsan: woon_san
Thanks,
Am 14.10.2013 06:11, schrieb Stefan Bodewig:
On 2013-10-13, Oliver Heger wrote:
The artifacts look good, the build works fine with Java 1.7 on Windows
7. I tried to build with Java 1.5, but got:
Tests in error:
On 14/10/2013 20:27, Ate Douma wrote:
On 10/14/2013 09:23 PM, Ate Douma wrote:
Hi Commons team,
Can someone grant me, and likewise for Woonsan, committer karma in
JIRA for at
least Commons SCXML so we can start picking up and assigning issues?
Forgot to mention my ASF JIRA handle is:
On 10/14/2013 09:33 PM, Mark Thomas wrote:
On 14/10/2013 20:27, Ate Douma wrote:
On 10/14/2013 09:23 PM, Ate Douma wrote:
Hi Commons team,
Can someone grant me, and likewise for Woonsan, committer karma in
JIRA for at
least Commons SCXML so we can start picking up and assigning issues?
Good idea!
2013/10/14 ohe...@apache.org
Author: oheger
Date: Mon Oct 14 19:44:55 2013
New Revision: 1532038
URL: http://svn.apache.org/r1532038
Log:
Created a branch for adding generics and Java5 features.
Added:
commons/proper/beanutils/branches/java5/
- copied from
On 2013-10-14, Oliver Heger wrote:
Am 14.10.2013 06:11, schrieb Stefan Bodewig:
On 2013-10-13, Oliver Heger wrote:
When I build the site locally, I get a different clirr report showing 9
errors because some public methods have been made final.
Strange. Why would Clirr create different
Could make more sense in 2013 to have generics in trunk and move previous
trunk in a maintenance branch.
?
--
Olivier
On Oct 15, 2013 6:46 AM, Benedikt Ritter brit...@apache.org wrote:
Good idea!
2013/10/14 ohe...@apache.org
Author: oheger
Date: Mon Oct 14 19:44:55 2013
New Revision:
Hi SCXML community,
I'd like to propose dropping Ant build support for the next major SCXML version
1.0, which development now has been reactivated on trunk.
Both Woonsan and myself are 'Maven' adepts, and have no use nor interest in
maintaining and updating/fixing the already outdated Ant
On 10/14/13 1:42 PM, ma...@apache.org wrote:
Author: markt
Date: Mon Oct 14 20:42:03 2013
New Revision: 1532083
URL: http://svn.apache.org/r1532083
Log:
Fix some FindBugs warnings
Modified:
I'm +1 for this, but I think there are components that need this ant build for
Debian packages... probably someone else can chime in and confirm if that's the
case for scxml.
Cheers,
Bruno P. Kinoshita
http://kinoshita.eti.br
http://tupilabs.com
- Original Message -
From: Ate
Le 14/10/2013 22:51, Bruno P. Kinoshita a écrit :
I'm +1 for this, but I think there are components that need this ant build
for Debian packages... probably someone else can chime in and confirm if
that's the case for scxml.
I did say the Ant build was used for some Debian packages, but
Am 14.10.2013, 23:22 Uhr, schrieb Emmanuel Bourg ebo...@apache.org:
I did say the Ant build was used for some Debian packages, but scxml
isn't in Debian yet and I'm updating the packages to use Maven instead.
So go for it.
Do you use a deb-builder script or similiar to package those or do you
Le 14/10/2013 23:38, Bernd Eckenfels a écrit :
Do you use a deb-builder script or similiar to package those or do you
use unix:deb or assembly for that inside maven?
For the official packages I use maven-repo-helper [1] and
maven-debian-helper [2]. It configures Maven to run in offline mode
The Apache Commons Team is pleased to announce the release of Apache
Commons JCI 1.1.
JCI is a java compiler interface. It can be used to either compile java
(or any other language that can be compiled to java classes like e.g.
groovy or javascript) to Java.
Changes in this version:
o Updated
On Mon, Oct 14, 2013 at 8:56 AM, Benedikt Ritter brit...@apache.org wrote:
Hi Hen,
anything that makes working through the issues easier is good. But I think
i don't understand your proposal completely. Do you want to create a new
version that is called feature requests? That would feel like
One reason I like this, apart from the general visualization of the state
of our todo group, is that it gives us a very nice way to point new
contributors to potential work. We point them at the Code Needed version,
with a strong expectation that the patch they provide will go in (as an
issue we
I contend that all of the Commons components are inactive and should move
to the Attic/Dormant. In line with Phil's recent suggestion that anyone can
present a dormancy challenge at any time, I'm challenging all of Commons
Proper.
I've made a file in SVN:
I agree it would be strange. I think we consider this as a duplication to
keep. Deprecating and removing one method out of Validate isn't going to
simplify its API, and I wouldn't expect users to be using it for only that
one method.
So -1 to deprecation of Validate.notNull(...).
Hen
On Mon,
I think we treat it as a bug and fix. The code is fine for the explained
use of an array of length 2, but fails when you move to larger chains.
Given the common meaning of the name, I think people would have noticed if
they'd needed xor to work for arrays 2 and it didn't. So a) I think we
can fix
I just assigned myself a few issues. This doesn't mean anything
more than that I am working on them, i.e., should not discourage
anyone from also working on them. It just helps me keep track of
what I want to get to next.
Phil
On 10/14/13 8:55 PM, Henri Yandell wrote:
I contend that all of the Commons components are inactive and should move
to the Attic/Dormant. In line with Phil's recent suggestion that anyone can
present a dormancy challenge at any time, I'm challenging all of Commons
Proper.
I've made a file in
I am willing to help out with CSV. ID = adrianc.
Adrian Crum
Sandglass Software
www.sandglass-software.com
On 10/14/2013 9:14 PM, Phil Steitz wrote:
On 10/14/13 8:55 PM, Henri Yandell wrote:
I contend that all of the Commons components are inactive and should move
to the Attic/Dormant. In
On 10/14/13 9:14 PM, Phil Steitz wrote:
On 10/14/13 8:55 PM, Henri Yandell wrote:
I contend that all of the Commons components are inactive and should move
to the Attic/Dormant. In line with Phil's recent suggestion that anyone can
present a dormancy challenge at any time, I'm challenging all
On 10/14/13 9:26 PM, Adrian Crum wrote:
I am willing to help out with CSV. ID = adrianc.
Done :)
Phil
Adrian Crum
Sandglass Software
www.sandglass-software.com
On 10/14/2013 9:14 PM, Phil Steitz wrote:
On 10/14/13 8:55 PM, Henri Yandell wrote:
I contend that all of the Commons components
Thanks! I'm a committer in the sandbox, but I haven't ventured into
proper yet. I was hoping to get Commons Convert promoted to proper
someday. In the meantime I would be happy to work on CSV.
Adrian Crum
Sandglass Software
www.sandglass-software.com
On 10/14/2013 9:32 PM, Phil Steitz wrote:
svn co -N https://svn.apache.org/repos/asf/commons/trunks-proper
Happy to move it, also happy to have people pick up a bit of SVN usefulness
:)
I've lifted the definition to:
(you monitor commits, JIRA, mail, and develop code for that component)
On Mon, Oct 14, 2013 at 9:27 PM, Phil Steitz
I vote -1 to this process. I see no value in attic-izing projects.
On 10/14/2013 11:55 PM, Henri Yandell wrote:
I contend that all of the Commons components are inactive and should move
to the Attic/Dormant. In line with Phil's recent suggestion that anyone can
present a dormancy challenge at
Three values jump out to me:
* First is for our users. Having code available that no one is supporting
while giving the appearance of support (ie: active Commons) is a bad
experience.
* Second (generally for the ASF) is that if we have code we can't maintain,
because there is no one who can
Perhaps for new users, however there are lots of projects currently
using these libraries. We are extending the middle finger to them by
doing this. I would come away thinking i'm not going to risk using any
Apache library, if I they will just yank away the next project i choose
to use
Am 15.10.2013 um 07:14 schrieb Dave Brosius dbros...@apache.org:
Perhaps for new users, however there are lots of projects currently using
these libraries. We are extending the middle finger to them by doing this. I
would come away thinking i'm not going to risk using any Apache library,
I couldn't disagree more. Dormant/attic means the project has leprosy. I
don't know the answer to this, but wondering, has there ever been a
commit to an attic'ed project? I personally would never think of doing that.
On 10/15/2013 01:22 AM, Benedikt Ritter wrote:
Am 15.10.2013 um 07:14
On 10/14/13 9:59 PM, Henri Yandell wrote:
Three values jump out to me:
* First is for our users. Having code available that no one is supporting
while giving the appearance of support (ie: active Commons) is a bad
experience.
* Second (generally for the ASF) is that if we have code we can't
On 10/14/13 10:33 PM, Dave Brosius wrote:
I couldn't disagree more. Dormant/attic means the project has
leprosy. I don't know the answer to this, but wondering, has there
ever been a commit to an attic'ed project? I personally would
never think of doing that.
There have been commons
85 matches
Mail list logo
