Attendees: Michael Bouschen, Tilmann Zäschke, Tobias Bouschen, Craig Russell
Next meeting: Tuesday June 11 1100 PDT 2000 CEST
Agenda:
1. JIRA JDO-835 "TCK: Check ResultClassRequirementsMap when running
multithreaded" https://issues.apache.org/jira/browse/JDO-835
2. JIRA JD
Sorry for the error. I trust no one was confused...
Craig
> On May 15, 2024, at 00:29, Michael Bouschen wrote:
>
> Hi,
>
> just a small remark below ...
>
>> Attendees: Michael Bouschen, Tilmann Zäschke, Tobias Bouschen, Craig Russell
>>
>> Next meetin
Attendees: Michael Bouschen, Tilmann Zäschke, Tobias Bouschen, Craig Russell
Next meeting: Tuesday May 21 1100 PDT 2000 CEST
Agenda:
1. JIRA JDO-835 "TCK: Check ResultClassRequirementsMap when running
multithreaded" https://issues.apache.org/jira/browse/JDO-835
Before executing
Attendees: Michael Bouschen, Tilmann Zäschke, Craig Russell
Next meeting: Tuesday May 14 1100 PDT 2000 CEST
Agenda:
1. JIRA JDO-835 "TCK: Check ResultClassRequirementsMap when running
multithreaded" https://issues.apache.org/jira/browse/JDO-835
2. JIRA JDO-836 "TCK: QueryCa
Attendees: Michael Bouschen, Tobias Bouschen, Tilmann Zäschke, Craig Russell
Next meeting: Tuesday May 7 1100 PDT 2000 CEST
Agenda:
1. JIRA JDO-835 "TCK: Check ResultClassRequirementsMap when running
multithreaded" https://issues.apache.org/jira/browse/JDO-835
2. JIRA JD
Attendees: Michael Bouschen, Tilmann Zäschke, Craig Russell
Next meeting: Tuesday April 30 1100 PDT 2000 CEST
Agenda:
1. JIRA JDO-835 "TCK: Check ResultClassRequirementsMap when running
multithreaded" https://issues.apache.org/jira/browse/JDO-835
2. JIRA JDO-836 "TCK: QueryCa
Attendees: Michael Bouschen, Tilmann Zäschke, Tobias Bouschen, Craig Russell
Next meeting: Tuesday April 23 1100 PDT 2000 CEST
Agenda:
1. db-jdo-site PR #52 "JDO-840: Fix changes links on JDO news site"
https://github.com/apache/db-jdo-site/pull/52
Good to go. Ok to merge.
2. JI
Attendees: Michael Bouschen, Tilmann Zäschke, Tobias Bouschen, Craig Russell
Next meeting: Tuesday April 16 1100 PDT 2000 CEsT
Agenda:
1. News for our April report to the board?
No additional news. Thanks to Bryan for taking care of this.
2. db-jdo-site PR #51 "Update downloads.adoc&qu
Hi Rick,
Thanks so much for all of the work you did for us in this. Much more than I was
expecting.
Best regards,
Craig
> On Mar 26, 2024, at 13:54, Rick Hillegas wrote:
>
> Hey Craig,
>
> At the end of this message, I have attached a program which demonstrates the
> behavior of
Attendees: Michael Bouschen, Tobias Bouschen, Craig Russell
Next meeting: Tuesday April 9 1100 PDT 2000 CEsT
Agenda:
1. ASF - Infra newsletter for March, 2024: Policy change on use of GitHub
Actions for heavy users.
This does not affect the JDO project.
2. New db-jdo-site PR #51 "U
Hi,
You may notice that JDO is having a bit of a hard time trying to get our test
for canceling a query to work. Our specification calls for throwing an
exception if the JDBC driver does not support it. Our reference implementation
is DataNucleus.
I'd like to verify that since you do not
Let's discuss this new Github policy on our normal schedule. Comments here,
decisions here or at our regular meetings.
WDYT?
> Begin forwarded message:
>
> From: Andrew Wetmore
> Subject: ASF - Infra newsletter for March, 2024
> Date: March 23, 2024 at 05:59:32 PDT
> To: Users
>
> Welcome
Attendees: Michael Bouschen, Tilmann Zäschke, Craig Russell
Next meeting: Tuesday March 26 1200 PDT 2000 CET
Agenda:
1. JIRA JDO-835 "TCK: Check ResultClassRequirementsMap when running
multithreaded" https://issues.apache.org/jira/browse/JDO-835
2. JIRA JDO-836 "TCK: QueryCa
Attendees: Michael Bouschen, Tilmann Zäschke, Craig Russell
Next meeting: Tuesday March 19 1200 PDT 2000 CET
Agenda:
1. JIRA JDO-835 "TCK: Check ResultClassRequirementsMap when running
multithreaded" https://issues.apache.org/jira/browse/JDO-835
No change.
2. JIRA JDO-836 "T
Attendees: Michael Bouschen, Tilmann Zäschke, Tobias Bouschen, Craig Russell
Next meeting: Tuesday March 12 1100 PST 2000 CET
Agenda:
1. Update GitHub Action versions
Tobias merged the change to update GitHub Action versions.
2. JIRA JDO-838 "Clarify doc for query cancel()/cancelAll()&qu
45 PST
> To: derby-...@db.apache.org, Craig Russell
>
> Hey Craig,
>
> I don't know how DataNucleus tries to cancel a query.
>
> jdbc.sql.Statement.cancel() is an optional method which some DBMSes implement
> but Derby doesn't. The method raises a "Feature
Attendees: Michael Bouschen, Tilmann Zäschke, Tobias Bouschen, Craig Russell
Next meeting: Tuesday March 5 1100 PST 2000 CET
Agenda:
1. JIRA JDO-838 "Clarify doc for query cancel()/cancelAll()"
https://issues.apache.org/jira/browse/JDO-838
New PR #92 "Clarify javadoc
Attendees: Michael Bouschen, Tilmann Zäschke, Tobias Bouschen, Craig Russell
Next meeting: Tuesday February 27 1100 PST 2000 CET
Agenda:
1. New JIRA JDO-839 "Lock at XML parser factory settings"
https://issues.apache.org/jira/browse/JDO-839
<https://issues.apache.org/jira/browse
Attendees: Tilmann Zäschke, Tobias Bouschen, Michael Bouschen, Craig Russell
Next meeting: Tuesday February 20 1100 PST 2000 CET
Agenda:
1. GitHub security alert digest
Notifications will be sent based on settings.
-- derby
We would have to update our JDK dependency in order to handle
Attendees: Michael Bouschen, Tilmann Zäschke, Tobias Bouschen, Craig Russell
Next meeting: Tuesday February 13 1100 PST 2000 CET
Agenda:
1. New JIRA JDO-835 "TCK: Check ResultClassRequirementsMap when running
multithreaded" https://issues.apache.org/jira/browse/JDO-835
May be a D
Attendees: Michael Bouschen, Tilmann Zäschke, Craig Russell
Next meeting: Tuesday January 23 1100 PST 2000 CET
1. JIRA JDO-831: "tck: improve tck tests for performance"
https://issues.apache.org/jira/browse/JDO-831
Some TCK tests needed updated due to the PCPoint equals implementat
Attendees: Michael Bouschen, Tilmann Zäschke, Tobias Bouschen, Craig Russell
Next meeting: January 16 1100 PST 2000 CET
Agenda:
1. JIRA JDO-831: "tck: improve tck tests for performance"
https://issues.apache.org/jira/browse/JDO-831
Running tests for query-orig.conf with datasto
Hi Bryan,
Happy New Year. Here's some info from JDO:
Items for January board meeting:
The JDO project has a number of code improvements currently active. We are
investigating use of automated release artifact signing to streamline release
preparation. We have updated our automatic CI build to
Attendees: Michael Bouschen, Tobias Bouschen, Craig Russell
Next meeting: Tuesday January 9 1100 PST 2000 CET
Agenda:
Items for January board meeting:
The JDO project has a number of code improvements currently active. We are
investigating use of automated release artifact signing
Attendees: Michael Bouschen, Tilmann Zäschke, Tobias Bouschen, Craig Russell
Next meeting: Tuesday January 2 1100 PST 2000 CET
Agenda:
1. JIRA JDO-831: "tck: improve tck tests for performance"
https://issues.apache.org/jira/browse/JDO-831
Separation of sample queries has b
Attendees: Michael Bouschen, Tilmann Zäschke, Craig Russell
Next meeting: Tuesday December 19 1100 PST 2000 CET
Agenda:
1. JIRA JDO-831: "tck: improve tck tests for performance"
https://issues.apache.org/jira/browse/JDO-831
Work is under way. First issue is initialization of method
Attendees: Michael Bouschen, Tilmann Zäschke, Tobias Bouschen, Craig Russell
Next meeting: Tuesday December 12 1100 PST 2000 CET
Agenda:
1. JIRA JDO-831: "tck: improve tck tests for performance"
https://issues.apache.org/jira/browse/JDO-831
First steps: see which tests are read-
Attendees: Michael Bouschen, Tilmann Zäschke, Craig Russell
Next meeting: Tuesday December 5 1100 PST 2000 CET
Agenda:
1. JIRA JDO-834 "Consider moving files instead of copying"
https://issues.apache.org/jira/browse/JDO-834
Anything left?
Ok to resolve. Close when we ship.
2. JDO
Attendees: Michael Bouschen, Tilmann Zäschke, Tobias Bouschen, Craig Russell
Next meeting: Tuesday November 28 1100 PST 2000 CET
Agenda:
1. New PR #86 "Export TCK logs in GitHub Action"
https://github.com/apache/db-jdo/pull/86
Logs are uploaded with an expiration date + 2 we
Attendees: Michael Bouschen, Tilmann Zäschke, Tobias Bouschen, Craig Russell
Next meeting: Tuesday November 21 1100 PST 2000 CET
Agenda:
1. JDO-830: "tck: Migrate JUnit tests to version 5"
https://issues.apache.org/jira/browse/JDO-830
PR #85 https://github.com/apache/db-jdo/pul
Attendees: Michael Bouschen, Tilmann Zäschke, Tobias Bouschen, Craig Russell
Next meeting: Tuesday November 14 1100 PST 2000 CET
Agenda:
1. JDO-830: "tck: Migrate JUnit tests to version 5"
https://issues.apache.org/jira/browse/JDO-830
New PR #85 https://github.com/apache/db-j
Attendees: Michael Bouschen, Tilmann Zäschke, Craig Russell
Next meeting: Tuesday November 7 1100 PST 2000 CET
Agenda:
1. JDO-830: "tck: Migrate JUnit tests to version 5"
https://issues.apache.org/jira/browse/JDO-830
Currently using JUnit 5.9.3. But it no longer works s
Attendees: Michael Bouschen, Tilmann Zäschke, Craig Russell
Next meeting: Tuesday October 31 1200 PDT 2000 CET
Agenda:
1. New PR #84 "JDO-822 - Add JDK 21 to matrix build"
https://github.com/apache/db-jdo/pull/84
The TCK still builds to produce JDK 8. Andy says that DataNucleus is
Attendees: Michael Bouschen, Tobias Bouschen, Craig Russell
Next meeting: Thursday October 26 1100 PDT 2000 CET
Agenda:
1. JDO-830: "tck: Migrate JUnit tests to version 5 "
https://issues.apache.org/jira/browse/JDO-830
The current way to get the output is way too complicate
Attendees: Michael Bouschen, Tobias Bouschen, Craig Russell
Next meeting: Wednesday October 18 1200 PDT 2100 CET
1. JDO-830: "tck: Migrate JUnit tests to version 5 "
https://issues.apache.org/jira/browse/JDO-830
JUnit 5 has a few modules (not Java Modules) divided into parts. Wh
Hi Bryan,
Here's a tad more detail on some of the topics.
JDO currently supports JDK 8, 11, and 17. We have tested JDK 20 in a branch and
it looks good. Now that JDK 21 is GA, we will start CI testing using JDK 21 and
look at testing with target JDK 11, 17, and 21 instead of target JDK 8.
As
Attendees: Michael Bouschen, Tilmann Zäschke, Craig Russell
Next meeting: Thursday October 12 11:00 PDT 20:00 CET
Agenda:
1. Updates for our October report to the board
Items of note:
JDK21 is now an official release Generally Available as of September 19.
Tobias was elected to DB PMC.
JDO
Attendees: Michael Bouschen, Tilmann Zäschke, Craig Russell
Next meeting: Thursday October 5 1100 PDT 2000 CET
Agenda:
1. DOAP for JDO
The only possible issue is the name of the listing db-_JDO. Volunteer to "fix"
this? If not, drop from future agenda.
2. JIRA JDO-833 "Use au
Attendees: Michael Bouschen, Tilmann Zäschke, Tobias Bouschen, Craig Russell
Next meeting: Thursday September 21 11:00 PDT 20:00 CET
Agenda:
1. DOAP for JDO
https://projects.apache.org/doapfaq.html
The DOAP file was created from the template:
https://projects.apache.org/create.html
The DOAP
/develop
Seems to be the most common.
Please confirm that is what you recommend.
Thanks,
Craig
> On Sep 6, 2023, at 15:37, sebb wrote:
>
> On Wed, 6 Sept 2023 at 22:03, Craig Russell wrote:
>>
>> Hi Sebb,
>>
>> I've created a DOAP for the JDO project bu
Attendees: Michael Bouschen, Tilmann Zäschke, Tobias Bouschen, Craig Russell
Next meeting: Thursday Sept 14 1100 PDT 2000 CET
Agenda:
1. No Description Of A Project for JDO
Craig is working on it. The authoritative file will go into the db-jdo-site
repo.
2. JIRA JDO-833 "Use automated re
Hi Sebb,
I've created a DOAP for the JDO project but I'm having some trouble putting it
into the proper place. My svn is a bit rusty and I'm not even sure I'm trying
to put it where it belongs.
Could you help? I think it's ready to go into
Attendees: Tilmann Zäschke, Tobias Bouschen, Michael Bouschen, Craig Russell
Next meeting: Thursday September 7 1100 PDT 2000 CET
Agenda:
1. New DB PMC member: Tobias Bouschen
Congratulations Tobias!
2. No DOAP for JDO
This will need an update to the DOAP for DB to include JDO, Derby
Please join me in welcoming Tobias Bouschen as the latest member of the DB PMC.
Tobias has been contributing to JDO, writing pull requests, helping streamline
the build process and providing valuable insight into project strategy
especially with regard to JDK support.
He has been a committer
Attendees: Tobias Bouschen, Michael Bouschen, Tilmann Zäschke, Craig Russell
Next meeting: Thursday August 31 1100 PDT 2000 CET
Agenda:
1. Signing releases using automated release infra is a possibility for us to
use for the next release.
Looks like we should investigate for the next release
Attendees: Michael Bouschen, Tilmann Zäschke, Craig Russell
Next meeting: Thursday August 24 1100 PDT 2000 CET
Agenda:
1. Signing releases using automated release infra is a possibility for us to
use for the next release.
2. JDO-830: "tck: Migrate JUnit tests to version 5&qu
Hi,
We will have our regular meeting Thursday August 10 1100 PDT 2000 CET to
discuss JDO TCK issues and status.
We use the following dial-in for audio and video:
https://us02web.zoom.us/j/87074698575?pwd=bmZXeVV3dVowRHFDWk9KWFdVWjc3dz09
Agenda:
1. Signing releases using automated release
Attendees: Tobias Bouschen, Tilmann Zäschke, Craig Russell
Next meeting: Thursday August 10 1100 PDT 2000 CET
Agenda:
1. Any way to reduce the number of messages sent to the dev list for changes in
PRs?
See email discussion with cdutz
Done. If any changes are still needed, we can discuss.
2
Attendees: Tilmann Zäschke, Tobias Bouschen, Craig Russell
Next meeting: Thursday August 3 1100 PDT 2000 CET
Agenda:
1. Any way to reduce the number of messages sent to the dev list for changes in
PRs?
See email discussion with cdutz
2. Signing releases using automated release infra
Defer
Hi,
We will have our regular meeting Thursday August 3 1100 PDT 2000 CET to discuss
JDO TCK issues and status.
We use the following dial-in for audio and video:
https://us02web.zoom.us/j/87074698575?pwd=bmZXeVV3dVowRHFDWk9KWFdVWjc3dz09
Agenda:
1. Any way to reduce the number of messages sent
Hi,
We will have our regular meeting Thursday July 27 11:00 Pacific Daylight Time
(PDT) 20:00 Central European Summer Time (CET) to discuss JDO TCK issues and
status.
We use the following dial-in for audio and video:
https://us02web.zoom.us/j/87074698575?pwd=bmZXeVV3dVowRHFDWk9KWFdVWjc3dz09
Attendees:
Next meeting: Thursday July 27 1100 PDT 2000 CET
Agenda:
1. Any way to reduce the number of messages sent to the dev list for changes in
PRs?
See email discussion with cdutz. We may be able to thread more results. Need to
look into removing the commit id from the subject. The list
Hi,
This is something worth discussing. It has the potential to significantly
reduce the release manager's effort.
I'd guess that setting this up (once) is about the same complexity as
performing a release (each time).
Any interest?
Craig
> Begin forwarded message:
>
> From: Volkan Yazıcı
Hi Christofer,
We at the JDO project are concerned about the number of non-threaded messages
in our jdo-commits list. We reconfigured our notifications in our asf.yaml but
still get lots of un-threaded messages.
Could you spare 5 minutes and tell us what you think of our configuration?
Attendees: Michael Bouschen, Tilmann Zäschke, Tobias Bouschen, Craig Russell
Next meeting: July 20 11:00 PDT 20:00 CET
Agenda:
1. Any way to reduce the number of messages sent to the dev list for changes in
PRs?
AI Craig ask cdutz to look at our mail lists
2. JIRA JDO-827 "Conside
There are over half a dozen messages regarding JDO-827/PR#81.
Is there a problem with the asf.yaml configuration that prevents these from
being threaded?
I know we updated asf.yaml recently but somehow this does not meet my
expectations.
Thanks,
Craig
> Begin forwarded message:
>
> From:
Attendees: Tilmann Zäschke, Michael Bouschen, Tobias Bouschen, Craig Russell
Next meeting: Thursday July 13 11:00 PDT 20:00 CET
Agenda:
1. JIRA JDO-827 "Consider (re-)moving JNDI support"
https://issues.apache.org/jira/browse/JDO-827
PR # 81 "JDO-827 Simplify JNDI " https
Hi Bryan,
Thanks for taking care of this.
Status of JDO is ongoing, low activity.
No new releases since the last report.
No changes to roster.
The JDO project is continuing to work on improving support for current and
future JDKs. Currently supporting JDK 7, 11, and 17. Looking to JDK 21 for
Attendees: Michael Bouschen, Tilmann Zäschke, Tobias Bouschen, Craig Russell
Next meeting: Thursday July 6 11:00 PDT 20:00 CET
Agenda:
1. JDO-829: "api: Migrate JUnit tests to version 5"
https://issues.apache.org/jira/browse/JDO-829
New PR #80 https://github.com/apache/db-jdo/pul
I may have a conflict on Thursday June 29 at 1100/2000.
Can we reschedule the call for one hour later? Thursday June 29 1200 PDT 2100
CET.
Thanks,
Craig
Craig L Russell
c...@apache.org
Attendees: Michael Bouschen, Tilmann Zäschke, Tobias Bouschen, Craig Russell
Next meeting: Thursday June 29 1100 PDT 2000 CET
Agenda:
1. New JUnit JIRAs
JDO-829: "api: Migrate JUnit tests to version 5"
https://issues.apache.org/jira/browse/JDO-829
Some test classes that inherit
Attendees: Michael Bouschen, Tilmann Zäschke, Tobias Bouschen, Craig Russell
Next meeting: Thursday June 15 1100 PDT 2000 CET
Agenda:
1. New JIRA JDO-828 "Set up automated mail subjects for GitHub action
responses" https://issues.apache.org/jira/browse/JDO-828
New PR #78 &quo
Attendees: Michael Bouschen, Tilmann Zäschke, Craig Russell
Next meeting: Thursday June 8 1100 PDT 2000 CET
Agenda:
1. New JIRA JDO-827 "Consider (re-)moving JNDI support"
https://issues.apache.org/jira/browse/JDO-827
2. sonarcloud issues
JIRA JDO-819 "Code quality a
Attendees: Michael Bouschen, Tobias Bouschen, Craig Russell
Next meeting: Thursday June 1 1100 PDT 2000 CET
Agenda:
1. Github settings in .asf.yaml (see email from Craig)
2. Mailing list configurations for discussion (see email from Craig)
We should try out these configuration settings.
AI
weaking it if we have issues. I have
noticed that the GH notices that we get are not threaded to make it easy to
follow.
So anything could be better. Feel free to make a PR or just push to main and
see what happens.
Best,
Craig
>
> Best,
> Til
>
> On 18/05/2023 02:37,
Take a look at this:
https://community.apache.org/contributors/mailing-lists
It may make sense for us to re-examine our mail lists, notifications, etc.
WDYT?
Craig
Craig L Russell
c...@apache.org
What do you think about these settings? Other projects have used them to
simplify the stream of messages on dev related to PRs, comments, etc.
These go in the .asf.yaml file:
# Attempt to make the auto-generated github emails more easily readable in
email clients.
custom_subjects:
Attendees: Michael Bouschen, Tilmann Zäschke, Tobias Bouschen, Craig Russell
Next meeting: Thursday May 18 1100 PST 2000 CET
Agenda:
1. sonarcloud issues
JIRA JDO-819 "Code quality analysis"
https://issues.apache.org/jira/browse/JDO-819
JIRA JDO-823 "Fix sonarcloud issues of t
Attendees: Michael Bouschen, Tilmann Zäschke, Craig Russell
Next meeting: Thursday May 11 1100 PDT 2000 CET
Agenda:
1. sonarcloud issues
JIRA JDO-819 "Code quality analysis"
https://issues.apache.org/jira/browse/JDO-819
JIRA JDO-823 "Fix sonarcloud issues of type Code
Attendees: Michael Bouschen, Tilmann Zäschke, Craig Russell
Next meeting: Wednesday May 3 1200 PDT 2100 CET
Agenda:
1. sonarcloud issues
JIRA JDO-819 "Code quality analysis"
https://issues.apache.org/jira/browse/JDO-819
JIRA JDO-823 "Fix sonarcloud issues of type Code
Attendees: Michael Bouschen, Tilmann Zäschke, Tobias Bouschen, Craig Russell
Next meeting: Wednesday April 26 1200 PDT 2100 CEST
Agenda:
1. sonarcloud issues
JIRA JDO-819 "Code quality analysis"
https://issues.apache.org/jira/browse/JDO-819
JIRA JDO-823 "Fix sonarcloud issu
Hi Bryan,
We discussed the quarterly report yesterday.
Warm regards,
Craig
> Begin forwarded message:
>
> From: Craig Russell
> Subject: Minutes: JDO TCK Conference Call Thursday April 6 1100 PDT 2000 CEST
> Date: April 6, 2023 at 11:57:19 PDT
> To: JDO Project
>
Attendees: Michael Bouschen, Tilmann Zäschke, Tobias Bouschen, Craig Russell
Next meeting: Thursday April 20 1100 PDT 2000 CET
Agenda:
1. Updates for our quarterly report to the board?
JDO project is working on sonar cloud reports that will improve the quality of
the code. We have already
he new javadoc is not
>>> formatted correctly. The issue is probably that the javadoc has a linebreak
>>> even though the character limit is not reached on the first line. If you
>>> want the second line to actually be printed as a second line in the
>>> java
s, the formatter should do this for you.
>
> Best regards,
> Tobias
>
> On 03/04/2023 22:25, Craig Russell wrote:
>> So the code format check failed. I cannot see anything wrong with the
>> changes I made.
>>
>> https://github.com/apache/db-jdo/acti
So the code format check failed. I cannot see anything wrong with the changes I
made.
https://github.com/apache/db-jdo/actions/runs/4591159720/jobs/8107138939?pr=73
Error: To fix formatting errors, run "mvn
com.spotify.fmt:fmt-maven-plugin:format"
8275
Attendees: Michael Bouschen, Tilmann Zäschke, Tobias Bouschen, Craig Russell
Next meeting: Thursday April 6 1100 PDT 2000 CET
Agenda:
1. JIRA JDO-819 "Code quality analysis"
https://issues.apache.org/jira/browse/JDO-819
JIRA JDO-823 "Fix sonarcloud issues of type Code
Two methods with different names but identical implementation:
public static void string2Set(String names, Collection list)
public static void string2List(String names, List list)
The behavior only depends on the actual type of the "list" parameter.
Proposal: change implementations of both
Attendees: Michael Bouschen, Tilmann Zäschke, Tobias Bouschen, Craig Russell
Next meeting: Thursday March 30 1100 PDT 2000 CET
Agenda:
1. JIRA JDO-819 "Code quality analysis"
https://issues.apache.org/jira/browse/JDO-819
JIRA JDO-823 "Fix sonarcloud issues of type Code
Attendees: Michael Bouschen, Tilmann Zäschke, Tobias Bouschen, Craig Russell
Next meeting: Thursday March 23 1200 PDT 2000 CET
Agenda:
1. JIRA JDO-819 "Code quality analysis"
https://issues.apache.org/jira/browse/JDO-819
JIRA JDO-823 "Fix sonarcloud issues of type Code
Attendees: Michael Bouschen, Tilmann Zäschke, Tobias Bouschen, Craig Russell
Next meeting: Thursday March 16 1200 PDT 2000 CET
Agenda:
1. New PR #69 "Removed nested try-catch"
https://github.com/apache/db-jdo/pull/69
A couple of comments but otherwise good to go.
2. new PR #7
well, dunno how that happened. the jdo meeting is in progress with just me
> On Mar 1, 2023, at 12:07, Tilmann Zäschke wrote:
>
> I am getting "the host has another meeting in progress" ...?
>
>
> On 01/03/2023 18:57, Tobias Bouschen wrote:
>> Hi all,
>>
>> sorry for the short notice again,
Attendees: Michael Bouschen, Tilmann Zäschke, Craig Russell
Next meeting: Wednesday 1200 PST 2100 CET
Agenda:
1. JIRA JDO-819 "Code quality analysis"
https://issues.apache.org/jira/browse/JDO-819
JIRA JDO-823 "Fix sonarcloud issues of type Code Smells"
https://issues.ap
Attendees: Michael Bouschen, Tilmann Zäschke, Tobias Bouschen, Craig Russell
Next meeting: Thursday February 23 1100 PST 2000 CET
Agenda:
1. Upcoming global changes to default GitHub Actions behavior for outside
collaborators
Because of possible security issues, ASF's use of GitHub Actions
Attendees: Michael Bouschen, Tobias Bouschen, Tilmann Zäschke, Craig Russell
Next meeting: Thursday February 16 1100 PDT 2000 CET
Agenda:
1. JIRA JDO-819 "Code quality analysis"
https://issues.apache.org/jira/browse/JDO-819
JIRA JDO-823 "Fix sonarcloud issues of type Code
Attendees: Michael Bouschen, Tobias Bouschen, Craig Russell
Next meeting: Thursday February 9 1200 PST 2100 CET
Agenda:
1. JIRA JDO-819 "Code quality analysis"
https://issues.apache.org/jira/browse/JDO-819
JIRA JDO-823 "Fix sonarcloud issues of type Code Smells"
https
Attendees: Michael Bouschen, Tilmann Zäschke, Tobias Bouschen, Craig Russell
Next meeting:
Agenda:
1. Copyright notice is out of date
There are two NOTICE files. Only one is really needed. The NOTICE in the tck
package is only needed if there is an independent distribution of the tck.
[Til
I believe that the NOTICE.txt in the tck is only there if the tck is
distributed independently. Otherwise, it should be removed.
> On Dec 7, 2022, at 20:47, Craig Russell wrote:
>
> The copyright notice is in two places:
>
>
> ./NOTICE:Copyright 2005-2022 The Apache S
Attendees: Michael Bouschen, Tilmann Zäschke, Tobias Bouschen, Craig Russell
Next meeting: Thursday January 26 1100 PST 2000 CET
Agenda:
1. JIRA JDO-819 "Code quality analysis"
https://issues.apache.org/jira/browse/JDO-819
JIRA JDO-823 "Fix sonarcloud issues of type Code
Attendees: Michael Bouschen, Tilmann Zäschke, Tobias Bouschen, Craig Russell
Next meeting: Wednesday January 18 1200 PST 2100 CET
Agenda:
1. JIRA JDO-819 "Code quality analysis"
https://issues.apache.org/jira/browse/JDO-819
JIRA JDO-823 "Fix sonarcloud issues of type Code
Hi Bryan,
Thanks for the reminder.
No JDO releases since 3.2.1 last quarter.
The JDO project is working on improving code quality via feedback solicited
from a code analysis tool called SonarCloud. SonarCloud itself is not open
source but is free to analyze open source projects. A number of
Attendees: Michael Bouschen, Tobias Bouschen, Tilmann Zäschke, Craig Russell
Next meeting: Thursday January 12 1100 PST 2000 CET
Agenda:
1. JIRA JDO-819 "Code quality analysis"
https://issues.apache.org/jira/browse/JDO-819
JIRA JDO-823 "Fix sonarcloud issues of type Code
Attendees: Michael Bouschen, Tobias Bouschen, Craig Russell
Next meeting: Thursday January 5 1100 PST 2000 CET
Agenda:
1. Derby vulnerability
See https://issues.apache.org/jira/browse/DERBY-7147
This is a vulnerably without a known exploit. The only use of Derby in JDO is
in the TCK tests
;
> In my opinion this would be preferred over '// NOSONAR' because using
> the web UI avoids cluttering the code with '// NOSONAR' statements.
>
> Maybe something to discuss in the next meeting.
>
> Best,
>
> Til
>
>
> On 16.12.22 16:49, Craig Russell wrote:
>>
Attendees: Michael Bouschen, Tilmann Zäschke, Tobias Bouschen, Craig Russell
Next meeting: Thursday December 29 1100 PST 2000 CET
Agenda:
1. Derby vulnerability
See https://issues.apache.org/jira/browse/DERBY-7147
<https://issues.apache.org/jira/browse/DERBY-7147>
No rush to upgrade
The copyright notice is in two places:
./NOTICE:Copyright 2005-2022 The Apache Software Foundation
./tck/NOTICE.txt:Copyright 2005-2006 The Apache Software Foundation
The NOTICE.txt in tck might be historic. Do we need it?
Craig
> On Dec 6, 2022, at 17:07, Craig Russell wrote:
>
>
I noticed this while reviewing the http https patch (hat tip Til). The
copyright NOTICE is out of date.
I'll write a patch which includes both the copyright notice and updated
instructions for release.
Craig
Craig L Russell
c...@apache.org
Attendees: Michael Bouschen, Tilmann Zäschke, Tobias Bouschen, Craig Russell
Next meeting: Thursday December 8 1100 PST 2000 CET
Agenda:
1. JIRA JDO-819 "Code quality analysis"
https://issues.apache.org/jira/browse/JDO-819
Three admins are now authorized. The main issue looks like
Attendees: Michael Bouschen, Tilmann Zäschke, Tobias Bouschen, Craig Russell
Next meeting: Thursday December 1 1100 PST 2000 CET
Agenda:
1. JIRA JDO-819 "Code quality analysis"
https://issues.apache.org/jira/browse/JDO-819
<https://issues.apache.org/jira/browse/JDO-819&g
Attendees: Michael Bouschen, Tilmann Zäschke, Tobias Bouschen, Craig Russell
Next meeting: Wednesday 1200 noon PST 2100 CET
Agenda:
1. JIRA JDO-819 "Code quality analysis"
https://issues.apache.org/jira/browse/JDO-819
<https://issues.apache.org/jira/browse/JDO-819>
Tilmann
1 - 100 of 1711 matches
Mail list logo
