am not completely certain.
Best regards,
Tobias Bouschen
Hi all,
after a long discussion with the INFRA team, it seems like we have
gotten to a point were the problem has almost been resolved.
The issue seemed to be caused by the backend not being set up to handle
our specific use case. It should work in the future, but to avoid
putting
Hi all,
I have created the JIRA ticket:
https://issues.apache.org/jira/browse/INFRA-21326
If you see any issues with the entry, I can still adjust it.
Best regards,
Tobias
. [That's why we were forced to change to
> the new .asf.yaml process.]
>
> I'm a bit surprised that the db.apache.org CMS setup is still alive. Perhaps
> other sub-projects are still using the old system.
>
> Anyway, let's see what Humbedoo has to say.
>
> Regards,
>
, Tobias Bouschen wrote:
Hi all,
Just as a quick heads up: The new hosting setup (publishing it to the
'content' directory on the 'publish' branch) works. But, as I suspected,
it also requires URL forwarding to work as intended. The same
configuration that had previously been used on the master could
Hi all,
Just as a quick heads up: The new hosting setup (publishing it to the
'content' directory on the 'publish' branch) works. But, as I suspected,
it also requires URL forwarding to work as intended. The same
configuration that had previously been used on the master could be
reused, only
I don't think there is any way of making everybody happy here. No matter
what we do, somebody will most likely complain. From reading the
discussions you linked to, Craig, the arguments seem to go around in
circles. Either it matters or doesn't matter what the etymological
origin/usage/context
The website does not update for me as well.
The changes were successfully deployed to the 'publish' branch, so my
guess is that the issue again lies with the hosting backend. I am going
to post another comment to the INFRA jira.
On 05/02/2021 19:31, Craig Russell wrote:
> I'm still not seeing
Hi all,
I encountered some more issues regarding branch protection. Even though
I managed to resolve the main issue (regarding required checks and
required linear history), the current setup still has some drawbacks
that I was not aware of before:
Due to the restriction of requiring
cases to
avoid the failure.
On 2/5/21 8:00 PM, Tobias Bouschen wrote:
I forgot to hit 'reply list' for my last mail. Sorry about that.
> Same here.
> I reran the job, it is not obvious to me why it fails:
>
https://github.com/apache/db-jdo-site/runs/1841121479?check_suite_focus=true
if I can
adjust the behavior to 'fail' gracefully if there is nothing to commit.
On 2/5/21 7:51 PM, Tobias Bouschen wrote:
I am pretty sure that this is unrelated. The 'red x' is solely related
to GitHub jobs, specifically the deployment of the GitHub pages in this
case. If you hover over t
for similar issues when we push changes to the master
the next time, just to make sure that the deployment worked out.
Best regards,
Tobias
On 05/02/2021 20:06, Tobias Bouschen wrote:
>> Probably because git gives the return code 1 if there is
>> nothing to push.
>
> To be more pr
The commit notification have gone to the 'jdo-comm...@db.apache.org'
mailing list, as intended.
With this, I would see the topic of GitBox notification settings as
resolved as they are also covered by the asf.yaml settings.
Best regards,
Tobias
On 2/13/21 2:10 PM, Tobias Bouschen wrote:
Hi
Hi all,
I am wondering who initially designed/created the JDO logo and whether
there are higher-resolution versions of it around. Ideally, it would be
nice to have a scalable vector graphic (svg) version of the logo.
With the number of irregular rings as part of the logo, automatically
Hi all,
during the last conference call, I proposed to migrate the existing
specification from OpenOffice to LaTeX. I created the following Jira for
it: https://issues.apache.org/jira/browse/JDO-798
I mentioned some advantages LaTeX would offer in my opinion, so have a
look if you are
Works for me, but I might be a bit late depending on how long work runs.
On 8 September 2021 19:37:29 CEST, Craig Russell wrote:
>Hi,
>
>I have a conflict at 11:00. Could we meet at 10:00 instead?
>
>Thanks
>Craig
>
>Craig L Russell
>c...@apache.org
>
Hi all,
as discussed in the last conference call, I have split of the
specification from the db-jdo repository and moved it to the repo
clr-apache/jdo-specification
(https://github.com/clr-apache/jdo-specification). I force-pushed the
changes onto the main of the new repo (as it was
Branch: refs/heads/main
Home: https://github.com/clr-apache/jdo-specification
Commit: 82583f48849a71af5a645aa4a32b2878aab1215f
https://github.com/clr-apache/jdo-specification/commit/82583f48849a71af5a645aa4a32b2878aab1215f
Author: Michelle Caisse
Date: 2012-07-01 (Sun, 01 Jul
+1
On 27/01/2022 17:36, Tilmann Zäschke wrote:
Dear all,
I prepared the final release for JDO 3.2.
Please vote on the release. Voting will be open until Monday, January 31st.
You may download the JDO 3.2 release artifacts from the staging repository:
Hi all,
I won't be able to join the conference call today. But I will be back next week.
Best regards (and a happy new year),
Tobias
On 5 January 2022 21:26:54 CET, Michael Bouschen wrote:
>Hi,
>
>Happy New Year!
>
>We will have our regular meeting Thursday January 6 11 AM Pacific Standard
Hi all,
Unfortunately, I won't be able to make the conference call this week. I will
see you all next week.
Best regards,
Tobias
On 4 October 2023 20:55:50 CEST, Michael Bouschen wrote:
>Hi,
>
>We will have our regular meeting Thursday October 5 1100 PDT 2000 CEST to
>discuss JDO TCK issues
+1.
Files in release artifacts seem to be in order and TCK runs from src
release.
On 5/22/22 16:28, Tilmann Zäschke wrote:
Hi,
please vote on the JDO 3.2.1 release (based on RC2). Voting will be open
until Wednesday,
May 25th, 14:30 UTC.
You may download the JDO 3.2.1 release artifacts
I won't be able to make it to today's conference call. I will join
again next week.
Best regards,
Tobias
On 07/09/2022 21:44, Michael Bouschen wrote:
Hi,
We will have our regular meeting Thursday September 8 11:00 Pacific
Daylight Time (PDT) 20:00 Central European Summer Time (CEST) to
I can't make it to the call this week. I will join you again next week.
Beat regards,
Tobias
On 10 August 2022 20:27:58 CEST, Michael Bouschen wrote:
>Hi,
>
>We will have our regular meeting Thursday August 11 11:00 Pacific Daylight
>Time (PDT) 20:00 Central European Summer Time (CEST) to
Hi all,
I can't make it to today's phone conference. I will see you all next week.
Best regards,
Tobias
On 7 December 2022 21:08:54 CET, Michael Bouschen wrote:
>Hi,
>
>We will have our regular meeting Thursday December 8 11:00 Pacific Standard
>Time (PST) 20:00 Central European Time (CET) to
Hi all,
sorry for the short notice again, but I won't be able to attend today's
conference call. I will see you all next week.
Best regards,
Tobias
On 28/02/2023 20:58, Michael Bouschen wrote:
Hi,
We will have our regular meeting Wednesday March 1 12:00 Pacific
Standard Time (PST) 21:00
Hi all,
I won't be able to attend the meeting this week. I will join you again
next week.
Best regards,
Tobias
On 22/02/2023 21:01, Michael Bouschen wrote:
Hi,
We will have our regular meeting Thursday February 23 11:00 Pacific
Standard Time (PST) 20:00 Central European Time (CET) to
Hi Craig,
the instructions on how to run the format jobs are given in the readme:
https://github.com/apache/db-jdo#formatting-using-maven
GJF also formats javadoc. So my guess would be that the new javadoc is
not formatted correctly. The issue is probably that the javadoc has a
linebreak
t;Oracle Corporation" - "Java" /Library/Internet
>>> Plug-Ins/JavaAppletPlugin.plugin/Contents/Home
>>> 1.8.0_331 (x86_64) "Oracle Corporation" - "Java SE 8"
>>> /Library/Java/JavaVirtualMachines/jdk1.8.0_331.jd
Hello Tilman,
the conference call is indeed today at 21:00 CET. Then we will see you next
week.
Best regards,
Tobias
On 8 February 2023 12:59:42 CET, "Tilmann Zäschke" wrote:
>Hi Michael,
>
>in the minutes last week it said:
>
>Next meeting: Thursday February 9 1200 PST 2100 CET
>
>Is it Feb
Hi all,
I am sick and won't be joining the conference call tomorrow.
Best regards,
Tobias
On 02/05/2023 19:02, Michael Bouschen wrote:
Hi,
We will have our regular meeting Wednesday May 3 12:00 Pacific
Daylight Time (PDT) 21:00 Central European Summer Time (CET) to
discuss JDO TCK issues
Hi all,
I can't make it to the conference call today. See you next week.
Best regards,
Tobias
On 31/05/2023 21:01, Michael Bouschen wrote:
Hi,
We will have our regular meeting Thursday June 1 11:00 Pacific
Daylight Time (PDT) 20:00 Central European Summer Time (CET) to
discuss JDO TCK
Hi all,
I won't be attending today's conference call.
Best regards,
Tobias
On 03/08/2023 20:34, Craig Russell wrote:
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:
Hi all,
sorry, I won't be able to make the meeting today. See you all next week.
Best regards,
Tobias
On 15/01/2024 22:20, Michael Bouschen wrote:
Hi,
We will have our regular meeting Tuesday January 16 1100 PST 2000 CET
to discuss JDO TCK issues and status.
We use the following dial-in
Tobias Bouschen created JDO-788:
---
Summary: Decide what to do with GitHub pages setup
Key: JDO-788
URL: https://issues.apache.org/jira/browse/JDO-788
Project: JDO
Issue Type: Task
[
https://issues.apache.org/jira/browse/JDO-792?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tobias Bouschen resolved JDO-792.
-
Resolution: Fixed
> Create branch protection for master bra
[
https://issues.apache.org/jira/browse/JDO-792?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17308935#comment-17308935
]
Tobias Bouschen commented on JDO-792:
-
To allow for direct pushes to the master, we decided to also
Tobias Bouschen created JDO-792:
---
Summary: Create branch protection for master branch
Key: JDO-792
URL: https://issues.apache.org/jira/browse/JDO-792
Project: JDO
Issue Type: Task
Tobias Bouschen created JDO-791:
---
Summary: Introduce GitHub actions for the main JDO repository
Key: JDO-791
URL: https://issues.apache.org/jira/browse/JDO-791
Project: JDO
Issue Type: Task
[
https://issues.apache.org/jira/browse/JDO-791?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tobias Bouschen reassigned JDO-791:
---
Assignee: Tobias Bouschen
> Introduce GitHub actions for the main JDO reposit
[
https://issues.apache.org/jira/browse/JDO-792?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17302730#comment-17302730
]
Tobias Bouschen commented on JDO-792:
-
After discussing the topic, the decision was made to not include
[
https://issues.apache.org/jira/browse/JDO-791?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tobias Bouschen resolved JDO-791.
-
Fix Version/s: JDO 3.2
Resolution: Fixed
> Introduce GitHub actions for the main
Tobias Bouschen created JDO-793:
---
Summary: Decide whether to rename the 'master' branch to 'main'
Key: JDO-793
URL: https://issues.apache.org/jira/browse/JDO-793
Project: JDO
Issue Type: Task
[
https://issues.apache.org/jira/browse/JDO-793?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tobias Bouschen updated JDO-793:
Description:
There still is an ongoing discussion over the use of the word 'master' in the
context
[
https://issues.apache.org/jira/browse/JDO-788?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tobias Bouschen resolved JDO-788.
-
Resolution: Fixed
GitHub pages have been disabled for now. If we decide we want to use them again
[
https://issues.apache.org/jira/browse/JDO-795?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tobias Bouschen updated JDO-795:
Description:
* Added A.21 Changes for 3.1 and A.22 Changes for 3.2 to
AppF-RevisionHistory.odt (done
[
https://issues.apache.org/jira/browse/JDO-795?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tobias Bouschen updated JDO-795:
Description:
* Added A.21 Changes for 3.1 and A.22 Changes for 3.2 to
AppF-RevisionHistory.odt (done
[
https://issues.apache.org/jira/browse/JDO-795?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tobias Bouschen updated JDO-795:
Description:
* Added A.21 Changes for 3.1 and A.22 Changes for 3.2 to
AppF-RevisionHistory.odt (done
[
https://issues.apache.org/jira/browse/JDO-795?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tobias Bouschen updated JDO-795:
Description:
* Added A.21 Changes for 3.1 and A.22 Changes for 3.2 to
AppF-RevisionHistory.odt (done
[
https://issues.apache.org/jira/browse/JDO-795?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tobias Bouschen updated JDO-795:
Description:
* Added A.21 Changes for 3.1 and A.22 Changes for 3.2 to
AppF-RevisionHistory.odt (done
[
https://issues.apache.org/jira/browse/JDO-795?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tobias Bouschen updated JDO-795:
Description:
* Added A.21 Changes for 3.1 and A.22 Changes for 3.2 to
AppF-RevisionHistory.odt (done
[
https://issues.apache.org/jira/browse/JDO-798?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tobias Bouschen updated JDO-798:
Description:
As we were having many issues with the current specification written using
OpenOffice
[
https://issues.apache.org/jira/browse/JDO-795?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tobias Bouschen updated JDO-795:
Description:
* Added A.21 Changes for 3.1 and A.22 Changes for 3.2 to
AppF-RevisionHistory.odt (done
[
https://issues.apache.org/jira/browse/JDO-795?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tobias Bouschen updated JDO-795:
Description:
* Added A.21 Changes for 3.1 and A.22 Changes for 3.2 to
AppF-RevisionHistory.odt (done
[
https://issues.apache.org/jira/browse/JDO-798?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tobias Bouschen updated JDO-798:
Summary: Proposal – Migrate Specification to LaTeX (was: Proposa – Migrate
Specification to LaTeX
Tobias Bouschen created JDO-798:
---
Summary: Proposa – Migrate Specification to LaTeX
Key: JDO-798
URL: https://issues.apache.org/jira/browse/JDO-798
Project: JDO
Issue Type: Task
[
https://issues.apache.org/jira/browse/JDO-798?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tobias Bouschen updated JDO-798:
Description:
As we were having many issues with the current specification written using
OpenOffice
[
https://issues.apache.org/jira/browse/JDO-798?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17410823#comment-17410823
]
Tobias Bouschen commented on JDO-798:
-
I know what you mean. Setting it up for windows is somewhat
[
https://issues.apache.org/jira/browse/JDO-795?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tobias Bouschen updated JDO-795:
Description:
* Added A.21 Changes for 3.1 and A.22 Changes for 3.2 to
AppF-RevisionHistory.odt (done
[
https://issues.apache.org/jira/browse/JDO-795?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tobias Bouschen updated JDO-795:
Description:
* Added A.21 Changes for 3.1 and A.22 Changes for 3.2 to
AppF-RevisionHistory.odt (done
[
https://issues.apache.org/jira/browse/JDO-793?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tobias Bouschen updated JDO-793:
Description:
There still is an ongoing discussion over the use of the word 'master' in the
context
[
https://issues.apache.org/jira/browse/JDO-822?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tobias Bouschen updated JDO-822:
Fix Version/s: JDO 3.2.2
(was: JDO 3.3)
> Verify compatibility with JDK
[
https://issues.apache.org/jira/browse/JDO-822?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tobias Bouschen updated JDO-822:
Fix Version/s: JDO 3.3
> Verify compatibility with JDK
[
https://issues.apache.org/jira/browse/JDO-822?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tobias Bouschen resolved JDO-822.
-
Resolution: Fixed
> Verify compatibility with JDK
Tobias Bouschen created JDO-812:
---
Summary: Move to JDK 11 as the lowest supported version
Key: JDO-812
URL: https://issues.apache.org/jira/browse/JDO-812
Project: JDO
Issue Type: Task
Tobias Bouschen created JDO-818:
---
Summary: Use Google Java Style as the code format conventions for
the JDO project
Key: JDO-818
URL: https://issues.apache.org/jira/browse/JDO-818
Project: JDO
[
https://issues.apache.org/jira/browse/JDO-818?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tobias Bouschen resolved JDO-818.
-
Resolution: Fixed
> Use Google Java Style as the code format conventions for the JDO proj
Tobias Bouschen created JDO-828:
---
Summary: Set up automated mail subjects for GitHub action responses
Key: JDO-828
URL: https://issues.apache.org/jira/browse/JDO-828
Project: JDO
Issue Type
[
https://issues.apache.org/jira/browse/JDO-822?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17729106#comment-17729106
]
Tobias Bouschen commented on JDO-822:
-
I adjusted the matrix build on my fork to run with JDK 20
[
https://issues.apache.org/jira/browse/JDO-828?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tobias Bouschen closed JDO-828.
---
Resolution: Fixed
> Set up automated mail subjects for GitHub action respon
[
https://issues.apache.org/jira/browse/JDO-828?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tobias Bouschen resolved JDO-828.
-
Resolution: Fixed
> Set up automated mail subjects for GitHub action respon
[
https://issues.apache.org/jira/browse/JDO-828?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tobias Bouschen reopened JDO-828:
-
> Set up automated mail subjects for GitHub action respon
72 matches
Mail list logo
