Call for Discussion: New Project: Skara -- investigating source code management options for the JDK sources
martijnverburg at gmail.com
Fri Jul 27 08:31:28 UTC 2018
The Adoption group has been having a lot of ‘fun’ with importing hg into
git (one of the options that you’ll likely explore) for our git mirrors.
We’ve got a bunch of war stories and most importantly working scripts that
capture history and tags and all that good stuff. They’re Apache 2
licensed at the moment but I’m sure the authors (all being Adoption
members) will be happy to re license or dual license.
Other useful knowledge we can share is around how we manage repos,
projects, issues, work in progress and code reviews at the Adopt build
farm. We’ve learned some valuable lessons of what works and what doesn’t at
a reasonable scale of number of contributors around a git based workflow.
Assuming this project kicks off We’re all very happy to help out!
On Fri, 27 Jul 2018 at 05:13, joe darcy <joe.darcy at oracle.com> wrote:
> The source code management (SCM) system of a software project is a
> fundamental piece of its infrastructure and workflows. Starting in
> February 2008, the source code of different JDK releases and supporting
> projects has been hosted in Mercurial repositories under
> http://hg.openjdk.java.net/. Code reviews of JDK changes are typically
> conducted as discussions in mailing lists over small patches sent to one
> or more lists or over webrevs hosted on cr.openjdk.java.net. Since 2008,
> many open source projects have successfully adopted more efficient SCM
> and review tooling, in some cases provided by third parties.
> In order to help OpenJDK contributors be more productive, both seasoned
> committers and relative newcomers, the Skara project proposes to
> investigate alternative SCM and code review options for the JDK source
> code, including options based upon Git rather than Mercurial, and
> including options hosted by third parties.
> The Skara project intends to build prototypes of hosting the JDK 12
> sources under different providers.
> The evaluation criteria to consider include but are not limited to:
> * Performance: time for clone operations from master repos, time of
> local operations, etc.
> * Space efficiency
> * Usability in different geographies
> * Support for common development environments such as Linux, Mac,
> and Windows
> * Able to easily host the entire history of the JDK and the
> projected growth of its history over the next decade
> * Support for general JDK code review practices
> * Programmatic APIs to enable process assistance and automation of
> review and processes
> If one or more prototypes indicate a different SCM arrangement offers
> substantial improvements over the current situation, the Skara project
> will shepherd a JEP to change the SCM for the JDK.
> I propose to lead the project with the initial reviewers including but
> not limited to Tim Bell (tbell), Erik Duveblad (ehelin), Erik Joelsson
> (erikj), Tiep Vo (tiep), Tony Squier (squierts), and Robin Westberg
> We suggest the build group sponsor this work.
> Changing the bug tracking system is out of scope for this project and is
> *not* under consideration.
Cheers, Martijn (Sent from Gmail Mobile)
More information about the discuss