Re: [DISCUSS] SQLLine as a sub-project of DB

for SQLLine. DB already >> has a SQL REPL tool called ij, which can be deployed against any JDBC >> database. The ij REPL tool is part of the Derby toolset: >> https://db.apache.org/derby/docs/10.15/tools/ctoolsij34525.html There could >> be some interesting cross-pollination

Re: [DISCUSS] SQLLine as a sub-project of DB

;>>> >>>>> Thanks. >>>>> >>>>> - Carl >>>>> >>>>> [1] https://db.apache.org/management.html >>>>> >>>>> On 2021/11/01 19:30:11 Julian Hyde wrote: >>>>>> Th

Re: [DISCUSS] SQLLine as a sub-project of DB

her to sponsor. > > Julian > > [1] https://cwiki.apache.org/confluence/display/INCUBATOR/New+Podling+Proposal > >> On Apr 1, 2022, at 5:13 PM, Craig Russell wrote: >> >> Hi, >> >> The hard part about bringing in sub-projects is what the incub

Re: svn commit: r1078263 - /websites/production/db/content/derby/

Hi Gav, Thanks so much for helping us get here. From my browser, all sub-projects are now in working order. Thanks again, Craig > On Feb 2, 2022, at 7:55 AM, gmcdon...@apache.org wrote: > > Author: gmcdonald > Date: Wed Feb 2 15:55:34 2022 > New Revision: 1078263 > > Log: > move Derby sub

Re: svn commit: r1078263 - /websites/production/db/content/derby/

rmer link is correct on the main db.apache.org page. I guess we will need some help restoring the contents. Gav, could you find the (now static) contents and restore them? Thanks, Craig > > ... unless I put a wrong link in the DB page? > > Best, > Til > > > On 02/02/2022 19:3

Re: svn commit: r1078263 - /websites/production/db/content/derby/

Hi Gav, Looks good. Thanks again, Craig > On Feb 3, 2022, at 5:36 AM, Gavin McDonald wrote: > > Hi, > > On Wed, Feb 2, 2022 at 10:46 PM Craig Russell <mailto:apache@gmail.com>> wrote: > Hi Til, Gav, > > > On Feb 2, 2022, at 11:38 AM, Tilmann

Fwd: [jira] [Created] (INFRA-22837) Please change the reply-to email for notifications to general@db.apache.org

FYI... > Begin forwarded message: > > From: "Craig L Russell (Jira)" > Subject: [jira] [Created] (INFRA-22837) Please change the reply-to email for > notifications to general@db.apache.org > Date: February 3, 2022 at 7:05:00 PM PST > To: c...@apache.org > > Craig L Russell created

Lazy consensus to deploy new db.apache.org web site

The replacement web site is ready to deploy. https://github.com/apache/db-site Please take a look (try building the site locally). If no objections by Monday January 31, we will publish the site. Best regards, Craig Craig L Russell c...@apache.org

db.apache.org web site

Hi, The DB project is currently migrating the web site to a brand new process started by Tilmann Zäschke (thanks, Til). If you are not already subscribed to general@ please do so in order to participate in this discussion. Current status: under development. Please visit

Github emails for db-site

It's time to change the notification emails for the db-site. I think that pull requests should go to general@ but pushes, commits, and other details like updates to the site via asf.yaml, protected branch notices, etc. should go to notifications@. My objective is for general to get discussions

Fwd: Protected Branches for db-site.git has been updated

So how do we get Protected Branches messages to go to notifications@ And why do we get these messages anyway??? Craig > Begin forwarded message: > > From: GitBox > Subject: Protected Branches for db-site.git has been updated > Date: January 23, 2022 at 9:13:17 AM PST > To:

Re: Github emails for db-site

m happy to change it if people disagree? > > Best, > Til > > > On 23/01/2022 01:25, Craig Russell wrote: >> It's time to change the notification emails for the db-site. >> >> I think that pull requests should go to general@ but pushes, commits, and >> other

Site db.apache.org misconfiguration?

Hi, The DB project are working on replacing the db.apache.org site with a site built using GitHub at apache/db-site. Most of the work is done but we have an unexpected anomaly. Each push to the sources seems to generate two GitHub messages, e.g. [1] and [2]. There is probably a

[ANNOUNCE] Member of DB PMC Tobias Bouschen

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

Re: Extend closer.lua to act as a download page

I'd like to ask on behalf of the DB PMC for the infra tool closer.lua to be enhanced a bit for use by projects. It will be much easier for us if we can simply link to e.g. https://www.apache.org/dyn/closer.lua/db/jdo/3.2/jdo-3.2-source-release.tar.gz and have that page contain the .asc and

Fwd: Extend closer.lua to act as a download page

/closer.lua/db/jdo/3.2/jdo-3.2-source-release.tar.gz and the linked page would have everything needed to download the release and verify the checksum and signatures. Regards, Craig > Begin forwarded message: > > From: Craig Russell > Subject: Re: Extend closer.lua to act as a download

Re: Extend closer.lua to act as a download page

;> My idea here was just to link to the sig and hash by adding the >>>>> appropriate suffix to the artifact path name, and checking that it >>>>> exists. >>>>> e.g. look for db/jdo/3.2/jdo-3.2-source-release.tar.gz + .asc also >>>>> .