Re: Ivy release
+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.5.0-rc1. > > Nicolas > > > - > To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org > For additional commands, e-mail: dev-h...@ant.apache.org > >
Re: Ivy release
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; maybe consider merging the recent proposal by Greg [1] or PR#63/64. Gintas [1] https://github.com/apache/ant-ivy/commit/d06e3bc
Re: Ivy release this month?
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 JIRA issues, in JIRA as well. > > Gintas > The ugliness is that comments on commits get subject "[GitHub] ant-ivy pull request #:" in mailing list rather than the original Git comment. Do we have control over that of is it something to report to infra? Gintas
Re: Ivy release this month?
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-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 are not set in stone yet); > > >> changes the generic type of an argument of a public method inside a > >> public class. > > > That's obvious. Any suggestions? > > I'm not familiar with the Ivy code base so all I can suggest is along > general lines of "think about a different approach" and "document the > break of backwards compatibility if unavoidable". > > This case is specifically tricky as you will only run into problems at > runtime (unless you recompile your code) thanks to type erasure. > Existing compiled code that invokes doesCallersExclude with a Stack of > ModuleRevisionIds will be allowed to call the method. > Hmmm, I may use (Array)Deque and provide Stack for backwards compatibility, how about that? Gintas
Re: Ivy release this month?
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 classloader created as a child of Ivy's classloader has all Ivy classes creating conflicts. By taking a parent of Ivy classloader (that is, system classloader) the conflicts are avoided. What is exactly the problem? Is there a use case that MUST have Ivy classes on the classloader automagically? Gintas 2018-02-27 14:26 GMT+01:00 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 issue. And the case is >>> around >>> the use which is definitely documented. >>> >> Let me rephrase. Is this a use-case the Ivy developers want to support? >> >> > I am nervous about this change for multiple reasons: > > - I read that JIRA and I don't understand why Ivy jar is being used to > call into Ant's Main class. > - The JIRA doesn't provide any context nor did I find (in my limited > search) that we support that use case. > - The change being proposed involves a classloader (hierarchy) change > which is what makes me nervous, since without knowing more on what we are > trying to achieve here and why, it's difficult to say whatelse it might > impact. > - It also brings in additional deps and again comes back to the > original question about what use case we are trying to support. > > IMO, this is something that we can avoid changing. > > -Jaikiran > > > > - > To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org > For additional commands, e-mail: dev-h...@ant.apache.org > >
Re: Ivy release instructions
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 into the release directories of dist.apache.org or releasing maven artifacts from Nexus we don't need any intermediate releases IMHO. Those final steps would only happen after a successful release vote which should not happen unless the result is usable :-) > I understand the release process is time consuming, so if neither of > you would be able to get to this and if there's no objections, I can > initiate these steps (and ask for specific help as I go along) for an > intermediate release. Once this goes well, we can then have any of us > do the final release (which should be much smoother). I can give it a try but likely won't get there before the weekend. To be honest finishing my review of that JUnit5 PR for Ant somebody has created would by higher on my personal priority list ;-) Stefan - To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org For additional commands, e-mail: dev-h...@ant.apache.org
Re: Ivy release this month?
- 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 issue. And the case is around the use which is definitely documented. Let me rephrase. Is this a use-case the Ivy developers want to support? I am nervous about this change for multiple reasons: - I read that JIRA and I don't understand why Ivy jar is being used to call into Ant's Main class. - The JIRA doesn't provide any context nor did I find (in my limited search) that we support that use case. - The change being proposed involves a classloader (hierarchy) change which is what makes me nervous, since without knowing more on what we are trying to achieve here and why, it's difficult to say whatelse it might impact. - It also brings in additional deps and again comes back to the original question about what use case we are trying to support. IMO, this is something that we can avoid changing. -Jaikiran - To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org For additional commands, e-mail: dev-h...@ant.apache.org
Re: Ivy release this month?
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 an argument of a public method inside a >> public class. > That's obvious. Any suggestions? I'm not familiar with the Ivy code base so all I can suggest is along general lines of "think about a different approach" and "document the break of backwards compatibility if unavoidable". This case is specifically tricky as you will only run into problems at runtime (unless you recompile your code) thanks to type erasure. Existing compiled code that invokes doesCallersExclude with a Stack of ModuleRevisionIds will be allowed to call the method. >>- https://github.com/apache/ant-ivy/pull/64 (in production at TomTom; >>>should we look for a more general solution, or just document that >>>preemptive authentication restricts to basic scheme?); >> adds a new method to a public interface (URLHandler). > Java 8, then. Not my call. >>>- 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 issue. And the case is around > the use which is definitely documented. Let me rephrase. Is this a use-case the Ivy developers want to support? Stefan - To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org For additional commands, e-mail: dev-h...@ant.apache.org
Re: Ivy release this month?
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); > > changes the generic type of an argument of a public method inside a > public class. > That's obvious. Any suggestions? >- https://github.com/apache/ant-ivy/pull/64 (in production at TomTom; > >should we look for a more general solution, or just document that > >preemptive authentication restricts to basic scheme?); > > adds a new method to a public interface (URLHandler). > Java 8, then. > >- 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 issue. And the case is around the use which is definitely documented. Gintas
Re: Ivy release this month?
[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 method inside a public class. >- https://github.com/apache/ant-ivy/pull/64 (in production at TomTom; >should we look for a more general solution, or just document that >preemptive authentication restricts to basic scheme?); adds a new method to a public interface (URLHandler). >- 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? Stefan - To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org For additional commands, e-mail: dev-h...@ant.apache.org
Re: Ivy release this month?
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); - https://github.com/apache/ant-ivy/pull/64 (in production at TomTom; should we look for a more general solution, or just document that preemptive authentication restricts to basic scheme?); - https://github.com/apache/ant-ivy/pull/67 (a one-liner; anybody sees some side effects?) Thanks, Gintas 2018-02-18 13:06 GMT+01:00 Jaikiran Pai : > Hello everyone, > > Is there anything I can help with to start off and complete the Ivy > release, hopefully this month? As I noted in the dev list mail, I don't > plan to include the fix for > https://issues.apache.org/jira/browse/IVY-1485 in this release and > instead try and tackle it after that. There are few PRs open, but except > for this one https://github.com/apache/ant-ivy/pull/62 I don't plan to > merge the rest given the nature of the changes. There's no release > instructions that I could find, so I am not sure what's going to be > involved in the actual release process. > > > -Jaikiran > > > - > To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org > For additional commands, e-mail: dev-h...@ant.apache.org > >
Re: Ivy release schedule
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 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 a majority >> of the PMC. >> >>> If that's something any committer can do, I'll gladly run the process after >>> your pending feature is in. >> >> I think we have a good doc about how to release: >> http://ant.apache.org/ivy/history/trunk/dev/makerelease.html >> >> I willing to help, especially for the optional publication to the Eclipse >> updatesite. >> >> I'll keep you posted about my progress. > > I nailed it. It needs a little bit of documentation thought. I'll write some > soon. doc written. It's good for me. Nicolas > > Nicolas > >> >> Cheers, >> Nicolas >> >>> >>> Thanks! >>> >>> >>> On Thu, Jan 2, 2014 at 10:02 AM, Nicolas Lalevée >>> wrote: >>> 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 tickets assigned to 2.4.0, and nothing on 2.3.1, would I be > correct in gathering that that's where we're going next?) Yep 2.4.0 should be the next one. I only have one wish. I am working on supporting "packed" (.pack.gz) resources from Eclipse update sites. For that I would need to redesign a feature which is only in trunk: uncompress artifact on resolve (not documented yet, see DefaultRepositoryCacheManager#uncompressArtifact). Since I would like to break it a little bit, I would like to do it before releasing it, so no backward compatibility have to be supported. I am struggling a little bit with it, but I don't think it will take very long. Nicolas - To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org For additional commands, e-mail: dev-h...@ant.apache.org >> >> >> - >> To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org >> For additional commands, e-mail: dev-h...@ant.apache.org >> > > > - > To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org > For additional commands, e-mail: dev-h...@ant.apache.org > - To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org For additional commands, e-mail: dev-h...@ant.apache.org
Re: Ivy release schedule
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.html > > You can do a release, but it will be officially accepted only by a majority > of the PMC. > >> If that's something any committer can do, I'll gladly run the process after >> your pending feature is in. > > I think we have a good doc about how to release: > http://ant.apache.org/ivy/history/trunk/dev/makerelease.html > > I willing to help, especially for the optional publication to the Eclipse > updatesite. > > I'll keep you posted about my progress. I nailed it. It needs a little bit of documentation thought. I'll write some soon. Nicolas > > Cheers, > Nicolas > >> >> Thanks! >> >> >> On Thu, Jan 2, 2014 at 10:02 AM, Nicolas Lalevée >> wrote: >> >>> >>> 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 tickets assigned to 2.4.0, and nothing on 2.3.1, would I be correct in gathering that that's where we're going next?) >>> >>> Yep 2.4.0 should be the next one. >>> >>> I only have one wish. I am working on supporting "packed" (.pack.gz) >>> resources from Eclipse update sites. For that I would need to redesign a >>> feature which is only in trunk: uncompress artifact on resolve (not >>> documented yet, see DefaultRepositoryCacheManager#uncompressArtifact). >>> Since I would like to break it a little bit, I would like to do it before >>> releasing it, so no backward compatibility have to be supported. >>> I am struggling a little bit with it, but I don't think it will take very >>> long. >>> >>> Nicolas >>> >>> >>> - >>> To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org >>> For additional commands, e-mail: dev-h...@ant.apache.org >>> >>> > > > - > To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org > For additional commands, e-mail: dev-h...@ant.apache.org > - To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org For additional commands, e-mail: dev-h...@ant.apache.org
Re: Ivy release schedule
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 a majority of the PMC. > If that's something any committer can do, I'll gladly run the process after > your pending feature is in. I think we have a good doc about how to release: http://ant.apache.org/ivy/history/trunk/dev/makerelease.html I willing to help, especially for the optional publication to the Eclipse updatesite. I'll keep you posted about my progress. Cheers, Nicolas > > Thanks! > > > On Thu, Jan 2, 2014 at 10:02 AM, Nicolas Lalevée > wrote: > >> >> 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 tickets assigned to 2.4.0, and nothing on 2.3.1, would I be >>> correct in gathering that that's where we're going next?) >> >> Yep 2.4.0 should be the next one. >> >> I only have one wish. I am working on supporting "packed" (.pack.gz) >> resources from Eclipse update sites. For that I would need to redesign a >> feature which is only in trunk: uncompress artifact on resolve (not >> documented yet, see DefaultRepositoryCacheManager#uncompressArtifact). >> Since I would like to break it a little bit, I would like to do it before >> releasing it, so no backward compatibility have to be supported. >> I am struggling a little bit with it, but I don't think it will take very >> long. >> >> Nicolas >> >> >> - >> To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org >> For additional commands, e-mail: dev-h...@ant.apache.org >> >> - To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org For additional commands, e-mail: dev-h...@ant.apache.org
Re: Ivy release schedule
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. 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 tickets assigned to 2.4.0, and nothing on 2.3.1, would I be > > correct in gathering that that's where we're going next?) > > Yep 2.4.0 should be the next one. > > I only have one wish. I am working on supporting "packed" (.pack.gz) > resources from Eclipse update sites. For that I would need to redesign a > feature which is only in trunk: uncompress artifact on resolve (not > documented yet, see DefaultRepositoryCacheManager#uncompressArtifact). > Since I would like to break it a little bit, I would like to do it before > releasing it, so no backward compatibility have to be supported. > I am struggling a little bit with it, but I don't think it will take very > long. > > Nicolas > > > - > To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org > For additional commands, e-mail: dev-h...@ant.apache.org > >
Re: Ivy release schedule
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 tickets assigned to 2.4.0, and nothing on 2.3.1, would I be > correct in gathering that that's where we're going next?) Yep 2.4.0 should be the next one. I only have one wish. I am working on supporting "packed" (.pack.gz) resources from Eclipse update sites. For that I would need to redesign a feature which is only in trunk: uncompress artifact on resolve (not documented yet, see DefaultRepositoryCacheManager#uncompressArtifact). Since I would like to break it a little bit, I would like to do it before releasing it, so no backward compatibility have to be supported. I am struggling a little bit with it, but I don't think it will take very long. Nicolas - To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org For additional commands, e-mail: dev-h...@ant.apache.org
Re: Ivy release problem
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: dev-unsubscr...@ant.apache.org For additional commands, e-mail: dev-h...@ant.apache.org
Re: Ivy release problem
No, it still doesn't work: [maart...@minotaur:/www/www.apache.org/dist/ant/ivy]$ ls -al drwxrwsr-x 9 apbackup apsite 9 Jul 14 20:36 . drwxrwsr-x 8 apbackup apsite 19 Jul 9 2008 .. drwxrwsr-x 2 apbackup apsite 26 Jan 19 2009 2.0.0 drwxrwsr-x 2 apbackup apsite 37 Dec 13 2007 2.0.0-beta1 drwxrwsr-x 2 apbackup apsite 26 Mar 3 2008 2.0.0-beta2 drwxrwsr-x 2 apbackup apsite 26 Sep 26 2008 2.0.0-rc1 drwxrwsr-x 2 apbackup apsite 26 Nov 4 2008 2.0.0-rc2 drwxrwsr-x 2 apbackup apsite 26 Mar 30 2009 2.1.0-rc1 drwxrwsr-x 2 apbackup apsite 26 Jul 14 20:39 2.1.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 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 commands, e-mail: dev-h...@ant.apache.org - To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org For additional commands, e-mail: dev-h...@ant.apache.org
Re: Ivy release problem
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: > 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 commands, e-mail: dev-h...@ant.apache.org - To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org For additional commands, e-mail: dev-h...@ant.apache.org
Re: Ivy release problem
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 commands, e-mail: dev-h...@ant.apache.org
Re: Ivy release problem
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've just asked on infrastructure to get it fixed. Stefan - To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org For additional commands, e-mail: dev-h...@ant.apache.org
Re: Ivy release?
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 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 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 Maarten for your involvement and for stepping in for this >> release! >> >> Xavier >> >> On Fri, Sep 4, 2009 at 23:36, Maarten Coene >> wrote: >> >>> Hi all, >>> >>> the second release candidate for Ivy is now some weeks old and it's time >> we >>> decide what to do next. >>> >>> I'd prefer to promote this RC2 as final 2.1.0 release, but merge revision >>> 801820 from trunk which fixes a regression introduced in RC2. >>> Furthermore, since trunk contains fixes for some annoying bugs, we could >>> create a 2.1.1 release candidate later this month after the 2.1.0 final >>> release is out. >>> >>> I'm willing to do the 2.1.0 final release if there a no other volunteers. >>> >>> Maarten >>> >>> >>> >>> >>> >>> - >>> To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org >>> For additional commands, e-mail: dev-h...@ant.apache.org >>> >>> >> >> >> -- >> Xavier Hanin - 4SH France - http://www.4sh.fr/ >> BordeauxJUG creator & leader - http://www.bordeauxjug.org/ >> Apache Ivy Creator - http://ant.apache.org/ivy/ >> - To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org For additional commands, e-mail: dev-h...@ant.apache.org - To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org For additional commands, e-mail: dev-h...@ant.apache.org
Re: Ivy release?
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 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 Maarten for your involvement and for stepping in for this release! Xavier On Fri, Sep 4, 2009 at 23:36, Maarten Coene wrote: Hi all, the second release candidate for Ivy is now some weeks old and it's time we decide what to do next. I'd prefer to promote this RC2 as final 2.1.0 release, but merge revision 801820 from trunk which fixes a regression introduced in RC2. Furthermore, since trunk contains fixes for some annoying bugs, we could create a 2.1.1 release candidate later this month after the 2.1.0 final release is out. I'm willing to do the 2.1.0 final release if there a no other volunteers. Maarten - To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org For additional commands, e-mail: dev-h...@ant.apache.org -- Xavier Hanin - 4SH France - http://www.4sh.fr/ BordeauxJUG creator & leader - http://www.bordeauxjug.org/ Apache Ivy Creator - http://ant.apache.org/ivy/ - To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org For additional commands, e-mail: dev-h...@ant.apache.org
Re: Ivy release?
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 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 Maarten for your involvement and for stepping in for this > release! > > Xavier > > On Fri, Sep 4, 2009 at 23:36, Maarten Coene > wrote: > > > Hi all, > > > > the second release candidate for Ivy is now some weeks old and it's time > we > > decide what to do next. > > > > I'd prefer to promote this RC2 as final 2.1.0 release, but merge revision > > 801820 from trunk which fixes a regression introduced in RC2. > > Furthermore, since trunk contains fixes for some annoying bugs, we could > > create a 2.1.1 release candidate later this month after the 2.1.0 final > > release is out. > > > > I'm willing to do the 2.1.0 final release if there a no other volunteers. > > > > Maarten > > > > > > > > > > > > - > > To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org > > For additional commands, e-mail: dev-h...@ant.apache.org > > > > > > > -- > Xavier Hanin - 4SH France - http://www.4sh.fr/ > BordeauxJUG creator & leader - http://www.bordeauxjug.org/ > Apache Ivy Creator - http://ant.apache.org/ivy/ >
Re: Ivy release?
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 Maarten for your involvement and for stepping in for this release! Xavier On Fri, Sep 4, 2009 at 23:36, Maarten Coene wrote: > Hi all, > > the second release candidate for Ivy is now some weeks old and it's time we > decide what to do next. > > I'd prefer to promote this RC2 as final 2.1.0 release, but merge revision > 801820 from trunk which fixes a regression introduced in RC2. > Furthermore, since trunk contains fixes for some annoying bugs, we could > create a 2.1.1 release candidate later this month after the 2.1.0 final > release is out. > > I'm willing to do the 2.1.0 final release if there a no other volunteers. > > Maarten > > > > > > - > To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org > For additional commands, e-mail: dev-h...@ant.apache.org > > -- Xavier Hanin - 4SH France - http://www.4sh.fr/ BordeauxJUG creator & leader - http://www.bordeauxjug.org/ Apache Ivy Creator - http://ant.apache.org/ivy/
Re: Ivy release schedule
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 week containing all changes made to trunk. Do you know when you will do the merges? We want to release Gradle 0.7 next week and would love to ship with an Ivy that contains those fixes. - Hans -- Hans Dockter Gradle Project Manager http://www.gradle.org - To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org For additional commands, e-mail: dev-h...@ant.apache.org
Re: Ivy release schedule
+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 > containing all changes made to trunk. > If that RC2 doesn't contain critical bugs, we can release it a few weeks > later. > > What do you think? > And as Nicolas stated in one of his mails, this doesn't influence the > upcoming IvyDE release in any way: Ivy and IvyDE can be release > independently from each other... > > Maarten > > > > > > - > To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org > For additional commands, e-mail: dev-h...@ant.apache.org > >
Re: Ivy release schedule
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 a 2.1.0-RC2 next week > containing all changes made to trunk. > If that RC2 doesn't contain critical bugs, we can release it a few weeks > later. > > What do you think? +1 Nicolas > And as Nicolas stated in one of his mails, this doesn't influence the > upcoming IvyDE release in any way: Ivy and IvyDE can be release > independently from each other... > > Maarten > > > > > > - > To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org > For additional commands, e-mail: dev-h...@ant.apache.org - To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org For additional commands, e-mail: dev-h...@ant.apache.org
Re: Ivy release schedule
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 changes made to trunk. > If that RC2 doesn't contain critical bugs, we can release it a few weeks > later. > > What do you think? > And as Nicolas stated in one of his mails, this doesn't influence the > upcoming IvyDE release in any way: Ivy and IvyDE can be release > independently from each other... > > Maarten > > > > > > - > To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org > For additional commands, e-mail: dev-h...@ant.apache.org > > > +1 -- View this message in context: http://www.nabble.com/Ivy-release-schedule-tp23951857p23957246.html Sent from the Ant - Dev mailing list archive at Nabble.com. - To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org For additional commands, e-mail: dev-h...@ant.apache.org
