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

[J Pai]

Maarten, thanks for volunteering to review the PRs. One of them has a test
case. I will add a test for the other one.

It looks like you have been involved with Ivy development and releases
before, so I think you would be in a better position to decide if it should
be 2.5.0 or 2.4.1. I personally prefer 2.4.1 because we are focussing on
fixing some reported issues rather than introducing some new features.

As for the release timeline, the reason I asked for a March 2017 date is to
make sure we have a realistic goal in mind of releasing it instead of a
open ended one which drags can potentially drag on for a while given the
current state of the project. Having said that, you and others in ant-dev
team who have been involved in previous releases can decide what makes
sense in terms of release commitments. My whole goal is to try and get a
usable bug fix release out soon, since the last one was 2 years back.

-Jaikiran

On Monday, December 12, 2016, Maarten Coene 
wrote:
> 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
>
>
>
>

Re: IvyDE status

[Gintautas Grigelionis]

Thanks for clarification. There are lots of duplications around there, and
the overall process would surely benefit from some restructuring. I took
the liberty of extracting the commits particular to style subdirectory
(there are three of them, identical in ivy/source and ivyde/source trees).
I would happily push them to Github if I had a permission to
https://github.com/apache/any-ivy-site-styles, otherwise you may follow
this procedure

> svn log http://svn.apache.org/repos/asf/ant/site/ivyde/sources/style
[note the first commit at the bottom which is 501128]
> git svn clone --no-minimize-url -r501128
http://svn.apache.org/repos/asf/ant/site/ivyde/sources/style
> cd style
> GIT_TRACE=1 git svn fetch --log-window-size 10

then add Github as remote and push (took me less than 5 minutes on a
MacBook).

Gintas


2016-12-13 17:26 GMT+01:00 Stefan Bodewig :

> On 2016-12-11, Gintautas Grigelionis wrote:
>
> > I have a question, too: perhaps the entire ivyde site repo could be
> > converted to Git?
>
> The "ivyde site" is only a subdirectory of the whole of the Ant project
> website.
>
> Back when we migrated to git the way the ASF web hosting worked meant
> the site had to be in svn - published via svnpubsub. I think there is an
> alternative git workflow by now, but it won't be feasible to convert
> only part of the site. So it would be all or nothing.
>
> Stefan
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
> For additional commands, e-mail: dev-h...@ant.apache.org
>
>

Re: IvyDE status

[Stefan Bodewig]

On 2016-12-11, Gintautas Grigelionis wrote:

> I have a question, too: perhaps the entire ivyde site repo could be
> converted to Git?

The "ivyde site" is only a subdirectory of the whole of the Ant project
website.

Back when we migrated to git the way the ASF web hosting worked meant
the site had to be in svn - published via svnpubsub. I think there is an
alternative git workflow by now, but it won't be feasible to convert
only part of the site. So it would be all or nothing.

Stefan

-
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

[Stefan Bodewig]

On 2016-12-12, Maarten Coene wrote:

> 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, is this

the guide you've been working from when you last cut a release?

It looks as if Nicolas had already converted it to use git commands
rather than svn. I'll be happy to proof-read the changes, but am pretty
certain they are correct.

Stefan

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

Re: archiving EasyAnt

[Stefan Bodewig]

On 2016-12-13, Jan Matèrne (jhm) wrote:

> - Gump: it seems, that there is no buildjob for EA
>   https://svn.apache.org/viewvc/gump/metadata/profile/gump.xml?view=markup
>   @Stefan: as our Gump master ;) please check

True, EasyAnt has never been added to Gump.

Stefan

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

archiving EasyAnt

[jhm]

The vote about archiving EasyAnt passed [1].
So according to [2] the todo list is:

Retire: Version Control 
---
Most of our source code is in git, only "site" and "sandbox" use subversion.

--> only git for sources. Homepage in svn.

We place a marker RETIRED_PROJECT file on the top level. 
--> done (will commit that after deleting the build jobs)

Add a note at the top of a README file as well so it is immediately visible
to people browsing the github mirror. 
--> done, dito

Include a link to this page for a possible future reactivation and a link to
the vote result. 
--> done

Ask infra to make the repository read-only. 
--> open


Retire: Issue Tracker 
-
If the subproject/component has its own issue tracker we have to close that.
It is enough to make it read-only, so these information are longer
available. 
--> open; use Jira EASYANT


Retire: Mailing List 

If the subproject/component has its own mailing list we have to close this.
We should send a final email. 
--> no mailing list; used dev|us...@ant.ao


Retire: Announcement 

We have to announce the retirement of the subproject at dev@ant,
announce@apache and the Ant main page. 
--> open


Retire: Build Jobs 
--
All build jobs on Jenkins@Apache, TeamCity and Gump have to be deleted. 
- Jenkins: deleted "EasyAnt" (standard build job), updated
http://ant.apache.org/nightlies.html
- TeamCity: no build jobs there
- Gump: it seems, that there is no buildjob for EA
  https://svn.apache.org/viewvc/gump/metadata/profile/gump.xml?view=markup
  @Stefan: as our Gump master ;) please check


Retire: Homepage 

Add the retirement to the archive-page. 
--> done


Retire: Releases 

The last released artifacts, if any, should be removed from the Apache
distribution server. To do so, remove any artifact related to the retired
subproject in https://dist.apache.org/repos/dist/release/ant/ (it is managed
with subversion). 
--> open


Retire: Free Further Resources 
--
Maybe a subproject locks further resources (update-site, ...). So we have to
unblock them. 
--> open: I am not aware of any resources. Someone else?



Jan



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