Re: [Lazy] Jena5 Branch
On 12/10/2023 10:40, Bruno Kinoshita wrote: ... Given that I believe most of the Jena development should now be focused on Jena5, wouldn't it make more sense to create a Jena4 branch, merge Jena5 branch into main, and backport bug fixes to the Jena4 branch as needed? I think we might even be able to cut releases from that branch. The maven release plugin should work on a branch. That way, I think we could say that the official version under development is Jena5, and Jena4 is now in hotfix maintenance, until Jena5 is released (plus whatever time we need/can to support it in the future). Good point about the showing jena5 is the "official version under development". Since 4.9.0, there are about 18 closed non-Jena5 issues, and 37 PRs mostly dependency upgrades. https://s.apache.org/jena-4.10.0-issues. I think we should do 4.10.0 as normal (which is "soon"ish), wait a bit to make sure nothing horrendous turns up, then switch. It creates space for 5.0.0 in the release cycle. That becomes the official split point jena4 and jena5. No more rebasing jena4 onto jena5! 5.0.0 might be a -beta or -M1 or -rc1, though I'm not sure how much take up they will at our scale. There are changes which will slow switch over, but other than that it's at the same usability level of 4.x.x. "main" is protected - no forced pushes - so seeing Jena5 hasn't got some that it is reasonably stable, has been building SNAPSHOTs and has been used. Andy Cheers Bruno On Thu, 12 Oct 2023 at 11:05, Andy Seaborne wrote: On 06/10/2023 11:47, Andy Seaborne wrote: There's a large PR for a new branch "jena5" https://github.com/apache/jena/pull/2029 of what I've managed to do so far. It's not finished. Andy I'd like to bring the PR in as a branch and setup Jenkins to produce snapshot artifacts. The branch might still liable to force pushes to keep the history comprehensible, such as rebasing it to main, and finally when switching to this branch to be main if we use rebase and merge. I think having a baseline for people to look at and maybe even try out, is better than waiting until the very last minute to become Jena5. Maybe we should use rebase and merge" for PRs from now on? Andy
Re: [Lazy] Jena5 Branch
(Maybe we can also change the base branch of any existing pull request to that Jena4 branch, so even in the future after we merge Jena5 into main, those PR's could be left reviewed for Jena4 if needed?) On Thu, 12 Oct 2023 at 11:40, Bruno Kinoshita wrote: > Hi Andy, > > Maybe we should use rebase and merge" for PRs from now on? >> > > I try to use rebase and merge as it works best for me to keep the git > commit tree in order, so I'm +1 for that. > > I'd like to bring the PR in as a branch and setup Jenkins to produce >> snapshot artifacts. >> >> The branch might still liable to force pushes to keep the history >> comprehensible, such as rebasing it to main, and finally when switching >> to this branch to be main if we use rebase and merge. >> > > Given that I believe most of the Jena development should now be focused on > Jena5, wouldn't it make more sense to create a Jena4 branch, merge Jena5 > branch into main, and backport bug fixes to the Jena4 branch as needed? > > I think we might even be able to cut releases from that branch. > > That way, I think we could say that the official version under development > is Jena5, and Jena4 is now in hotfix maintenance, until Jena5 is released > (plus whatever time we need/can to support it in the future). > > Cheers > > Bruno > > > > On Thu, 12 Oct 2023 at 11:05, Andy Seaborne wrote: > >> >> On 06/10/2023 11:47, Andy Seaborne wrote: >> > There's a large PR for a new branch "jena5" >> > >> > https://github.com/apache/jena/pull/2029 >> > >> > of what I've managed to do so far. >> > >> > It's not finished. >> > >> > Andy >> >> I'd like to bring the PR in as a branch and setup Jenkins to produce >> snapshot artifacts. >> >> The branch might still liable to force pushes to keep the history >> comprehensible, such as rebasing it to main, and finally when switching >> to this branch to be main if we use rebase and merge. >> >> I think having a baseline for people to look at and maybe even try out, >> is better than waiting until the very last minute to become Jena5. >> >> Maybe we should use rebase and merge" for PRs from now on? >> >> Andy >> >
Re: [Lazy] Jena5 Branch
Hi Andy, Maybe we should use rebase and merge" for PRs from now on? > I try to use rebase and merge as it works best for me to keep the git commit tree in order, so I'm +1 for that. I'd like to bring the PR in as a branch and setup Jenkins to produce > snapshot artifacts. > > The branch might still liable to force pushes to keep the history > comprehensible, such as rebasing it to main, and finally when switching > to this branch to be main if we use rebase and merge. > Given that I believe most of the Jena development should now be focused on Jena5, wouldn't it make more sense to create a Jena4 branch, merge Jena5 branch into main, and backport bug fixes to the Jena4 branch as needed? I think we might even be able to cut releases from that branch. That way, I think we could say that the official version under development is Jena5, and Jena4 is now in hotfix maintenance, until Jena5 is released (plus whatever time we need/can to support it in the future). Cheers Bruno On Thu, 12 Oct 2023 at 11:05, Andy Seaborne wrote: > > On 06/10/2023 11:47, Andy Seaborne wrote: > > There's a large PR for a new branch "jena5" > > > > https://github.com/apache/jena/pull/2029 > > > > of what I've managed to do so far. > > > > It's not finished. > > > > Andy > > I'd like to bring the PR in as a branch and setup Jenkins to produce > snapshot artifacts. > > The branch might still liable to force pushes to keep the history > comprehensible, such as rebasing it to main, and finally when switching > to this branch to be main if we use rebase and merge. > > I think having a baseline for people to look at and maybe even try out, > is better than waiting until the very last minute to become Jena5. > > Maybe we should use rebase and merge" for PRs from now on? > > Andy >
[Lazy] Jena5 Branch
On 06/10/2023 11:47, Andy Seaborne wrote: There's a large PR for a new branch "jena5" https://github.com/apache/jena/pull/2029 of what I've managed to do so far. It's not finished. Andy I'd like to bring the PR in as a branch and setup Jenkins to produce snapshot artifacts. The branch might still liable to force pushes to keep the history comprehensible, such as rebasing it to main, and finally when switching to this branch to be main if we use rebase and merge. I think having a baseline for people to look at and maybe even try out, is better than waiting until the very last minute to become Jena5. Maybe we should use rebase and merge" for PRs from now on? Andy
[Draft] Apache Jena - October 2023
## Description: The mission of Jena is the creation and maintenance of software related to Java framework for building Semantic Web applications ## Project Status: Current project status: Ongoing Issues for the board: None ## Membership Data: Apache Jena was founded 2012-04-18 (11 years ago) There are currently 19 committers and 13 PMC members in this project. The Committer-to-PMC ratio is roughly 5:4. Community changes, past quarter: - No new PMC members. Last addition was Aaron Coburn on 2019-01-22. - Arne Bernhardt was added as committer on 2023-07-11 ## Project Activity: Development is now around Jena 5, using the major version change for both external changes and code improvements. External changes include building convenience binaries for Java17 in keeping with the project supporting two Java LTS; switching from javax.servlet to jakarta.servlet); update to Eclipse Jetty12; and removing a dependency from a project that is no longer active. Project development for Jena5 includes removing deprecated code and tidying up. There is a new standards compliant RDF/XML parser which is both faster and easier to maintain. ## Community Health: The community continues to answer questions on the users list. The dev list has been quieter because the project has moved some more automated email off that list, general seasonal effects, and because the Jena5 development has proceeded on github.
unattended-upgrades result for jena-vm.apache.org: SUCCESS
Unattended upgrade result: All upgrades installed Packages that were upgraded: curl libcurl3-gnutls libcurl4 libtiff5 Package installation log: Log started: 2023-10-12 06:44:32 apt-listchanges: Reading changelogs... apt-listchanges: Reading changelogs... Preparing to unpack .../libtiff5_4.1.0+git191117-2ubuntu0.20.04.10_amd64.deb ... Unpacking libtiff5:amd64 (4.1.0+git191117-2ubuntu0.20.04.10) over (4.1.0+git191117-2ubuntu0.20.04.9) ... Setting up libtiff5:amd64 (4.1.0+git191117-2ubuntu0.20.04.10) ... Processing triggers for libc-bin (2.31-0ubuntu9.12) ... Log ended: 2023-10-12 06:44:35 Log started: 2023-10-12 06:44:36 apt-listchanges: Reading changelogs... apt-listchanges: Reading changelogs... Preparing to unpack .../curl_7.68.0-1ubuntu2.20_amd64.deb ... Unpacking curl (7.68.0-1ubuntu2.20) over (7.68.0-1ubuntu2.19) ... Preparing to unpack .../libcurl4_7.68.0-1ubuntu2.20_amd64.deb ... Unpacking libcurl4:amd64 (7.68.0-1ubuntu2.20) over (7.68.0-1ubuntu2.19) ... Setting up libcurl4:amd64 (7.68.0-1ubuntu2.20) ... Setting up curl (7.68.0-1ubuntu2.20) ... Processing triggers for man-db (2.9.1-1) ... Processing triggers for libc-bin (2.31-0ubuntu9.12) ... Log ended: 2023-10-12 06:44:39 Log started: 2023-10-12 06:44:39 apt-listchanges: Reading changelogs... apt-listchanges: Reading changelogs... Preparing to unpack .../libcurl3-gnutls_7.68.0-1ubuntu2.20_amd64.deb ... Unpacking libcurl3-gnutls:amd64 (7.68.0-1ubuntu2.20) over (7.68.0-1ubuntu2.19) ... Setting up libcurl3-gnutls:amd64 (7.68.0-1ubuntu2.20) ... Processing triggers for libc-bin (2.31-0ubuntu9.12) ... Log ended: 2023-10-12 06:44:44 Unattended-upgrades log: Starting unattended upgrades script Allowed origins are: origin=Ubuntu,suite=focal, origin=Ubuntu,suite=focal-security, origin=Ubuntu,suite=focal-backports, origin=Ubuntu,suite=focal-updates Initial blacklist: Initial whitelist (not strict): Packages that will be upgraded: curl libcurl3-gnutls libcurl4 libtiff5 Writing dpkg log to /var/log/unattended-upgrades/unattended-upgrades-dpkg.log All upgrades installed
