Re: Ivy release

2018-04-09 Thread Jaikiran Pai
+1. Thanks Nicolas. -Jaikiran On Monday, April 9, 2018, Nicolas Lalevée wrote: > The last thread about a release has been stuck in the discussion about which PR, patch or Jira needed to be tackled before releasing. I suggest we just move forward with the current master. I volunteer to build a 2.

Re: Ivy release

2018-04-09 Thread Gintautas Grigelionis
2018-04-09 17:20 GMT+00:00 Nicolas Lalevée : > The last thread about a release has been stuck in the discussion about > which PR, patch or Jira needed to be tackled before releasing. I suggest we > just move forward with the current master. I volunteer to build a 2.5.0-rc1. > > Nicolas > +1; mayb

Re: Ivy release this month?

2018-02-27 Thread Gintautas Grigelionis
The ugly thing 2018-02-27 22:40 GMT+01:00 Gintautas Grigelionis : > 2018-02-18 20:30 GMT+01:00 Stefan Bodewig : > >> [Personally I prefer discussion by email over discussion in github >> issues.] >> > > The beauty is that GitHub comments are echoed in mailing list, and, in > case of PR mentioning

Re: Ivy release this month?

2018-02-27 Thread Gintautas Grigelionis
2018-02-18 20:30 GMT+01:00 Stefan Bodewig : > [Personally I prefer discussion by email over discussion in github > issues.] > The beauty is that GitHub comments are echoed in mailing list, and, in case of PR mentioning JIRA issues, in JIRA as well. Gintas

Re: Ivy release this month?

2018-02-27 Thread Gintautas Grigelionis
2018-02-19 7:35 GMT+01:00 Stefan Bodewig : > On 2018-02-18, Gintautas Grigelionis wrote: > > > 2018-02-18 20:30 GMT+01:00 Stefan Bodewig : > > >> On 2018-02-18, Gintautas Grigelionis wrote: > > >>>- https://github.com/apache/ant-ivy/pull/63 (has to do with choice > of > >>>generics, with a

Re: Ivy release this month?

2018-02-27 Thread Gintautas Grigelionis
Frankly, I was doubtful about the classloader change. But, what use cases are there for java -jar ivy.jar -main ? As I understand it, it's about resolving an artifact and lauching whatever main class would be there in it. So, why not bootstrapping an Ivy build in a fancy way? But, the new classl

Re: Ivy release instructions

2018-02-27 Thread Stefan Bodewig
On 2018-02-27, Jaikiran Pai wrote: > The first round of this might not be publicly usable and we might have > to redo the steps as and when we fix things in the release process. So > maybe we should attempt an intermediate release before doing a 2.5.0. As long as we stop before pushing anything i

Re: Ivy release this month?

2018-02-27 Thread Jaikiran Pai
- https://github.com/apache/ant-ivy/pull/67 (a one-liner; anybody sees some side effects?) I don't understand the issue. Is this a documented way of using Ivy or why would anybody expect it to be possible to invoke Ant via the Ivy jar? Somebody was interested enough to open a JIRA issu

Re: Ivy release this month?

2018-02-18 Thread Stefan Bodewig
On 2018-02-18, Gintautas Grigelionis wrote: > 2018-02-18 20:30 GMT+01:00 Stefan Bodewig : >> On 2018-02-18, Gintautas Grigelionis wrote: >>>- https://github.com/apache/ant-ivy/pull/63 (has to do with choice of >>>generics, with are not set in stone yet); >> changes the generic type of a

Re: Ivy release this month?

2018-02-18 Thread Gintautas Grigelionis
2018-02-18 20:30 GMT+01:00 Stefan Bodewig : > [Personally I prefer discussion by email over discussion in github > issues.] > > On 2018-02-18, Gintautas Grigelionis wrote: > > >- https://github.com/apache/ant-ivy/pull/63 (has to do with choice of > >generics, with are not set in stone yet)

Re: Ivy release this month?

2018-02-18 Thread Stefan Bodewig
[Personally I prefer discussion by email over discussion in github issues.] On 2018-02-18, Gintautas Grigelionis wrote: >- https://github.com/apache/ant-ivy/pull/63 (has to do with choice of >generics, with are not set in stone yet); changes the generic type of an argument of a public me

Re: Ivy release this month?

2018-02-18 Thread Gintautas Grigelionis
I suggested previously how some of the contentious issues could be dealt with (no response AFAICS). In the meantime, I added the following PRs asking for some discussion - https://github.com/apache/ant-ivy/pull/63 (has to do with choice of generics, with are not set in stone yet); - http

Re: Ivy release schedule

2014-01-13 Thread Nicolas Lalevée
Le 4 janv. 2014 à 14:11, Nicolas Lalevée a écrit : > > Le 2 janv. 2014 à 17:34, Nicolas Lalevée a écrit > : > >> >> Le 2 janv. 2014 à 17:10, Charles Duffy a écrit : >> >>> Absolutely, then. :) >>> >>> I was under the impression that only members of the PMC could call a vote >>> for a rel

Re: Ivy release schedule

2014-01-04 Thread Nicolas Lalevée
Le 2 janv. 2014 à 17:34, Nicolas Lalevée a écrit : > > Le 2 janv. 2014 à 17:10, Charles Duffy a écrit : > >> Absolutely, then. :) >> >> I was under the impression that only members of the PMC could call a vote >> for a release. > > Here is the official rules: > http://ant.apache.org/bylaws.

Re: Ivy release schedule

2014-01-02 Thread Nicolas Lalevée
Le 2 janv. 2014 à 17:10, Charles Duffy a écrit : > Absolutely, then. :) > > I was under the impression that only members of the PMC could call a vote > for a release. Here is the official rules: http://ant.apache.org/bylaws.html You can do a release, but it will be officially accepted only by

Re: Ivy release schedule

2014-01-02 Thread Charles Duffy
Absolutely, then. :) I was under the impression that only members of the PMC could call a vote for a release. If that's something any committer can do, I'll gladly run the process after your pending feature is in. Thanks! On Thu, Jan 2, 2014 at 10:02 AM, Nicolas Lalevée wrote: > > Le 30 déc.

Re: Ivy release schedule

2014-01-02 Thread Nicolas Lalevée
Le 30 déc. 2013 à 19:35, Charles Duffy a écrit : > Howdy, all -- > > There's rather a lot of good stuff on Ivy's trunk. Agreed. > Any thoughts as to when > we might be in a position to start a release candidate series? I think any time a committer is willing to do so. > (As there are ticket

Re: Ivy release problem

2009-10-11 Thread Stefan Bodewig
On 2009-10-09, Maarten Coene wrote: > No, it still doesn't work: > [maart...@minotaur:/www/www.apache.org/dist/ant/ivy]$ ls -al Looks good right now, all files and dirs are owned by group ant. Stefan - To unsubscribe, e-mail:

Re: Ivy release problem

2009-10-09 Thread Maarten Coene
0-rc2 [maart...@minotaur:/www/www.apache.org/dist/ant/ivy]$ mkdir 2.1.0 mkdir: 2.1.0: Permission denied Maarten - Original Message From: Stefan Bodewig To: dev@ant.apache.org Sent: Fri, October 9, 2009 9:25:33 AM Subject: Re: Ivy release problem On 2009-10-09, Stefan Bodewig

Re: Ivy release problem

2009-10-09 Thread Maarten Coene
Thanks Stefan! I can't check it right now neither, I'll try it again this evening. Maarten - Original Message From: Stefan Bodewig To: dev@ant.apache.org Sent: Friday, October 9, 2009 9:25:33 AM Subject: Re: Ivy release problem On 2009-10-09, Stefan Bodewig wrote: &

Re: Ivy release problem

2009-10-09 Thread Stefan Bodewig
On 2009-10-09, Stefan Bodewig wrote: > I've just asked on infrastructure to get it fixed. Joe said it has been fixed (can't check it right now). Stefan - To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org For additional co

Re: Ivy release problem

2009-10-08 Thread Stefan Bodewig
On 2009-10-09, Maarten Coene wrote: > I've tried to upload the Ivy artifact to the distribution site, but I > receive a permission denied (it looks like the group/owner has changed > of these directories?) I assume this happened when backups have been restored after the apachecon site hack. I'v

Re: Ivy release?

2009-09-17 Thread Maarten Coene
ok, I'll start with the release process as soon as I've fixed some problems with my Eclipse installation... Maarten - Original Message From: Nicolas Lalevée To: Ant Developers List Sent: Sunday, September 13, 2009 2:51:34 PM Subject: Re: Ivy release? idem, +1 Nicolas

Re: Ivy release?

2009-09-13 Thread Nicolas Lalevée
idem, +1 Nicolas Le 7 sept. 09 à 12:50, Gilles Scokart a écrit : Same here, OK for a 2.1.0 with r801820 merge, and OK for 2.1.1 without an "external" RC first (having zip on which to vote is a suffisent "release candidate" step). Thanks, Gilles Scokart 2009/9/7 Xavier Hanin I'm ok

Re: Ivy release?

2009-09-07 Thread Gilles Scokart
Same here, OK for a 2.1.0 with r801820 merge, and OK for 2.1.1 without an "external" RC first (having zip on which to vote is a suffisent "release candidate" step). Thanks, Gilles Scokart 2009/9/7 Xavier Hanin > I'm ok for a 2.1.0 release with r801820 merged. > For a 2.1.1 I'm not sure a RC

Re: Ivy release?

2009-09-07 Thread Xavier Hanin
I'm ok for a 2.1.0 release with r801820 merged. For a 2.1.1 I'm not sure a RC is really necessary... If we have only bug fixes without too heavy changes I think releasing 2.1.1 directly without prior RC is ok. If something goes wrong we can release a 2.1.2 and that's fine. BTW, thanks a lot Maarte

Re: Ivy release schedule

2009-06-23 Thread Hans Dockter
On Jun 9, 2009, at 11:41 PM, Maarten Coene wrote: Ivy 2.1.0-RC1 has been out for some (too long?) time now. (didn't had much time last couple of months, but it's getting better now :-)) Let's decide our next steps... Because the RC1 is so old, I would like to create a 2.1.0-RC2 next wee

Re: Ivy release schedule

2009-06-10 Thread Gilles Scokart
+1 Gilles Scokart 2009/6/9 Maarten Coene > > Ivy 2.1.0-RC1 has been out for some (too long?) time now. (didn't had much > time last couple of months, but it's getting better now :-)) > > Let's decide our next steps... > > Because the RC1 is so old, I would like to create a 2.1.0-RC2 next week >

Re: Ivy release schedule

2009-06-10 Thread Nicolas Lalevée
On Tue, 9 Jun 2009 14:41:59 -0700 (PDT), Maarten Coene wrote: > > Ivy 2.1.0-RC1 has been out for some (too long?) time now. (didn't had much > time last couple of months, but it's getting better now :-)) > > Let's decide our next steps... > > Because the RC1 is so old, I would like to create

Re: Ivy release schedule

2009-06-10 Thread rednix
Maarten Coene wrote: > > > Ivy 2.1.0-RC1 has been out for some (too long?) time now. (didn't had much > time last couple of months, but it's getting better now :-)) > > Let's decide our next steps... > > Because the RC1 is so old, I would like to create a 2.1.0-RC2 next week > containing all