[GitHub] [jena-site] Aklakan opened a new pull request, #118: ServiceEnhancer: Revision initiated by JENA-1517
Aklakan opened a new pull request, #118: URL: https://github.com/apache/jena-site/pull/118 Added documentation of additional assembler options to configure bulk request aspects. Fixed a few grammar/formatting issues. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@jena.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [jena-site] afs commented on a diff in pull request #117: Improved backup docs https://github.com/apache/jena/issues/1500
afs commented on code in PR #117: URL: https://github.com/apache/jena-site/pull/117#discussion_r965076213 ## source/documentation/tdb2/tdb2_admin.md: ## @@ -67,3 +67,13 @@ continue to be serviced. There is also a command line tool `tdb2.tdbbackup` to run the backup process on a database not in use. + Review Comment: `tdb2.tdbbackup` has had this feature for a long time. `tdb2.tdbbackup` isn't really very important. Nowadays, tarsnaction handling applies to all databases so special casing it isn't necessary. TBH It should probably be removed. The recent PR put the same functionality into Fuseki - they don't share code. The Fuseki code isworks with any database type, integrates into the Fuseki lifecycle and Fuseki logging. Could you put this change in the Fuseki docs please? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@jena.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [] [] Apache Jena 4.6.1 RC1
The Fuseki war file isn't properly copied to dist/jena/binaries/ Some bug in the script that builds the area, not the war file contents. It was missing at 4.6.0 as well. I'll fix it up - it was built and signed properly in the building of the release and is in the ASF "releases" maven repo. https://repository.apache.org/content/repositories/releases/org/apache/jena/jena-fuseki-war/4.6.1/ Andy On 07/09/2022 14:09, Andy Seaborne wrote: The vote passes with 3 +1 votes from Bruno, Rob and Andy. I'll start the next steps, and announce tomorrow. Misc information: The bits go out as: Move the voted source and download binaries from proosed to releas area on SVN. These then propgate to downloads.apache.org/jena - takes a few minutes. Then there is propagation on the Apache CDN (was "mirrors") which can take a while. Because it's a page-CDN, and it has the index page there are links to the places files will be. Any 404's at this point get cached for 2 hours. Propagation to maven central is can take up to 4 hours. Often its more like 20-30 mins. No false 404's. jena-site: update after pushing changes is 15 mins max (you can run the Jenkins job manually to take a few minutes off that). Usually, I wait until bits are in repo1 before sending the [ANN] Andy On 01/09/2022 15:54, Andy Seaborne wrote: Hi, Here is a vote on the release of Apache Jena 4.6.1 This is a bugfix release for GH-1499. This is the first release candidate. The deadline is Monday, 5th September 2022 at 12:00 UTC Please vote to approve this release: [ ] +1 Approve the release [ ] 0 Don't care [ ] -1 Don't release, because ...
[RESULT] [VOTE] Apache Jena 4.6.1 RC1
The vote passes with 3 +1 votes from Bruno, Rob and Andy. I'll start the next steps, and announce tomorrow. Misc information: The bits go out as: Move the voted source and download binaries from proosed to releas area on SVN. These then propgate to downloads.apache.org/jena - takes a few minutes. Then there is propagation on the Apache CDN (was "mirrors") which can take a while. Because it's a page-CDN, and it has the index page there are links to the places files will be. Any 404's at this point get cached for 2 hours. Propagation to maven central is can take up to 4 hours. Often its more like 20-30 mins. No false 404's. jena-site: update after pushing changes is 15 mins max (you can run the Jenkins job manually to take a few minutes off that). Usually, I wait until bits are in repo1 before sending the [ANN] Andy On 01/09/2022 15:54, Andy Seaborne wrote: Hi, Here is a vote on the release of Apache Jena 4.6.1 This is a bugfix release for GH-1499. This is the first release candidate. The deadline is Monday, 5th September 2022 at 12:00 UTC Please vote to approve this release: [ ] +1 Approve the release [ ] 0 Don't care [ ] -1 Don't release, because ...
Re: [VOTE] Apache Jena 4.6.1 RC1
+1 Binding Cheers, Rob From: Andy Seaborne Date: Tuesday, 6 September 2022 at 08:17 To: dev@jena.apache.org Subject: Re: [VOTE] Apache Jena 4.6.1 RC1 Could we get another PMC vote please? Andy On 01/09/2022 15:54, Andy Seaborne wrote: > Hi, > > Here is a vote on the release of Apache Jena 4.6.1 > This is a bugfix release for GH-1499. > This is the first release candidate. > > The deadline is > > Monday, 5th September 2022 at 12:00 UTC > > Please vote to approve this release: > > [ ] +1 Approve the release > [ ] 0 Don't care > [ ] -1 Don't release, because ...
