Ok, will try this week-end. Thanks for the feedback.
Romain Manni-Bucau
@rmannibucau | Blog | Old Blog | Github | LinkedIn
2017-10-25 6:42 GMT+02:00 Gary Gregory :
> IMO, you should redo the tag and rewrite the VOTE email following the
> template in
IMO, you should redo the tag and rewrite the VOTE email following the
template in http://commons.apache.org/releases/prepare.html
Gary
On Tue, Oct 24, 2017 at 10:40 PM, Romain Manni-Bucau
wrote:
> Hmm,
>
> Read that page but the answer is probably hidden in the commons
Hmm,
Read that page but the answer is probably hidden in the commons parent - rc
property? - cause it is not written how a rc version ends in a not rc
version for binaries on nexus with the release plugin. Will check which
magic we do here later this week but anyway shouldnt block the release IMO
Maybe what is in master is enough?
Gary
On Tue, Oct 24, 2017 at 10:31 PM, Bruno P. Kinoshita <
brunodepau...@yahoo.com.br.invalid> wrote:
> Not so familiar, more familiar with Jena, but they are related.
> If nobody else volunteers, I can try to spend a weekend triaging issues
> and seeing if I
Not so familiar, more familiar with Jena, but they are related.
If nobody else volunteers, I can try to spend a weekend triaging issues and
seeing if I can catch up with the changes since the last release and volunteer
to cut a new release.
CheersBruno
From: Gary Gregory
On Tue, Oct 24, 2017 at 9:28 PM, kenneth mcfarland <
kennethpmcfarl...@gmail.com> wrote:
> Gary, I can't help but say great work on all of these releases. #praise
>
Thank you Kenneth.
Gary
>
> On Oct 24, 2017 8:24 PM, "Gary Gregory" wrote:
>
> > Our process documented
On 22 October 2017 at 16:17, Romain Manni-Bucau
wrote:
> So i just copy the mvn release tag? Sounds quite useless since the tag is
> done no?
>
A release candidate is supposed to match the eventual release at some
point; that's why it's a "candidate". Making a copy of an
Remove the version specifier for build-helper-maven-plugin, this will pick
up the version from the parent POM, which I locally updated from 34 to 42.
Then you'll run into some other error due to how this old build wants to
name jars.
Gary
On Sat, Oct 21, 2017 at 2:30 AM, Benedikt Ritter
Gary, I can't help but say great work on all of these releases. #praise
On Oct 24, 2017 8:24 PM, "Gary Gregory" wrote:
> Our process documented here http://commons.apache.org/
> releases/prepare.html
> makes it pretty clear that the RC tag should be labeled as such and
Hopefully someone who is familiar with Commons RDF is reading this...
Gary
On Fri, Oct 20, 2017 at 2:25 PM, Aaron Coburn wrote:
> Hello,
>
> I wanted to check in on the status of a 0.4.0 release of Commons RDF. It
> seems that all of the open PRs have been merged. Any idea
Our process documented here http://commons.apache.org/releases/prepare.html
makes it pretty clear that the RC tag should be labeled as such and that a
tag like "commons-jcs-2.2.1" should only be created after a VOTE passes.
Gary
On Sun, Oct 22, 2017 at 3:17 PM, Romain Manni-Bucau
We have fixed a few bugs since Apache Commons Pool 2.4.2 was released, so I
would like to release Apache Commons Pool 2.4.3.
Apache Commons Pool 2.4.3 RC1 is available for review here:
https://dist.apache.org/repos/dist/dev/commons/pool at revision: 22662
Get it like this: svn co
GitHub user michaelsavich opened a pull request:
https://github.com/apache/commons-cli/pull/21
Add module-info
This should modularize commons-cli. We may have to do another commit to get
maven to build modularized jars by default, but as of this build javac works
perfectly.
You
As long as it is on your to-do list, I can focus on other tasks.
Thank you!
Gary
On Oct 24, 2017 13:29, "Benedikt Ritter" wrote:
> I‘m planning to work on it soon but I can‘t give you an ETA at the moment.
>
> Regards,
> Benedikt
>
> Gary Gregory
I‘m planning to work on it soon but I can‘t give you an ETA at the moment.
Regards,
Benedikt
Gary Gregory schrieb am Di. 24. Okt. 2017 um 00:01:
> We've had a couple of false starts here. Is the RM ready to fire off an RC?
>
> Gary
>
On 24 October 2017 at 15:22, Gary Gregory wrote:
> I think I will:
> - release pool
> - update to Java 7
Might be sensible to add a note to the pom that Tomcat 8 needs Java 7+.
This means that Pool 2 cannot be updated beyond Java 7 without
affecting Tomcat 8.
> It seems
I think I will:
- release pool
- update to Java 7
It seems cleaner that way.
Gary
On Tue, Oct 24, 2017 at 8:04 AM, Matt Sicker wrote:
> On 24 October 2017 at 06:44, Mark Thomas wrote:
>
> > On 24/10/17 05:56, Matt Sicker wrote:
> > > Go for it! Though
On 24 October 2017 at 06:44, Mark Thomas wrote:
> On 24/10/17 05:56, Matt Sicker wrote:
> > Go for it! Though perhaps some quick feedback from Tomcat would be good
> > since they're the primary Apache project that uses the library.
>
> I assume we are talking about Pool 2.x.
>
On 24/10/17 05:56, Matt Sicker wrote:
> Go for it! Though perhaps some quick feedback from Tomcat would be good
> since they're the primary Apache project that uses the library.
I assume we are talking about Pool 2.x.
Pool 2.x is used by Tomcat 8 onwards and Tomcat 8 has a requirement of
Java 7
On Tue, Oct 24, 2017 at 12:30 AM, Gary Gregory wrote:
> Or the other way around. Release and update to Java 7...
Sounds like a better plan to me. After two years, it could be
necessary to provide another maintenance release at any time.
Jochen
--
The next time you
20 matches
Mail list logo