Hi Andy,
Thanks for helping us get the best possible list of DataNucleus dependencies
for the release.
Thanks for clarifying the purpose of the api-jdo jar. I had a misunderstanding
of what the datanucleus-api-jdo was, having never actually looked at it. I
should have asked the question
Attendees: Michael Bouschen, Tilmann Zäschke, Tobias Bouschen, Craig Russell
Next meeting: Thursday Dec 2 10:30 PST 19:30 CET
Agenda:
1. JDO 3.2 release RC4
The release includes DataNucleus reference in the pom: core 5.2.7; rdbms 5.2.7;
api-jdo 5.2.7; jdo-query 5.0.9; api-jpa 5.2.6
o be resolved as you suggested.
> What do you think?
I think it's fine to make the RC4 with the redundant artifacts. We can and
should remove the .md5 and .sha1 (and .sha512.sha1) files when we post them to
the dist/release area.
Again, sorry for missing the meeting.
Craig
>
> T
Sorry gang,
I had the time wrong on my personal calendar so I missed the meeting.
I noticed the JIRA for Nexus.
Once the issue has been fixed and the RC3 closed, I have all I need to file the
Maintenance Review with the JCP.
Craig
> On Nov 17, 2021, at 12:11 PM, Michael Bouschen wrote:
>
Hi Tilmann,
I would follow the Nexus rules and include the .md5 and .sha1 in order to stage
the release.
We can always remove these obsolete checksum files when we publish the release
on dist/db/jdo. After the build/vote process is done.
Separately, the bui...@apache.org might be the place to
Attendees: Michael Bouschen, Tilmann Zäschke, Tobias Bouschen, Craig Russell
Next meeting: Thursday November 18 10:15 PST 19:15 CET
Agenda:
1. Please test staged JDO 3.2 release (RC2)
https://repository.apache.org/content/repositories/orgapachejdo-1002
There is no .sha512 in the javax/jdo
Attendees: Michael Bouschen, Tilmann Zäschke, Tobias Bouschen, Craig Russell
Next meeting: Thursday November 11, 11:00 PST, 20:00 CET
Agenda:
1. Please test staged JDO 3.2 release
https://repository.apache.org/content/repositories/orgapachejdo-1001/
This contains two sets of release artifacts
Hi,
I'm afraid I got this wrong. Let's discuss.
The purpose of -rc1 is to allow for multiple iterations of a release, so if
changes are made, people know what it is they are voting for. So the file name
should change if a new release candidate is made.
But once a successful vote is complete,
Attendees: Michael Bouschen, Tilmann Zäschke, Tobias Bouschen, Craig Russell
Next meeting: Friday November 5 12:00 noon Pacific 20:00 Central Europe
Agenda:
1. JDO-795 "Publishing the 3.2
specification"https://issues.apache.org/jira/projects/JDO/issues/JDO-795
2. JSR-243 Maintenance
In case you're in Berlin and want to stop by...
https://foss-backstage.de/news/foss-backstage-returns-new-person-venue
Craig L Russell
c...@apache.org
fixing errata in a specification is slightly
> different.
>
>
> These are described in more detail online:
> https://jcp.org/en/resources/guide-maint211
>
>
> Let me know if you have any questions about the maintenance process.
>
>
> Thank you,
>
>
> H
Attendees: Michael Bouschen, Tilmann Zäschke, Tobias Bouschen, Craig Russell
Next meeting: Friday October 29 11:30 Pacific, 20:30 CET
Agenda:
1. JDO-795 "Publishing the 3.2 specification"
https://issues.apache.org/jira/projects/JDO/issues/JDO-795
All chapters are now reviewed
Hi Bryan,
Good start. Here's the latest on what JDO has been up to:
The JDO team have been making changes suggested by the Apache
Diversity Conscious Language Checker, including changing the
name of the git branch from master to main, and resolving all issues in the
source code and web site.
Attendees: Michael Bouschen, Tobias Bouschen, Craig Russell
Next meeting: Thursday October 7 11:00 Pacific
Agenda:
1. JDO-795 "Publishing the 3.2
specification"https://issues.apache.org/jira/projects/JDO/issues/JDO-795
Issue with "Optimistic" index entries. Merge "
Hi,
As Maintenance Lead for JSR-243 I'd like to propose a Maintenance Release 4.
We have prepared:
The Specification in .odm and .pdf formats
The API in source (GitHub) and binary formats
The TCK in source (GitHub) and binary formats
The Change List in .odf format
Can you please give me
Attendees: Michael Bouschen, Tilmann Zäschke, Tobias Bouschen, Craig Russell
Next meeting: Thursday September 30 11:00 Pacific
Agenda:
1. JDO-795 "Publishing the 3.2 specification"
https://issues.apache.org/jira/projects/JDO/issues/JDO-795
Look at index entries for hollow, JD
Attendees: Michael Bouschen, Tilmann Zäschke, Tobias Bouschen, Craig Russell
Next meeting: Wednesday September 22 11:30 Pacific Daylight Time
Agenda:
1. Update from Andy: JIRA JDO-796 "Write TCK test case to test JTA assertions"
Thanks to Andy for the link to the DataNucleus
Attendees: Michael Bouschen, Tilmann Zäschke, Tobias Bouschen, Craig Russell
Next meeting: Thursday September 16 11:00 AM Pacific
Agenda:
1. New JIRA JDO-798 "Proposal – Migrate Specification to LaTeX"
https://issues.apache.org/jira/browse/JDO-798
Currently we do not foresee maj
Hi,
I have a conflict at 11:00. Could we meet at 10:00 instead?
Thanks
Craig
Craig L Russell
c...@apache.org
Attendees: Michael Bouschen, Tilmann Zäschke, Tobias Bouschen, Craig Russell
Next meeting: Thursday September 9 11:00 Pacific
Agenda:
1. JDO-795 "Publishing the 3.2 specification"
https://issues.apache.org/jira/projects/JDO/issues/JDO-795
While reviewing, look for index entries p
Attendees: Michael Bouschen, Tilmann Zäschke, Tobias Bouschen, Craig Russell
Next meeting: Thursday September 2 11:00 Pacific
Agenda:
1. New GitHub repository: https://github.com/clr-apache/jdo-specification
This repository was created to remove the specification from the Apache
repository
Before I forget it, the new repository is
https://github.com/clr-apache/jdo-specification
Any DB PMC member or JDO committer is welcome to join.
Craig
> On Aug 20, 2021, at 12:01 PM, Craig Russell wrote:
>
> Hi,
>
> I've created a GitHub repository for the purpose of remov
Hi Tilmann,
> On Aug 21, 2021, at 10:23 AM, Tilmann wrote:
>
> Hi,
>
> sorry but I have to ask again:
>
> - Assertions are created by setting the style of e.g. "A6.4.3-18[" and
> the following "]" to "Assertion", correct?
Yes, that is how I remember it working. It's only a comment so it has
Hi,
I've created a GitHub repository for the purpose of removing the JSR-243
specification from the Apache repository. Its license is not currently
compatible with the Apache license. If I am unable to get Oracle to relicense
the specification, we can continue to work on it outside Apache,
Attendees: Michael Bouschen, Tilmann Zäschke, Tobias Bouschen, Craig Russell
Next meeting: Thursday August 26 11:00 Pacific
Agenda:
1. JDO-795 "Publishing the 3.2 specification"
https://issues.apache.org/jira/projects/JDO/issues/JDO-795
AI everyone: generate the pdf: open the maste
Attendees: Michael Bouschen, Tilmann Zäschke, Tobias Bouschen, Craig Russell
Next meeting: Thursday August 19 11:00 Pacific
Agenda:
1. JDO-795 "Publishing the 3.2 specification"
<https://issues.apache.org/jira/projects/JDO/issues/JDO-795><https://issues.apache.org/jira/proj
Attendees: Michael Bouschen, Tobias Bouschen, Tilmann Zäschke, Craig Russell
Next meeting: Thursday August 5 11:00 Pacific
Agenda:
1. JDO-795 "Publishing the 3.2 specification"
<https://issues.apache.org/jira/projects/JDO/issues/JDO-795>
Update to the specification/OO
Attendees: Michael Bouschen, Tilmann Zäschke, Tobias Bouschen, Craig Russell
Next meeting: Thursday July 29 11:00 Pacific
Agenda:
1. Change the name of our main branch from "master" to "main" JDO-793
<https://issues.apache.org/jira/browse/JDO-793> Infra JIRA ticket
Hi Humbedooh,
Thanks for all your efforts on the CLC project, and for your help getting the
JDO part working as expected.
It all looks fine now.
Warm regards,
Craig
> On Jul 20, 2021, at 12:15 AM, Daniel Gruno wrote:
>
> On 19/07/2021 20.40, Craig Russell wrote:
>> Hi Humbedo
Hi Humbedooh,
Just one more thing. We have changed our main branch to "main" instead of
"master". Do you know when that change will be reflected in git and clc?
Thanks,
Craig
> On Jul 19, 2021, at 6:57 AM, Daniel Gruno wrote:
>
> On 19/07/2021 15.40, Craig R
Hi Humbedooh,
> On 19/07/2021 02.36, Craig Russell wrote:
>> Hi Humbedooh,
>> I'm looking at
>> https://clc.diversity.apache.org/analysis.html?project=db-jdo.git
>> The master branch was updated 8 days ago to resolve the issue with
>> Utilities. So the data
> Begin forwarded message:
>
> From: "Craig L Russell (Jira)"
> Subject: [jira] [Created] (INFRA-22118) Please change the default branch for
> JDO repositories to "main"
> Date: July 17, 2021 at 6:40:00 PM PDT
> To: c...@apache.org
>
> Craig L Russell created INFRA-22118:
>
https://clc.diversity.apache.org/analysis.html?project=db-jdo.git
https://clc.diversity.apache.org/analysis.html?project=db-jdo-site.git
Craig L Russell
c...@apache.org
Attendees: Michael Bouschen, Tobias Bouschen, Craig Russell
Next meeting: Thursday July 22 11:00 Pacific
Agenda:
1. Recent website changes and fix of deploy action
The web page guide-maven-jdo is not linked and seems to be obsolete (it refers
to JPOX which has not been in use since 2012
Since no objections to changing the name of the default git branch were raised,
we started to implement the change from master to main.
During the weekly conference call we created a new branch called main in each
repository, copied master to main, and updated the configuration files.
Please
dozens of
> times, at least. But ... why? This specific case is easier to remediate than
> almost any of the other ones - you change a branch name, and you spend an
> hour updating your tooling. It is by far the easiest win in this entire
> effort. Unlike, say, altering function names
Hi Bryan,
I appreciate that you follow the JDO project and send relevant information to
the board based on the weekly JDO discussions.
It really does help that you are subscribed to and actually read our somewhat
weekly discussions and report the information to the board.
Thanks,
Craig
> On
Attendees: Tobias Bouschen, Craig Russell
Next meeting: Thursday July 15 11:00 Pacific
Agenda:
1. Any items for the board report?
JDO project is getting ready to finalize 3.2. All issues scheduled for 3.2 have
been resolved. Working to finalize the specification.
2. JDO-709 "Standardize
Hi,
We will have our regular meeting Thursday July 8 11:00 AM Pacific Daylight Time
(PDT) to discuss JDO TCK issues and status.
We use the following dial-in for audio and video. You need a Skype account to
join.
https://join.skype.com/lKWOxZDu2O5U
Agenda:
1. Any items for the board report?
2.
Attendees: Michael Bouschen, Tilmann Zäschke, Tobias Bouschen, Craig Russell
Next meeting: Thursday July 22 11:00 Pacific
Agenda:
Question: Should we keep the change bars in the specification after we publish
3.2? It would be easier to find the changes. But it's too late for 3.2.
1. New db
Attendees: Michael Bouschen, Tilmann Zäschke, Tobias Bouschen, Craig Russell
Next meeting: Thursday July 1 11:00 Pacific
Agenda:
1. List of JDO 3.1 changes for appendix F revision History (see email from
Michael)
Question: Should we keep the JIRA issue numbers in the specification revision
Attendees: Michael Bouschen, Tilmann Zäschke, Tobias Bouschen, Craig Russell
Next meeting: Thursday June 24 11:00 Pacific
Agenda:
1. jdo-site publishing: question about db.apache.org/content/jdo (see email
from Craig)
Apparently the asf.yaml is configured to use the content directory. No issue
Hi,
Apparently ASF infra thinks that there is something special about the content
directory
db.apache.org/content/jdo
https://infra-reports.apache.org/site-source/
We should probably update the site to remove references to content...
Craig
Craig L Russell
c...@apache.org
Hi Michael,
> On Jun 13, 2021, at 2:56 PM, Bouschen, Michael
> wrote:
>
> Hi Craig,
>
> the spec changes sound good to me.
>
> If we do not like this new functionality including auto-boxing and converters,
I think it would be more work to try to disable auto-boxing since that is a
Java
I've reviewed the latest test cases for JDO-709 proposed by Michael. The test
cases introduce functionality not yet described by the specification.
So I've added the following to Chapter 6 in the Primitive types section.
Fields and properties of primitive types may use a converter in order to
Please review the changes in the jdo-709-spec branch. I think it's ready to
merge.
I had just a bit of trouble with the description of converters used with Map
keys and values and Collection elements.
I actually do not know if DataNucleus supports converted keys, values, and
elements for
Attendees: Michael Bouschen, Tilmann Zäschke, Tobias Bouschen, Craig Russell
Next meeting: Thursday June 17 11:00 PDT
Agenda:
1. Spec Updates JDO-709 <https://issues.apache.org/jira/browse/JDO-709>
"Standardize field/property converters"
@Converts annotation
Hi Andy,
Could you please take a look at https://issues.apache.org/jira/browse/JDO-709
We are finalizing the api, tck, and specification for this and have an issue.
The @Convert annotation does not have the attribute property so it can only be
used directly on a field/property. So it does not
Attendees: Michael Bouschen, Tobias Bouschen, Craig Russell
Next meeting: Thursday June 10 11:00 PDT
Agenda:
1. Spec Updates JDO-709 <https://issues.apache.org/jira/browse/JDO-709>
"Standardize field/property converters"
Chapter 6 might need a bit more clarity. "If the fi
Attendees: Michael Bouschen, Tobias Bouschen, Craig Russell
Next meeting: Thursday June 3 11:00 AM PDT
Agenda:
0. Does GitHub really disallow direct pushes to the master branch?
AI Tobias clarify GitHub action for direct pushes.
1. Recent GitHub changes re GitHubActions
https://github.blog
I thought these might be of interest...
Craig
> Begin forwarded message:
>
> From: Gavin McDonald
> Subject: Recent GH changes re GHA
> Date: May 24, 2021 at 2:31:04 AM PDT
> To: builds
> Reply-To: bui...@apache.org
> Reply-To: gmcdon...@apache.org
>
> Hi All,
>
> FYI
>
>
Attendees: Michael Bouschen, Tilmann Zäschke, Tobias Bouschen, Craig Russell
Next meeting: Thursday May 27 11:00 Pacific
Agenda:
1. Discussion about nightly releases: do we want/need nightly builds?
GitHub is already set up for builds on each push to master to run the tck (mvn
clean install
Attendees: Michael Bouschen, Tilmann Zäschke, Tobias Bouschen, Craig Russell
Next meeting: Thursday May 20 11:00 Pacific
Agenda:
1. Pull request #20 <https://github.com/apache/db-jdo/pull/20> - JDO-709
<https://issues.apache.org/jira/browse/JDO-709> "Standardize field/property
Attendees: Michael Bouschen, Tobias Bouschen, Tilmann Zäschke, Craig Russell
Next meeting: Thursday May 13 11:00 AM Pacific
Agenda:
1. JDO-785 <https://issues.apache.org/jira/browse/JDO-785> "Update release
instructions for new website and release process"
see
db-jdo maste
While researching Second Class Object behaviors, I found this in the
specification 6.3:
Second Class Objects of mutable system classes and persistence-capable classes
track changes made to them, and notify their owning FCO that they have changed.
Since converted classes most resemble
Attendees: Michael Bouschen, Tilmann Zäschke, Tobias Bouschen, Craig Russell
Next meeting: Thursday May 6 11:00 Pacific
Agenda:
1. JDO-785 <https://issues.apache.org/jira/browse/JDO-785> "Update release
instructions for new website and release process"
see
https://docs.googl
Attendees: Michael Bouschen, Tilmann Zäschke, Tobias Bouschen, Craig Russell
Next meeting: Thursday April 29 11:00 PDT
Agenda:
1. [DISCUSS] Rename main branch?
There is a consensus among the five people who responded that there is no need
to change the name at this time. We will keep the JIRA
> On Apr 20, 2021, at 12:28 AM, Marco Nguitragool wrote:
>
> Hi Craig,
>
> thanks for your reply!
>
> Am 19.04.21 um 22:20 schrieb Craig Russell:
>> Hi Marco,
>>
>>> On Apr 18, 2021, at 8:54 PM, Marco Nguitragool wrote:
>>>
>>
em!
I'd say evil wrong-doers are the main problem. Do you have another experience?
Regards,
Craig
>
> Regards, Marco.
>
> P.S.: I'm resending this e-mail. The last e-mail was lost (censorship?).
> Trying it again, now.
>
>
> Am 17.04.21 um 02:41 schrieb Craig
Hi,
I'd like to have all of us come to the same understanding of renaming the main
branch of our repos.
Here is some background reading to inform our decision.
https://github.com/pmmmwh/react-refresh-webpack-plugin/issues/113
Let's have a discussion now and vote later.
Regards,
Craig
Craig L
Hi Bryan,
The JDO project is still working on the 3.2 release. The web site db-jdo-site
db.apache.org/jdo is up and running.
Regards,
Craig
> On Apr 14, 2021, at 7:27 AM, Bryan Pendleton
> wrote:
>
> Hi all, it is time for our quarterly report to the board.
>
> Please let me know of any
Attendees: Michael Bouschen, Tilmann Zäschke, Tobias Bouschen, Craig Russell
Next meeting: Thursday April 22 11:00 AM PDT
Agenda:
1. Items for our April report to the board?
Still working on the 3.2 release. The web site db-jdo-site db.apache.org/jdo is
up and running.
2. JDO-785 https
Attendees: Michael Bouschen, Tobias Bouschen, Tilmann Zäschke, Craig Russell
Next meeting: Thursday April 15 11:00 AM PDT
Agenda:
1. PR #14 https://github.com/apache/db-jdo-site/pull/14 "Update README.md"
approved and merged
Any changes now can be edited and pushed to master.
Hi Tobous,
Thanks for your careful review and for these updates.
I think we're now done with the README, modulo finding all of the missing full
stops and until we change the name of the master branch...
Craig
> Begin forwarded message:
>
> From: GitBox
> Subject: [GitHub] [db-jdo-site]
Attendees: Michael Bouschen, Tobias Bouschen, Craig Russell
Next meeting: April 8 11:00 AM Pacific Daylight Time
Agenda:
1. Branch protection issues resolved?
Yes.
2. PR #14 https://github.com/apache/db-jdo-site/pull/14 "Update README.md"
Final version is available for review.
3.
Hi,
The web site is diversity.apache.org and it probably needs a page or two of
asciidoc and a little .asf.yaml and maybe a GitHub action or two.
Anyone interested in volunteering? Reply on d...@diversity.apache.org.
https://lists.apache.org/list.html?d...@diversity.apache.org
Thanks,
Craig
Attendees: Michael Bouschen, Tilmann Zäschke, Tobias Bouschen, Craig Russell
Next meeting: Thursday April 1 11:00 Pacific Daylight Time (PDT)
Agenda:
1. Branch protection issues (see email from Tobias "Branch protection")
Issue: cannot push directly to master any more. Need to cre
Attendees: Michael Bouschen, Tilmann Zäschke, Tobias Bouschen, Craig Russell
Next meeting: Thursday March 25 noon Pacific Daylight Time
Agenda:
1. PR #17 https://github.com/apache/db-jdo/pull/17 "JDO-791: Introduce basic
GitHub action for automated TCK builds"
Looks good. Note t
I'll join soon
Attendees: Michael Bouschen, Tilmann Zäschke, Tobias Bouschen, Craig Russell
Next meeting: Wednesday March 17 noon Pacific Daylight Time
Please NOTE the day and time change
Agenda:
1. Synchronization github -> gitbox not working?
Seems to work now. In future, send mail to us...@infra.apache.
Attendees: Michael Bouschen, Tilmann Zäschke, Tobias Bouschen, Craig Russell
Next meeting: Thursday March 11 11:00 AM Pacific Standard Time
Agenda:
1. Done PR #32 https://github.com/apache/db-jdo-site/pull/32 "Move
copy-resources from compile to prepare-package lifecycle phase"
Attendees: Michael Bouschen, Tilmann Zäschke, Tobias Bouschen, Craig Russell
Next meeting: Thursday March 4 11:00 AM Pacific
Agenda:
1. Done PR #29 https://github.com/apache/db-jdo-site/pull/29 "Use icons with
highest resolution available for website"
Question: do we have the origi
Attendees: Michael Bouschen, Tilmann Zäschke, Tobias Bouschen, Craig Russell
Next meeting: Thursday February 25 11:00 AM PST
Agenda:
1. Do we want/need a review etiquette: how do we want to deal with
contributions?
For the db-jdo-site repository. All changes should be submitted via a PR
Attendees: Michael Bouschen, Tilmann Zäschke, Tobias Bouschen, Craig Russell
Next meeting: Thursday February 18 11:00 AM Pacific
Agenda:
The web site for db.apache.org <http://db.apache.org/> needs attention but not
by the JDO project directly. It will probably take someone a day
ess 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 the changes to get-involved.
>>
>> Anyone else seeing the new content?
>>
>
I'm still not seeing the changes to get-involved.
Anyone else seeing the new content?
Craig
> On Feb 4, 2021, at 2:42 PM, Craig Russell wrote:
>
> I still have not seen these changes to get-involved published to the live
> site.
>
> Are we still suffering from "JD
I still have not seen these changes to get-involved published to the live site.
Are we still suffering from "JDO Site Failed To Deploy"?
Craig
> On Feb 4, 2021, at 12:06 PM, tilma...@apache.org wrote:
>
> This is an automated email from the ASF dual-hosted git repository.
>
> tilmannz pushed
Attendees: Michael Bouschen, Tilmann Zäschke, Tobias Bouschen, Craig Russell
Next meeting: Thursday February 11 11:00 AM PST
Agenda:
1. Issue resolved: INFRA-21326 "JDO website does not deploy"
https://issues.apache.org/jira/browse/INFRA-21326
<https://issues.apache.org/jira/brows
hanks,
> -Rick
>
> On 2/2/21 11:26 AM, Craig Russell wrote:
>> Hi,
>>
>> priv...@db.apache.org in bcc...
>>
>> The JDO project is almost complete migrating the db.apache.org/jdo site from
>> the soon-to-be-retired CMS system to a new github
db.apache.org/torque
<http://db.apache.org/torque>, db.apache.org/derby
<http://db.apache.org/derby>, as well as jdo.
>
> 2) Can we still manage our code repo with subversion?
This is above my pay grade. ;-)
Craig
>
> Thanks,
> -Rick
>
> On 2/2/21 11:26
Hi,
priv...@db.apache.org in bcc...
The JDO project is almost complete migrating the db.apache.org/jdo site from
the soon-to-be-retired CMS system to a new github site repo using GitHub
Actions and .asf.yaml to publish the site.
Infra wants to know what the plans are for the main site, Derby,
Attendees: Michael Bouschen, Tilmann Zäschke, Tobias Bouschen, Craig Russell
Next meeting: Thursday February 4 11:00 AM Pacific
1. Items for the DB quarterly report to the board
Migration of the db-jdo-site using GitHub Actions and .asf.yaml features.
Slow progress on release of JDO 3.2
Hi Bryan,
This is for the quarterly report...
Regards,
Craig
> On Jan 17, 2021, at 12:26 PM, Craig Russell wrote:
>
> Hi Bryan,
>
> The JDO project is continuing to evolve the web presence. We successfully
> migrated the site to a combination of GitHub Actions
anybody have any issues/reservations regarding this approach?
> Otherwise, I would do so some time next week to have a finished setup
> for the next JDO conference call.
>
> Best regards,
> Tobias
>
> On 23/01/2021 17:25, Craig Russell wrote:
>> Hi Tobias,
>>
Hi Tobias,
I've added a comment to the JIRA.
I think the problem might be that DB has a mixed configuration. The old CMS
system was discontinued last year. [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.
Attendees: Michael Bouschen, Tilmann Zäschke, Tobias Bouschen, Craig Russell
Next meeting: Thursday January 28 11:00 AM PST
Agenda:
1. PR #13 "Move site to separate branch" for db-jdo-site:
https://github.com/apache/db-jdo-site/pull/13
Looks good. AI Tobias merge the reques
Hi Bryan,
The JDO project is continuing to evolve the web presence. We successfully
migrated the site to a combination of GitHub Actions and ASF processing to
automatically publish "source" changes to the web site.
We are working toward a JDO 3.2 release, with a few items still left to
Attendees: Michael Bouschen, Tilmann Zäschke, Tobias Bouschen, Craig Russell
Next meeting: Thursday January 21 11:00 AM PST
Agenda:
1. PR #12 "Implement rudimentary push logic for deploy action" for db-jdo-site
https://github.com/apache/db-jdo-site/pull/12
Good. Merged.
2. PR #13
Attendees: Michael Bouschen, Tilmann Zäschke, Tobias Bouschen, Craig Russell
Next meeting: Thursday January 14 11:00 AM PST
Agenda:
1. New PR #13 "Move site to separate branch" for db-jdo-site:
https://github.com/apache/db-jdo-site/pull/13
Note, this includes PR #12 "Implem
Sorry about that. Try this:
https://docs.google.com/document/d/1Ey4a8-9yeWOBETAwmqgsfhnktI63c5_bPgQmypFc-Zc/edit?usp=sharing
> On Dec 31, 2020, at 2:05 PM, Michael Bouschen wrote:
>
> Hi Craig,
>
> it looks like I need special access rights to open the doc.
>
> Happy New Year!
>
> Regards
Hi,
I've added a description of how the site is published. Feedback welcome.
https://docs.google.com/document/d/1Ey4a8-9yeWOBETAwmqgsfhnktI63c5_bPgQmypFc-Zc/edit?usp=sharing
Have a happy New Year if you celebrate that thing.
Craig L Russell
c...@apache.org
Attendees: Michael Bouschen, Tilmann Zäschke, Craig Russell
Next meeting: Thursday January 7 11:00 PST
Agenda:
1. Changes to sources for GitHub Actions (see email on jdo-dev list)
The changes made by infra affected our GitHub Actions that automatically deploy
changes to the .adoc files
Hi Daniel,
Well, this change was a failure from db.apache.org/jdo perspective.
I committed a change to the db-jdo-site repo that used to automatically
propagate to the live site through a combination of GitHub Action and asf.yml.
Now it does not.
Any help here?
Thanks, and Happy New Year
Attendees: Michael Bouschen, Tilmann Zäschke, Craig Russell
Next meeting: Wednesday December 30 2020 11:00 AM Pacific
Agenda:
1. JDO-785 "Update release instructions for new website and release process"
https://issues.apache.org/jira/browse/JDO-785
see
https://docs.google.com/
Attendees: Michael Bouschen, Tilmann Zäschke, Craig Russell
Next meeting: Wednesday December 23 11:00 AM PST
Agenda:
1. JDO-785 "Update release instructions for new website and release process"
https://issues.apache.org/jira/browse/JDO-785
see
https://docs.google.com/
Attendees: Michael Bouschen, Tilmann Zäschke, Craig Russell
Next meeting: Thursday December 17 10:30 AM PST
Agenda:
1. JDO-787 "Check mvn clean rules"
https://issues.apache.org/jira/browse/JDO-787
<https://issues.apache.org/jira/browse/JDO-787>
Done. Resolved. Possible iss
Attendees: Michael Bouschen, Tilmann Zäschke, Craig Russell
Next meeting: Thursday December 10 10:30 AM Pacific
Agenda:
1. INFRA issue "Change to db-jdo-site does not
publish"https://issues.apache.org/jira/projects/INFRA/issues/INFRA-21128 is
closed
2. JDO-785 "Update relea
Attendees: Michael Bouschen, Tilmann Zäschke, Craig Russell
Next meeting: Thursday December 3 10:30 AM Pacific
Agenda:
1. Status INFRA issue "Change to db-jdo-site does not
publish"https://issues.apache.org/jira/projects/INFRA/issues/INFRA-21128
This seems to be a non-issue.
https://issues.apache.org/jira/projects/INFRA/issues/INFRA-21128
Slack chat:
@Craig Russell I see ZooDB on there, which is the latest addition...am I
missing something?
11:30
on https://db.apache.org/jdo/impls.html
db.apache.org
JDO Implementations
Apache JDO - Java Data Objects
11:33
maybe
Attendees: Michael Bouschen, Tilmann Zäschke, Craig Russell
Next meeting: Wednesday November 25 11:00 AM PST
Agenda:
1. Andy fixed the page
https://github.com/apache/db-jdo-site/blob/master/src/main/asciidoc/impls.adoc,
but the changes are not visible on the JDO web site:
http://db.apache.org
201 - 300 of 1711 matches
Mail list logo
