We had a list of branches .... https://ci-maven.apache.org/job/Maven/job/maven-box/job/maven-dist-tool/job/master/site/dist-tool-branches.html - but now is an issue an report is not generated
On Sat, 4 Jan 2025 at 22:00, Gerd Aschemann <g...@aschemann.net> wrote: > > I am about to run some analysis of the overall Maven project with jQAssistant > in the next weeks (currently I am fighting with some problems with the tool > as it is really a large codebase). > > However, as a quick win I can provide some data about the number of branches. > The attached Excel lists all (133) projects and their current number of > branches. Some numbers are large (~30% have 10 or more branches). > > I hope I should be able to give more detailed reports in the next weeks. > It should also be possible to correlate branches to Jira issues (if they are > mentioned in the branch name or commit messages) and cross check whether they > are still necessary. > Additionally it should be possible to identify branches which are not > correlated to some ticket and sort out with the latest committers what is the > purpose of the branches. > > > > On 4. Jan 2025, at 21:12, Andy Law <andy....@roslin.ed.ac.uk> wrote: > > I’m a lurker on this list, albeit one that’s wanting to find time to add a > feature to the enforcer plugin. > > I’m with Tamás on this, not least because then all code updates will be > coming in through the same route, be they from you outstanding worthies or > from us occasional self-interest contributors. > > Later, > > Andy > > From: Elliotte Rusty Harold <elh...@ibiblio.org> > Date: Saturday, 4 January 2025 at 18:02 > To: Maven Developers List <dev@maven.apache.org> > Subject: Re: Using git forks > This email was sent to you by someone outside the University. > You should only click on links or attachments if you are certain that the > email is genuine and the content is safe. > > On Sat, Jan 4, 2025 at 4:20 PM Tamás Cservenák <ta...@cservenak.net> wrote: > > > > But to continue: what will happen to branches named like "mdo", > "apidoc", "copy", "null" etc in _cnonical maven repo_ if you go > missing? > > > Branches are cheap, but the way these things work if these aren't > cleaned up manually, eventually the project will move off git and > github and throw away its history. All this has happened before, and > all this will happen again . > > I've worked on enough Github hosted projects where all committers use > branches and only branches to be reasonably confident that the problem > is not the use of branches. Branches are how git works, and they work > just fine. Maven does seem to have a lot of old tooling that needs > work, though I'm not sure who has the knowledge or permissions to do > that. But meanwhile adding more layers of rules for developers to > follow instead of fixing broken tooling — like apparently whatever is > sending commit messages to the mailing list — is not the way to go. > > -- > Elliotte Rusty Harold > elh...@ibiblio.org > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > The University of Edinburgh is a charitable body, registered in Scotland, > with registration number SC005336. Is e buidheann carthannais a th’ ann an > Oilthigh Dhùn Èideann, clàraichte an Alba, àireamh clàraidh SC005336. > > > -- > Gerd Aschemann --- Veröffentlichen heißt Verändern (Carmen Thomas) > +49/173/3264070 -- g...@aschemann.net -- http://www.aschemann.net > -- Sławomir Jaranowski --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
