Thanks Jonas,
would you submit a patch for that? TIA!
-Simo
http://people.apache.org/~simonetripodi/
http://twitter.com/simonetripodi
On Thu, Jun 20, 2013 at 11:09 PM, Jonas Sprenger sprenger...@gmail.com wrote:
Hi guys,
so we talk about an enum 'PROCESSING' providing at least 3 states?
Hi Gary,
nice to see some activity in CSV again. We were talking about reverting
CSVFormat back to the old API that does not use the builder pattern, see
CSV-99[1].
We still have 18 unresolved issues. I think we should go through all those
issues and decide if we want to have them in 1.0.
2013/6/21 Simone Tripodi simonetrip...@apache.org
Thanks Jonas,
would you submit a patch for that? TIA!
-Simo
http://people.apache.org/~simonetripodi/
http://twitter.com/simonetripodi
On Thu, Jun 20, 2013 at 11:09 PM, Jonas Sprenger sprenger...@gmail.com
wrote:
Hi guys,
so we
2013/6/20 Simone Tripodi simonetrip...@apache.org
On Thu, Jun 20, 2013 at 4:06 PM, sebb seb...@gmail.com wrote:
On 20 June 2013 14:48, Simone Tripodi simonetrip...@apache.org wrote:
Don't you think it would worth at least announcing it, before moving a
component from sandbox to proper?
On 21 June 2013 07:54, Benedikt Ritter brit...@apache.org wrote:
Hi Gary,
nice to see some activity in CSV again. We were talking about reverting
CSVFormat back to the old API that does not use the builder pattern, see
CSV-99[1].
We still have 18 unresolved issues. I think we should go
On 21 June 2013 07:59, Benedikt Ritter brit...@apache.org wrote:
2013/6/20 Simone Tripodi simonetrip...@apache.org
On Thu, Jun 20, 2013 at 4:06 PM, sebb seb...@gmail.com wrote:
On 20 June 2013 14:48, Simone Tripodi simonetrip...@apache.org wrote:
Don't you think it would worth at least
This is a vote to release Apache Commons Digest Plugin based on RC2
This is the initial release of the digest plugin, which creates MD5
and SHA1 hashes for whatever files you specify.
The code is not expected to be perfect in this release.
So long as it is usable (and the release is valid) I'd
+1
Emmanuel
Le 21/06/2013 10:54, sebb a écrit :
This is a vote to release Apache Commons Digest Plugin based on RC2
This is the initial release of the digest plugin, which creates MD5
and SHA1 hashes for whatever files you specify.
The code is not expected to be perfect in this release.
Unfortunately I've just discovered that pom.xml does not have an AL header.
Not sure how that happened; I'm fairly sure I copied it from an
existing project ...
Sorry, I should have checked the RAT report ...
Also discovered that the download page was missing; that could have
been fixed after
I'm not sure if we need ABORTED. What is the difference between COMPLETE
and ABORTED from the PoV of the Chain? Chain defines an algorithm for
processing and I currently don't see how ABORTED fits in there.
OTOH I see some potential here:
* COMPLETE: all chain commands have completed their
So are your canceling this vote due to the header issue?
Gary
On Jun 21, 2013, at 4:55, sebb seb...@gmail.com wrote:
This is a vote to release Apache Commons Digest Plugin based on RC2
This is the initial release of the digest plugin, which creates MD5
and SHA1 hashes for whatever files you
Yes, I thought I just did.
On 21 June 2013 13:19, Gary Gregory garydgreg...@gmail.com wrote:
So are your canceling this vote due to the header issue?
Gary
On Jun 21, 2013, at 4:55, sebb seb...@gmail.com wrote:
This is a vote to release Apache Commons Digest Plugin based on RC2
This is
On Fri, Jun 21, 2013 at 8:51 AM, sebb seb...@gmail.com wrote:
Yes, I thought I just did.
I thought we email a [CANCEL][VOTE] email when that happens to make it
clear.
Gary
On 21 June 2013 13:19, Gary Gregory garydgreg...@gmail.com wrote:
So are your canceling this vote due to the header
As already advised - missing AL header.
On 21 June 2013 09:54, sebb seb...@gmail.com wrote:
This is a vote to release Apache Commons Digest Plugin based on RC2
This is the initial release of the digest plugin, which creates MD5
and SHA1 hashes for whatever files you specify.
The code is not
Hi,
we are unsure about the process of promoting a component from sandbox to
proper. Can this be done by simply announcing it or has a vote to take
place? How has this been done in the past?
Regards,
Benedikt
2013/6/21 sebb seb...@gmail.com
On 21 June 2013 07:59, Benedikt Ritter
I'm not retroactively -1ing anything, but don't we typically have a formal
vote for moving any component from sandbox to proper? What was different
about these plugins?
Thanks,
Matt
On Thu, Jun 20, 2013 at 9:06 AM, sebb seb...@gmail.com wrote:
On 20 June 2013 14:43, Gary Gregory
Le 21/06/2013 15:29, Benedikt Ritter a écrit :
we are unsure about the process of promoting a component from sandbox to
proper. Can this be done by simply announcing it or has a vote to take
place? How has this been done in the past?
What about merging the sandbox with proper? That would be
On 21 June 2013 14:29, Benedikt Ritter brit...@apache.org wrote:
Hi,
we are unsure about the process of promoting a component from sandbox to
proper. Can this be done by simply announcing it or has a vote to take
place? How has this been done in the past?
I suspect the answer is - it
Heh, I just added a similar question to the plugins thread. Happy to let
this thread rule them all, as it were.
Matt
On Fri, Jun 21, 2013 at 8:29 AM, Benedikt Ritter brit...@apache.org wrote:
Hi,
we are unsure about the process of promoting a component from sandbox to
proper. Can this be
On 21 June 2013 14:36, Emmanuel Bourg ebo...@apache.org wrote:
Le 21/06/2013 15:29, Benedikt Ritter a écrit :
we are unsure about the process of promoting a component from sandbox to
proper. Can this be done by simply announcing it or has a vote to take
place? How has this been done in the
Le 21/06/2013 15:45, sebb a écrit :
we want to be able to drop sandboxes easily.
How would that make dropping an experimental component more difficult?
also sandboxes can be used by non-Commons committers
Commit access could be open to all Apache committers on proper as well.
I trust the
On 21 June 2013 14:57, Emmanuel Bourg ebo...@apache.org wrote:
Le 21/06/2013 15:45, sebb a écrit :
we want to be able to drop sandboxes easily.
How would that make dropping an experimental component more difficult?
It would have to be removed from the website navigation.
Also, I don't think
[I'm not sure a vote for this is really needed, but]
I'd like to move the staging plugin from the sandbox to commons
proper, so it can be released for use by Commons.
The component name is currently
commons-staging-plugin
I propose to keep the same name unless there are objections.
The vote
Le 21/06/2013 16:02, sebb a écrit :
Also, I don't think we should have code under proper that is not
likely to be supported going forward.
Users have the expectation that code under proper is mature and supported.
It's doesn't prevent announcing a component as experimental with a clear
I prefer the distinct separation between sandbox and proper (although I've
never understood why the word proper was chosen).
As for moving components I would suggest starting a DISCUSS thread and then, if
appropriate, move to a vote thread.
Ralph
On Jun 21, 2013, at 7:22 AM, Emmanuel Bourg
On 21 June 2013 16:34, Ralph Goers ralph.go...@dslextreme.com wrote:
I prefer the distinct separation between sandbox and proper (although I've
never understood why the word proper was chosen).
+1
As for moving components I would suggest starting a DISCUSS thread and then,
if appropriate,
Le 2013-06-21 16:06, sebb a écrit :
[I'm not sure a vote for this is really needed, but]
I'd like to move the staging plugin from the sandbox to commons
proper, so it can be released for use by Commons.
+1
The component name is currently
commons-staging-plugin
I propose to keep the same
Le 2013-06-21 17:34, Ralph Goers a écrit :
I prefer the distinct separation between sandbox and proper (although
I've never understood why the word proper was chosen).
I agree for two different reasons.
The first one was already given by Sebb: users expect commons proper to
be mature and
On 6/21/13 10:45 AM, luc wrote:
Le 2013-06-21 17:34, Ralph Goers a écrit :
I prefer the distinct separation between sandbox and proper
(although
I've never understood why the word proper was chosen).
I agree for two different reasons.
The first one was already given by Sebb: users expect
Hello Sebb,
I very much appreciate your effort to ease the release process (although I've
never been RM).
I'd like to see some tests in the plugin. The code should meet the same quality
requirements we put on other proper components (although it is intended to be
used only for releasing
On Wed, Jun 19, 2013 at 3:12 AM, Julien Aymé julien.a...@gmail.com wrote:
Hi everyone,
I've used sshd from mina at work
(http://mina.apache.org/sshd-project/index.html), and I found the api
really attractive.
In sshd there is already a SFTP server implemented, but there is no
SFTP
On 21 June 2013 19:45, Benedikt Ritter benerit...@gmail.com wrote:
Hello Sebb,
I very much appreciate your effort to ease the release process (although I've
never been RM).
Thanks.
I'd like to see some tests in the plugin. The code should meet the same
quality requirements we put on
This is a vote to release Apache Commons Digest Plugin 0.1 based on RC2
This is the initial release of the digest plugin, which creates MD5
and SHA1 hashes for whatever files you specify.
The code is not expected to be perfect in this release.
So long as it is usable (and the release is valid)
Hi Simone,
more meat as I expected, thats for sure.
I will provide a patch for
CHAIN-98https://issues.apache.org/jira/browse/CHAIN-98tomorow. The
patch will only cover the refactoring of CONTINUE and
COMPLETED processing results.
But, I do not understand how exceptions should be handled in this
-0
I don't think this sort of things belongs in Commons proper as a
component. What we advertise, release and support from commons
proper are general purpose libraries that developers can use in
their own applications. This is what Commons was created for.
While the staging plugin looks like a
I've submitted a patch for the issue (see MATH-994). This will allow users
to integrate functions with infinity as one of the bounds.
Cheers,
Ajo Fod.
36 matches
Mail list logo
