Re: [jexl] 3.1 release review

[sebb]

On 14 March 2017 at 03:49, Matt Sicker  wrote:
> Using interfaces and implementing them are two entirely separate things.

Good point; sorry I had overlooked the distinction.

If there are no external implementions (yet) then I agree it should be
OK to release with the existing caveat in the RN.

It would probably be a good idea to warn consumers (in the Javadoc)
that these IFs are not intended for implementation.
Likewise for any other IFs that are intended for use only.

> For instance, people use Logger instances, but we've added new APIs to that
> interface in log4j-api while maintaining backwards compatibility (though we
> do that by providing abstract base classes for implementations to use).

Unfortunately I don't think that can be done here.

> On 13 March 2017 at 21:08, sebb  wrote:
>
>> On 14 March 2017 at 01:38, Matt Sicker  wrote:
>> > If they're not user-implemented interfaces, then changing them isn't
>> really
>> > a backwards incompatible change.
>>
>> I agree, but since users asked for the changes to the interfaces that
>> suggests that the interfaces are being used externally.
>>
>> > On 13 March 2017 at 17:50, sebb  wrote:
>> >
>> >> On 13 March 2017 at 20:12, henrib  wrote:
>> >> >
>> >> > The interface modifications are fixes to user enhancement requests:
>> >> >
>> >> > JEXL-211: Add callable method to JexlExpression interface
>> >> > JEXL-198: JxltEngine Template deos not expose pragmas
>> >> > JEXL-201: Allow Interpreter to use live values from JexlEngine.Option
>> >> > interface implemented by JexlContext
>> >> >
>> >> > Note again that these interfaces are *not* expected to be implemented
>> by
>> >> > user code.
>> >>
>> >> I'm not sure I understand how that follows.
>> >>
>> >> If the JIRAs are enhancement requests for users, surely the intention
>> >> is to allow the users to make use of the new methods?
>> >>
>> >> That suggests that the users are currently using the interfaces.
>> >>
>> >> > The likelihood of any user implementing those and not filling
>> >> > enhancements requests or even asking questions in the Apache mailing
>> >> lists
>> >> > (or Stackoverflow) seems very small...
>> >>
>> >> Sorry, no idea what you mean by that.
>> >>
>> >> > Choice is please (the few) users using the library or stay true to a
>> rule
>> >> > that protects no real usage in this case. I wish this was seen as an
>> easy
>> >> > choice for the community.
>> >>
>> >> Nor that.
>> >>
>> >> > Cheers
>> >> >
>> >> >
>> >> >
>> >> > --
>> >> > View this message in context: http://apache-commons.680414.
>> >> n4.nabble.com/jexl-3-1-release-review-tp4691513p4696492.html
>> >> > Sent from the Commons - Dev mailing list archive at Nabble.com.
>> >> >
>> >> > -
>> >> > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
>> >> > For additional commands, e-mail: dev-h...@commons.apache.org
>> >> >
>> >>
>> >> -
>> >> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
>> >> For additional commands, e-mail: dev-h...@commons.apache.org
>> >>
>> >>
>> >
>> >
>> > --
>> > Matt Sicker 
>>
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
>> For additional commands, e-mail: dev-h...@commons.apache.org
>>
>>
>
>
> --
> Matt Sicker 

-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org

[lang] fix for LANG-1310

[don jeba]

Hello,    The fix meant for the bug LANG-1310 is now available for review.

https://github.com/apache/commons-lang/pull/256

Can you kindly review and comment.
Thank you,
Regards,Don Jeba.

Re: [ANNOUNCE] Apache Commons Text 1.0 released!

[Rob Tompkins]

Thanks. Honestly, my (our) success here is directly tied to the encouragement 
and support of everyone in the community.

-Rob

> On Mar 13, 2017, at 6:53 PM, Gary Gregory  wrote:
> 
> +1
> 
> Gary
> 
> On Mar 13, 2017 6:55 PM, "Benedikt Ritter"  wrote:
> 
>> Kudos to Rob for getting this release out of the door!
>> 
>>> Am 13.03.2017 um 13:27 schrieb Rob Tompkins :
>>> 
>>> The Apache Commons Team is pleased to announce the release of
>>> Apache Commons Text 1.0.
>>> 
>>> The Apache Commons Text open source software library provides a host of
>>> algorithms focused on working with strings and blocks of text.
>>> 
>>> Notes.
>>> (a) In 1.0 the package names are the expected
>> "org.apache.commons.text.*";
>>>  whereas, in 1.0-beta-1 they were "org.apache.commons.text.beta.*."
>>> (b) The source and binary distributions' RELEASE-NOTES.txt contains a
>>>  typographical error on line 29, where "1.0-beta-1" should be replaced
>>>  by "1.0." We have fixed this in all locations other than inside the
>>>  distributions.
>>> 
>>> Source and binary distributions are available for download from the
>> Apache
>>> Commons download site:
>>> http://commons.apache.org/proper/commons-text/download_text.cgi
>>> 
>>> When downloading, please verify signatures using the KEYS file available
>> at
>>> the above location when downloading the release.
>>> 
>>> Alternatively the release can be pulled via maven:
>>> org.apache.commons
>>> commons-text
>>> 1.0
>>> 
>>> The corrected release notes can be reviewed at:
>>> http://www.apache.org/dist/commons/text/RELEASE-NOTES.txt
>>> 
>>> For complete information on Commons Text, including instructions on how
>> to
>>> submit bug reports, patches, or suggestions for improvement, see the
>> Apache
>>> Commons Text website:
>>> 
>>> http://commons.apache.org/proper/commons-text/
>>> 
>>> Best regards,
>>> Rob Tompkins
>>> on behalf of the Apache Commons community
>> 
>> 
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
>> For additional commands, e-mail: dev-h...@commons.apache.org
>> 
>> 


-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org

Re: [LANG] Next release

[Allon Mureinik]

The recent commits 0ba25aa, 4fb393b and 15dcb42 buffed up the CI so several
of these reports (javadoc, checkstyle, rat) are checked per commit, so
reviewing the reports should be easier than previous verisons.

If the project's maintainers can review it, I'd like to get PR #257 in
before the release.
It isn't critical, but it completes the work started in PR #254, and it
would be nice to have it included so that the next version can have a clean
start wrt checkstyle verification.

On Mon, Mar 13, 2017 at 11:22 AM, Benedikt Ritter 
wrote:

> Hello,
>
> I’m going to start work on the next [lang] release tonight. If there is
> anything you would like to add, please do it now. If you want to help me
> with the release process, please review the various project reports and
> make sure they look good. Most importantly make sure RAT is clean and Clirr
> does not show breaking changes.
>
> Thank you!
> Benedikt
> -
> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> For additional commands, e-mail: dev-h...@commons.apache.org
>
>

[ANNOUNCE] Apache Commons CLI 1.4 has been released

[Benedikt Ritter]

Hello,

the Apache Commons Community is happy to announce the release of Apache Commons 
CLI 1.4. The Apache Commons CLI library provides an API for parsing command 
line options passed to programs. It's also able to print help messages 
detailing the options available for a command line tool.

Source and binary distributions are available for download from the Apache 
Commons download site:
 http://commons.apache.org/proper/commons-cli/download_cli.cgi

When downloading, please verify signatures using the KEYS file available at the 
above location when downloading the release.

Alternatively the release can be pulled via maven:

  commons-cli
  commons-cli
  1.4


The corrected release notes can be reviewed at:
 http://www.apache.org/dist/commons/cli/RELEASE-NOTES.txt

For complete information on Commons CLI, including instructions on how to
submit bug reports, patches, or suggestions for improvement, see the Apache
Commons CLI website:

http://commons.apache.org/proper/commons-cli/

Best regards,
Benedikt Ritter
on behalf of the Apache Commons community