Re: [log4j] Announce Scala release?

[Gary Gregory]

oops, you're right Matt!

Gary

On Sat, Jul 29, 2017 at 6:42 PM, Matt Sicker  wrote:

> Also, this isn't the right mailing list now that I look more closely.
> Anyways, just sent out a release to announce, dev, and log4j-user.
>
> On 29 July 2017 at 20:41, Gary Gregory  wrote:
>
> > I think you'll want to hit announce@a.o as well as our dev and user MLs.
> >
> > Gary
> >
> > On Sat, Jul 29, 2017 at 6:34 PM, Matt Sicker  wrote:
> >
> > > Oh no, sending the email completely passed my mind. I'll follow up.
> > >
> > > On 29 July 2017 at 20:19, Gary Gregory  wrote:
> > >
> > > > Hi All:
> > > >
> > > > Did I miss the announcement email for the log4j scala 11.0 components
> > > > release?
> > > >
> > > > Gary
> > > >
> > >
> > >
> > >
> > > --
> > > Matt Sicker 
> > >
> >
>
>
>
> --
> Matt Sicker 
>

Re: [log4j] Announce Scala release?

[Matt Sicker]

Also, this isn't the right mailing list now that I look more closely.
Anyways, just sent out a release to announce, dev, and log4j-user.

On 29 July 2017 at 20:41, Gary Gregory  wrote:

> I think you'll want to hit announce@a.o as well as our dev and user MLs.
>
> Gary
>
> On Sat, Jul 29, 2017 at 6:34 PM, Matt Sicker  wrote:
>
> > Oh no, sending the email completely passed my mind. I'll follow up.
> >
> > On 29 July 2017 at 20:19, Gary Gregory  wrote:
> >
> > > Hi All:
> > >
> > > Did I miss the announcement email for the log4j scala 11.0 components
> > > release?
> > >
> > > Gary
> > >
> >
> >
> >
> > --
> > Matt Sicker 
> >
>



-- 
Matt Sicker 

Re: [log4j] Announce Scala release?

[Gary Gregory]

I think you'll want to hit announce@a.o as well as our dev and user MLs.

Gary

On Sat, Jul 29, 2017 at 6:34 PM, Matt Sicker  wrote:

> Oh no, sending the email completely passed my mind. I'll follow up.
>
> On 29 July 2017 at 20:19, Gary Gregory  wrote:
>
> > Hi All:
> >
> > Did I miss the announcement email for the log4j scala 11.0 components
> > release?
> >
> > Gary
> >
>
>
>
> --
> Matt Sicker 
>

Re: [VOTE] Release Commons Email 1.5 Based on RC1

[Gary Gregory]

+1

BUT:

Branding: The RELEASE-NOTES.txt file should start with "Apache Commons
Email Package" instead of "Commons Email Package". I would do away with the
"Package" suffix, we just don't use that, if anything we say "Component"
since the Apache Commons Projects is made up of Components.

Building from the src zip: ASC, MD5, and SHA-1 OK.

CLIRR check OK

RAT check fails with:

Unapproved licenses:

  src/test/resources/eml/attachment-only.eml
  src/test/resources/eml/html-attachment-content-disposition.eml
  src/test/resources/eml/html-attachment-encoded-filename.eml
  src/test/resources/eml/html-attachment.eml
  src/test/resources/eml/multipart-report.eml
  src/test/resources/eml/multipart-text-attachment-only.eml
  src/test/resources/eml/multipart-text-attachment.eml
  src/test/resources/eml/outofmemory-no-header-seperation.eml
  src/test/resources/eml/simple-reply.eml
  src/test/resources/eml/simple.eml

Either these should be licensed with a header in each file or the files
should be excluded from the RAT check.

Built with:

Apache Maven 3.5.0 (ff8f5e7444045639af65f6095c62210b5713f426;
2017-04-03T12:39:06-07:00)
Maven home: C:\Java\apache-maven-3.5.0\bin\..
Java version: 1.8.0_144, vendor: Oracle Corporation
Java home: C:\Program Files\Java\jdk1.8.0_144\jre
Default locale: en_US, platform encoding: Cp1252
OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows"

Gary



On Sat, Jul 29, 2017 at 7:24 AM, Stefan Bodewig  wrote:

> We have fixed quite a few bugs and added some significant enhancements
> since Email 1.4 was released, so I would like to release Email 1.5.
>
> Email 1.5 RC1 is available for review here:
> https://dist.apache.org/repos/dist/dev/commons/email/
> (svn revision 20667)
>
> The tag is here:
> http://svn.apache.org/repos/asf/commons/proper/email/tags/
> EMAIL_1_5_RC1/
> (svn revision 1803366)
> N.B. the SVN revision is required because SVN tags are not immutable.
>
> Maven artifacts are here:
> https://repository.apache.org/content/repositories/
> orgapachecommons-1255/org/apache/commons/commons-email/1.5/
>
> These are the Maven artifacts and their SHA1 hashes
>
> e8e677c6362eba14ff3c476ba63ccb83132dbd52  commons-email-1.5.jar
> 6ccc8b44cb666b849b71ecc6fa32549a6461c099  commons-email-1.5-javadoc.jar
> 09d31911480b5148275d8a26c60e355bbcbe9ae3  commons-email-1.5.pom
> dbe951d1b89eb9472b4b2c8f618b8bc9783b6623  commons-email-1.5-sources.jar
> 15afde52264e316438802b5bd05d34bc424bf659  commons-email-1.5-tests.jar
> e157492dfd776839387a6ce4af0d191e0a92a534  commons-email-1.5-test-
> sources.jar
>
> I have tested this with JDK 8 using Maven 3.0.5.
>
> As usual when I cut a release the site is not the one I'll publish
> once the vote has succeeded. I'll recreate the site once the release
> date is known.
>
> I've already copied the javadocs for 1.4 so
> http://commons.apache.org/proper/commons-email/javadocs/api-1.4/index.html
> already is available. The javadoc links and download page certainly
> don't work in the staging site.
>
> Details of changes since 1.4 are in the release notes:
> https://dist.apache.org/repos/dist/dev/commons/email/RELEASE-NOTES.txt
> https://stefan.samaflost.de/staging/commons-email-1.5/
> changes-report.html
>
> Site:
> https://stefan.samaflost.de/staging/commons-email-1.5/
>
> Clirr Report (compared to 1.4):
> https://stefan.samaflost.de/staging/commons-email-1.5/
> clirr-report.html
>
> RAT Report:
> https://stefan.samaflost.de/staging/commons-email-1.5/rat-report.html
>
> KEYS:
>   https://www.apache.org/dist/commons/KEYS
>
> Please review the release candidate and vote.
> This vote will close no sooner that 72 hours from now,
> i.e. sometime after 14:30 UTC 1-Aug 2017
>
>   [ ] +1 Release these artifacts
>   [ ] +0 OK, but...
>   [ ] -0 OK, but really should fix...
>   [ ] -1 I oppose this release because...
>
> Thanks!
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> For additional commands, e-mail: dev-h...@commons.apache.org
>
>

Re: [log4j] Announce Scala release?

[Matt Sicker]

Oh no, sending the email completely passed my mind. I'll follow up.

On 29 July 2017 at 20:19, Gary Gregory  wrote:

> Hi All:
>
> Did I miss the announcement email for the log4j scala 11.0 components
> release?
>
> Gary
>



-- 
Matt Sicker 

[log4j] Announce Scala release?

[Gary Gregory]

Hi All:

Did I miss the announcement email for the log4j scala 11.0 components
release?

Gary

Re: [OT] Job offer

[Stefan Bodewig]

On 2017-07-29, Oliver Heger wrote:

> my apologies in advance if this is considered spam, but as some of my
> colleagues know that I am involved in an open source project, they asked
> my to post the following Job offer here.

Oliver, are you aware of the jobs@apache mailing list? You may find a
broader audience there.

Stefan

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

Re: [OT] Job offer

[Oliver Heger]

Am 29.07.2017 um 21:59 schrieb Hasan Diwan:
> Perhaps an English-translation here? German's far from my first language,
> after all. -- H

You are right. The job is located in Germany, but company language is
English. I will ask HR if there is a translation available.

Oliver

> 
> On 29 July 2017 at 12:56, Oliver Heger  wrote:
> 
>> Hi all,
>>
>> my apologies in advance if this is considered spam, but as some of my
>> colleagues know that I am involved in an open source project, they asked
>> my to post the following Job offer here.
>>
>> The company I am working for - Bosch Software Innovations - is searching
>> a developer with open source experience supporting our activities in
>> this area. We donated a product from out IoT suite to the Eclipse
>> Foundation and now want to hire a dedicated developer who drives this
>> project forward and collaborates with the community to integrate new
>> features.
>>
>> Detailed information can be found at
>> https://www.bosch-si.com/de/unternehmen/karriere/stellen/
>> hr-details-jobs-6388.html
>>
>> If there is interest, please contact me off-list.
>>
>> Regards
>> Oliver
>>
>> -
>> 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: [OT] Job offer

[Hasan Diwan]

Perhaps an English-translation here? German's far from my first language,
after all. -- H

On 29 July 2017 at 12:56, Oliver Heger  wrote:

> Hi all,
>
> my apologies in advance if this is considered spam, but as some of my
> colleagues know that I am involved in an open source project, they asked
> my to post the following Job offer here.
>
> The company I am working for - Bosch Software Innovations - is searching
> a developer with open source experience supporting our activities in
> this area. We donated a product from out IoT suite to the Eclipse
> Foundation and now want to hire a dedicated developer who drives this
> project forward and collaborates with the community to integrate new
> features.
>
> Detailed information can be found at
> https://www.bosch-si.com/de/unternehmen/karriere/stellen/
> hr-details-jobs-6388.html
>
> If there is interest, please contact me off-list.
>
> Regards
> Oliver
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> For additional commands, e-mail: dev-h...@commons.apache.org
>
>


-- 
OpenPGP:
https://sks-keyservers.net/pks/lookup?op=get=0xFEBAD7FFD041BBA1
If you wish to request my time, please do so using
http://bit.ly/hd1ScheduleRequest.
Si vous voudrais faire connnaisance, allez a
http://bit.ly/hd1ScheduleRequest.

Sent
from my mobile device
Envoye de mon portable

[OT] Job offer

[Oliver Heger]

Hi all,

my apologies in advance if this is considered spam, but as some of my
colleagues know that I am involved in an open source project, they asked
my to post the following Job offer here.

The company I am working for - Bosch Software Innovations - is searching
a developer with open source experience supporting our activities in
this area. We donated a product from out IoT suite to the Eclipse
Foundation and now want to hire a dedicated developer who drives this
project forward and collaborates with the community to integrate new
features.

Detailed information can be found at
https://www.bosch-si.com/de/unternehmen/karriere/stellen/hr-details-jobs-6388.html

If there is interest, please contact me off-list.

Regards
Oliver

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

Re: [VOTE] Release Commons Email 1.5 Based on RC1

[Oliver Heger]

Build works fine with Java 1.6 and 1.8. Artifacts and site look good.

+1

Oliver

Am 29.07.2017 um 16:24 schrieb Stefan Bodewig:
> We have fixed quite a few bugs and added some significant enhancements
> since Email 1.4 was released, so I would like to release Email 1.5.
> 
> Email 1.5 RC1 is available for review here:
> https://dist.apache.org/repos/dist/dev/commons/email/
> (svn revision 20667)
> 
> The tag is here:
> http://svn.apache.org/repos/asf/commons/proper/email/tags/EMAIL_1_5_RC1/
> (svn revision 1803366)
> N.B. the SVN revision is required because SVN tags are not immutable.
> 
> Maven artifacts are here:
> 
> https://repository.apache.org/content/repositories/orgapachecommons-1255/org/apache/commons/commons-email/1.5/
> 
> These are the Maven artifacts and their SHA1 hashes
> 
> e8e677c6362eba14ff3c476ba63ccb83132dbd52  commons-email-1.5.jar
> 6ccc8b44cb666b849b71ecc6fa32549a6461c099  commons-email-1.5-javadoc.jar
> 09d31911480b5148275d8a26c60e355bbcbe9ae3  commons-email-1.5.pom
> dbe951d1b89eb9472b4b2c8f618b8bc9783b6623  commons-email-1.5-sources.jar
> 15afde52264e316438802b5bd05d34bc424bf659  commons-email-1.5-tests.jar
> e157492dfd776839387a6ce4af0d191e0a92a534  commons-email-1.5-test-sources.jar
> 
> I have tested this with JDK 8 using Maven 3.0.5.
> 
> As usual when I cut a release the site is not the one I'll publish
> once the vote has succeeded. I'll recreate the site once the release
> date is known.
> 
> I've already copied the javadocs for 1.4 so
> http://commons.apache.org/proper/commons-email/javadocs/api-1.4/index.html
> already is available. The javadoc links and download page certainly
> don't work in the staging site.
> 
> Details of changes since 1.4 are in the release notes:
> https://dist.apache.org/repos/dist/dev/commons/email/RELEASE-NOTES.txt
> https://stefan.samaflost.de/staging/commons-email-1.5/changes-report.html
> 
> Site:
> https://stefan.samaflost.de/staging/commons-email-1.5/
> 
> Clirr Report (compared to 1.4):
> https://stefan.samaflost.de/staging/commons-email-1.5/clirr-report.html
> 
> RAT Report:
> https://stefan.samaflost.de/staging/commons-email-1.5/rat-report.html
> 
> KEYS:
>   https://www.apache.org/dist/commons/KEYS
> 
> Please review the release candidate and vote.
> This vote will close no sooner that 72 hours from now,
> i.e. sometime after 14:30 UTC 1-Aug 2017
> 
>   [ ] +1 Release these artifacts
>   [ ] +0 OK, but...
>   [ ] -0 OK, but really should fix...
>   [ ] -1 I oppose this release because...
> 
> Thanks!
> 
> -
> 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

[GitHub] commons-cli issue #15: CLI-217: Optional partial matching

[rubin55]

Github user rubin55 commented on the issue:

https://github.com/apache/commons-cli/pull/15
  
@chtompki Well, 216 is about disabling concatenated options, and 217 is 
about disabling partial matching; my patch implements the latter, i.e, you 
still have concatenated options, but can opt to disable partial matching:

foo -ver
!=
foo --version

So in the above, -ver could be a concatenated set of options, which, with 
the help of this patch, does not erronuously get interpreted as a partially 
matched long option 'version'.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

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

[GitHub] commons-cli issue #15: CLI-217: Optional partial matching

[rubin55]

Github user rubin55 commented on the issue:

https://github.com/apache/commons-cli/pull/15
  
@chtompki Well, 216 is about disabling concatenated options, and 217 is 
about disabling partial matching; my patch implements the latter, i.e, you 
still have concatenated options, but can opt to disable partial matching:

foo -ver
!=
foo --version

So in the above, -ver could be a concatenated set of options, which, with 
the help of this patch, does not erronuously get interpreted as a partially 
matched long option 'version'.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

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

[GitHub] commons-cli issue #15: CLI-217: Optional partial matching

[chtompki]

Github user chtompki commented on the issue:

https://github.com/apache/commons-cli/pull/15
  
Upon reading [CLI-216](https://issues.apache.org/jira/browse/CLI-216) and 
[CLI-217](https://issues.apache.org/jira/browse/CLI-217), this pull request 
looks like it resolves CLI-216 and not CLI-217. I might be missing something. 
@rubin55 - I'm definitely on board with this change. I just want to document it 
appropriately. Thoughts?


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

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

[GitHub] commons-cli issue #15: CLI-217: Optional partial matching

[chtompki]

Github user chtompki commented on the issue:

https://github.com/apache/commons-cli/pull/15
  
Upon reading [CLI-216](https://issues.apache.org/jira/browse/CLI-216) and 
[CLI-217](https://issues.apache.org/jira/browse/CLI-217), this pull request 
looks like it resolves CLI-216 and not CLI-217. I might be missing something. 
@rubin55 - I'm definitely on board with this change. I just want to document it 
appropriately. Thoughts?


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

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

[GitHub] commons-cli issue #15: CLI-217: Optional partial matching

[chtompki]

Github user chtompki commented on the issue:

https://github.com/apache/commons-cli/pull/15
  
Working on this now.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

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

[GitHub] commons-cli issue #15: CLI-217: Optional partial matching

[chtompki]

Github user chtompki commented on the issue:

https://github.com/apache/commons-cli/pull/15
  
Working on this now.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

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

[VOTE] Release Commons Email 1.5 Based on RC1

[Stefan Bodewig]

We have fixed quite a few bugs and added some significant enhancements
since Email 1.4 was released, so I would like to release Email 1.5.

Email 1.5 RC1 is available for review here:
https://dist.apache.org/repos/dist/dev/commons/email/
(svn revision 20667)

The tag is here:
http://svn.apache.org/repos/asf/commons/proper/email/tags/EMAIL_1_5_RC1/
(svn revision 1803366)
N.B. the SVN revision is required because SVN tags are not immutable.

Maven artifacts are here:

https://repository.apache.org/content/repositories/orgapachecommons-1255/org/apache/commons/commons-email/1.5/

These are the Maven artifacts and their SHA1 hashes

e8e677c6362eba14ff3c476ba63ccb83132dbd52  commons-email-1.5.jar
6ccc8b44cb666b849b71ecc6fa32549a6461c099  commons-email-1.5-javadoc.jar
09d31911480b5148275d8a26c60e355bbcbe9ae3  commons-email-1.5.pom
dbe951d1b89eb9472b4b2c8f618b8bc9783b6623  commons-email-1.5-sources.jar
15afde52264e316438802b5bd05d34bc424bf659  commons-email-1.5-tests.jar
e157492dfd776839387a6ce4af0d191e0a92a534  commons-email-1.5-test-sources.jar

I have tested this with JDK 8 using Maven 3.0.5.

As usual when I cut a release the site is not the one I'll publish
once the vote has succeeded. I'll recreate the site once the release
date is known.

I've already copied the javadocs for 1.4 so
http://commons.apache.org/proper/commons-email/javadocs/api-1.4/index.html
already is available. The javadoc links and download page certainly
don't work in the staging site.

Details of changes since 1.4 are in the release notes:
https://dist.apache.org/repos/dist/dev/commons/email/RELEASE-NOTES.txt
https://stefan.samaflost.de/staging/commons-email-1.5/changes-report.html

Site:
https://stefan.samaflost.de/staging/commons-email-1.5/

Clirr Report (compared to 1.4):
https://stefan.samaflost.de/staging/commons-email-1.5/clirr-report.html

RAT Report:
https://stefan.samaflost.de/staging/commons-email-1.5/rat-report.html

KEYS:
  https://www.apache.org/dist/commons/KEYS

Please review the release candidate and vote.
This vote will close no sooner that 72 hours from now,
i.e. sometime after 14:30 UTC 1-Aug 2017

  [ ] +1 Release these artifacts
  [ ] +0 OK, but...
  [ ] -0 OK, but really should fix...
  [ ] -1 I oppose this release because...

Thanks!

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