AW: VOTE Retire IvyDE - RESULT

[jhm]

The vote about archiving IvyDE starts on 05.December 2016 [1].
The result is:
* binding votes
   +1: (Jan), (Nicolas), Jean-Louis, Dominique,  
0: Stefan
   -1: --
   asks for cancelling: Nicolas [3], Jan [4]
* non binding votes
   +1: --
0: --
   -1: Gintas [2]

I interpret the asks for cancelling as changing from a +1 to a -1, so we 
haven't more +1 than -1.
Therefore the vote failed and IvyDE will be alive as it is.

I am happy that the discussion about archiving brings such an amount of new 
energy. ;-)


Jan

[1] 
http://mail-archives.apache.org/mod_mbox/ant-dev/201612.mbox/ajax/%3C001301d24ec5%24e0040790%24a00c16b0%24%40de%3E
[2] 
http://mail-archives.apache.org/mod_mbox/ant-dev/201612.mbox/ajax/%3CCALVNWHVZs6wSSKqG1wCN8sZsBPApg%3Dg1Q%2B0%3DZqg9h81pOOtpOg%40mail.gmail.com%3E
[3] 
http://mail-archives.apache.org/mod_mbox/ant-dev/201612.mbox/ajax/%3C2E959BA8-CCBE-4C24-B0A9-831655AD8E9D%40hibnet.org%3E
[4] 
http://mail-archives.apache.org/mod_mbox/ant-dev/201612.mbox/ajax/%3C002701d2518d%24e827b280%24b8771780%24%40de%3E



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

AW: VOTE Retire EasyAnt subproject - RESULT

[jhm]

The vote about archiving EasyAnt starts on 05.December 2016 [1].
The result is:
* binding votes
   +1: Jan, Stefan, Nicolas, Conor, Jean-Louis, Dominique
0: --
   -1: --
* non binding votes
   +1: --
0: --
   -1: --

The vote passed and EasyAnt including all its subcomponents will be archived 
according to the specified process [2].


[1] 
http://mail-archives.apache.org/mod_mbox/ant-dev/201612.mbox/ajax/%3C000e01d24ec5%24dfd88ac0%249f89a040%24%40de%3E
[2] http://ant.apache.org/processes.html


Jan



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

[GitHub] ant-ivy issue #12: IVY-1482 Fix potential NPE in XmlReportOutputter

[jaikiran]

Github user jaikiran commented on the issue:

https://github.com/apache/ant-ivy/pull/12
  
Closing this PR, since the commit here 
https://github.com/apache/ant-ivy/commit/c4bb60046de9ffdd1cf07cfcdba201df06b194dd
 handles it in a better way.



---
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...@ant.apache.org
For additional commands, e-mail: dev-h...@ant.apache.org

[GitHub] ant-ivy pull request #12: IVY-1482 Fix potential NPE in XmlReportOutputter

[jaikiran]

Github user jaikiran closed the pull request at:

https://github.com/apache/ant-ivy/pull/12


---
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...@ant.apache.org
For additional commands, e-mail: dev-h...@ant.apache.org

Re: Ivy - Proposal for reviving the project and moving towards a release

[Maarten Coene]

Thanks Jaikran,
I will look at your patches, I'll try to do it this week.If possible, please 
attach a junit test as well to reproduce the problem.

About the release, the master branch already contains some fixes since the 
2.4.0 release. They are listed in the release-notes.html in the 'doc' 
directory. If we want to create a 2.4.1 release, we should merge all these 
changes (and all upcomming patches) into the 2.4.x branch as well. If we decide 
to create a 2.5.0 release, this merging isn't necessary. I wouldn't pin on an 
exact timing, we can create a release any time when we think the codebase is 
ready for it.

We also have to find a release manager. I did it in the past when we were on 
SVN, but I don't have enough GIT knowledge (and I don't have the time to look 
into it) to do a new release. 

Maarten

  Van: Jaikiran Pai 
 Aan: dev@ant.apache.org 
 Verzonden: zondag 11 december 15:22 2016
 Onderwerp: Ivy - Proposal for reviving the project and moving towards a release
   
First off, I'm not an Ivy or Ant committer. The proposal that I make 
below for an Ivy release is based on what was discussed in a recent mail 
thread about the future of Ivy 
https://www.mail-archive.com/dev@ant.apache.org/msg45078.html. There was 
a suggestion that someone from community volunteer to try and bring in 
some activity into the project and see if we can create a release after 
triaging the JIRA issues.


I have had a look at the open issues in JIRA today and decided to filter 
out issues that are open, updated since Jan 2014 and affects versions 
2.1, 2.2, 2.3 and 2.4. I decided to use this as a filter criteria to 
just select a few that I thought can be considered "active". This [1] 
returns 57 issues. I went ahead and looked at those issues today and 
have asked for more information in the JIRAs wherever relevant and have 
sent a couple of pull requests [2] [3] to fix some straightforward ones. 
I also have another PR that I opened this week to fix one other issue. 
Out of those 57 issues, many are no longer relevant or don't have enough 
details. I don't have JIRA privileges to label them, share filters or 
even assign some to myself to track them better. So I think for now, we 
can rely on that JIRA search query [1].

At this point, I think, if we can target March 2017 for releasing a 
2.4.1-Beta-1 with fixes from the list of JIRAs I think that would be a 
good start. Some of the issues noted in that JIRA are indeed important 
ones and would need some review/help in fixing them correctly, which 
essentially means, we need at least one person who has had experience 
with the Ivy code and its design details and also has the committer rights.


Does any of this look feasible? Let me know if this isn't enough to move 
things forward - I don't want to end up sending PRs and spending time on 
this if there's no way we can get to a proper release in the next few 
months.


[1] 
https://issues.apache.org/jira/browse/IVY-1553?jql=project%20%3D%20IVY%20AND%20status%20in%20(Open%2C%20%22In%20Progress%22%2C%20Reopened)%20AND%20affectedVersion%20in%20(2.1.0%2C%202.2.0%2C%202.3.0%2C%202.4.0%2C%202.4.0-RC1)%20AND%20updated%20%3E%3D%202014-01-01%20ORDER%20BY%20updated%20DESC

[2] https://github.com/apache/ant-ivy/pull/11

[3] https://github.com/apache/ant-ivy/pull/12

-Jaikiran

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