On Mon, 27 May 2019 at 21:19, Vladimir Sitnikov <[email protected]> wrote: > > Hi, > > This thread has been idle for a while. > > The results (re move to Gradle) so far are: > +1 (binding) Philippe Mouawad > ++1 (binding) Vladimir Sitnikov > +1 (binding) Antonio Gomes Rodrigues > +1 Andrey Pokhilko > +1 Graham Russell > +1 (binding) Milamber > > No vetos detected. > > That is there's a consensus to use Git for source code.
OK > As you might know I have created a script to cleanup the repository: > https://github.com/vlsi/jmeter-git-cleanup > I just re-ran the script, and here's the result: > https://github.com/vlsi/jmeter-git-cleanup-result -1, because that loses all the SVN history. AFAICT, there is no way to find historic SVN revisions in the cleaned-up repo Also, where in the history are the files that have been deleted? > If no objections, I can start migration from SVN to Git. > The process is as follows: INFRA uses the provided repo and copies the > result to /apache/jmeter.git, and setups the infrastructure accordingly. I think INFRA need to review the script to make sure that it preserves all necessary provenance. > Note: I think it makes sense to do Ant+SVN -> Gradle+Git as a single > change. That would simplify the evaluation and review (both repositories > would be perfectly buildable). > If we go with Ant+SVN -> Ant+Git -> Gradle+Git route, then the intermediate > Ant+Git would probably contain its own bugs, and we would just spend time > on analyzing/fixing those. That can be tested now, by using the existing GitHub read-only mirror. > However I'm open to suggestions. If there are reasons to move from SVN to > Git first, it can definitely be done assuming we don't add Git support to > build.xml. > > If no objections received, I'll proceed with Ant+SVN -> Gradle+Git approach > as vote for Gradle resolves. -1 to combining Git with Gradle for the reasons stated above. > Vladimir
