Commit notifications from gitbox [was [ant] branch master updated (706d818 -> 722ccb7)]

2018-12-21 Thread Jaikiran Pai
Adding us...@infra.apache.org. Comments inline.

On 21/12/18 1:01 AM, bode...@apache.org wrote:
> This is an automated email from the ASF dual-hosted git repository.
>
> bodewig pushed a change to branch master
> in repository https://gitbox.apache.org/repos/asf/ant.git.
>
>
> from 706d818  moved to gitbox
>  add 82a603c  Use valid markup
>  new 722ccb7  Merge pull request #82 from twogee/invalid-html
>
> The 1 revisions listed above as "new" are entirely new to this
> repository and will be described in separate emails.  The revisions
> listed as "add" were already present in the repository and have only
> been added to this reference.

This looks a bit odd. The "Use valid markup" is a new commit and wasn't
there in the upstream repository previously, so not sure why it's being
considered as already present.

Furthermore, the other mail notification which contained the details
about the "new" just listed the files that changed and the line count of
changes. Previously, when we were on git.wip-us repo, these
notifications used to inline the diff within one or more emails and that
format was very convenient to do reviews. Would it be possible to have a
similar format (at least for Ant project(s)) for these notifications?

-Jaikiran


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



Re: [VOTE] Retire Antlib SVN

2018-12-21 Thread Jaikiran Pai
An implicit +1.

-Jaikiran


On 22/12/18 7:39 AM, Jaikiran Pai wrote:
> This is a proposal to retire the "Antlib SVN" library[1]. The project
> hasn't seen any new development for many years now[2]. Retiring this
> will reduce the work necessary to maintain it[3] (Jekins jobs etc...).
>
> More about retiring a project or a project component can be found here[4].
>
>
> [1] http://ant.apache.org/antlibs/svn/
>
> [2] https://github.com/apache/ant-antlibs-svn/commits/master
>
> [3]
> https://mail-archives.apache.org/mod_mbox/ant-dev/201812.mbox/%3c87k1k5wg7a@v45346.1blu.de%3e
>
> [4] http://ant.apache.org/processes.html
>
> -Jaikiran
>
>


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



[VOTE] Retire Antlib SVN

2018-12-21 Thread Jaikiran Pai
This is a proposal to retire the "Antlib SVN" library[1]. The project
hasn't seen any new development for many years now[2]. Retiring this
will reduce the work necessary to maintain it[3] (Jekins jobs etc...).

More about retiring a project or a project component can be found here[4].


[1] http://ant.apache.org/antlibs/svn/

[2] https://github.com/apache/ant-antlibs-svn/commits/master

[3]
https://mail-archives.apache.org/mod_mbox/ant-dev/201812.mbox/%3c87k1k5wg7a@v45346.1blu.de%3e

[4] http://ant.apache.org/processes.html

-Jaikiran



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



AW: Antlib SVN and antunit Java versions

2018-12-21 Thread jhm
Retiring a part of a top level project is much easier than retiring the TLP 
itself.
We have created a "process" while archiving EasyAnt & Co:
http://ant.apache.org/processes.html#Retire%20a%20subproject%20or%20component
Basically
* PMC vote for retiring the thing
* make resources read-only (code, mailinglists, issue tracker)
* clear all resources (build jobs)
* make it public (homepage, announcement)


Jan

> -Urspr√ľngliche Nachricht-
> Von: Jaikiran Pai [mailto:jaiki...@apache.org]
> Gesendet: Donnerstag, 20. Dezember 2018 14:52
> An: dev@ant.apache.org
> Betreff: Re: Antlib SVN and antunit Java versions
> 
> 
> On 19/12/18 11:29 PM, Stefan Bodewig wrote:
> > On 2018-12-18, Jaikiran Pai wrote:
> >
> >> One option in similar cases that we have employed in other jobs is
> to
> >> configure the Java system property -Dhttps.protocols to "TLSv1.2".
> >> But this version of TLS is only supported in a Java release after
> Java 1.5.
> > I'd be in favor of updating the jobs. Nobody would build releases
> > using Java 1.5 either, I guess.
> Done. I have updated the jobs of antlib svn and antunit to use Java 8
> to build it.
> 
> >
> >> At a more higher level, I think it's probably time to decide whether
> >> we want to change the minimum required Java versions for these
> libraries?
> >> Should we now mandate Java 1.8 at least?
> > In the case of antlib svn we could simply decide to call it dead or
> > dormant or whatever (like almost all other antlibs, I guess). Unless
> > I'm overlooking something, the svn antlib is neither listed on
> > http://ant.apache.org/antlibs/proper.html nor
> > http://ant.apache.org/antlibs/sandbox.html - so it doesn't even exist
> > from out user's point of view.
> I found this (live) page http://ant.apache.org/antlibs/svn/ the other
> day while looking at the Jenkins failure. But now that you mention it,
> I don't remember how I landed up on that page. I don't see it linked in
> the Jenkins job or some other place. But yes, I don't see it linked
> anywhere in the Ant website. I'll start a new VOTE thread to retire
> this project. I might need Jan's help here if/after the VOTE passes to
> actually do some of the process involved in retiring projects.
> 
> -Jaikiran
> 
> 
> 
> 
> -
> 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