[VOTE] [RESULTS] JDO 3.2.1 release
Dear all, JDO 3.2.1 (based on 3.2.1 RC2) has been approved as an official Apache JDO release. Thanks to all who worked on the release and who voted. +1 Craig Russell (pmc) Michael Bouschen (pmc) Tilmann Zäschke (pmc) Tobias Bouschen (Committer) There were no other votes. Kind regards, Til
Re: Derby, JDO, Torque websites missing - please redeploy websites
Dear all, @Derby & @Torque it looks like it has been fixed but Derby and Torque would need to redeploy their websites, could you do that? https://issues.apache.org/jira/browse/INFRA-22822 Let me know if I need to go through a different channel. Sorry for the inconvenience, Til On 31/01/2022 19:47, Bryan Pendleton wrote: Does this discussion help explain things at all? It seems to discuss the need for some 'svn mv' commands to relocate the subproject websites within Subversion? https://issues.apache.org/jira/browse/INFRA-21381?focusedCommentId=17481976=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-17481976 On Mon, Jan 31, 2022 at 9:55 AM Tilmann Zäschke wrote: Hi, Updating the DB website succeeded, but the subproject websites disappeared. I reported this here: https://issues.apache.org/jira/browse/INFRA-22822 https://db.apache.org/ Any help is appreciated. Best, Til
Derby, JDO, Torque websites missing
Hi, Updating the DB website succeeded, but the subproject websites disappeared. I reported this here: https://issues.apache.org/jira/browse/INFRA-22822 https://db.apache.org/ Any help is appreciated. Best, Til
new db.apache.org web site - PROBLEM
Hi, I just enabled the new DB website: https://db.apache.org/ This worked "fine". Problem: The websites of Derby, JDO and Torque have disappeared. I tried to reinstall the JDO website without success. I will now contact infra to see whether they can reinstantiate the websites. Any help would be appreciated. Best, Til On 28/01/2022 08:10, Gavin McDonald wrote: Hi, On Thu, Jan 27, 2022 at 11:25 PM Craig Russell wrote: 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. You can publish any time, I have removed the CMS configs. Best regards, Craig Craig L Russell c...@apache.org -- *Gavin McDonald* Systems Administrator ASF Infrastructure Team
Re: Fwd: Protected Branches for db-site.git has been updated
Ah, now I see what you mean, I have no idea why we have those messages... Til On 24/01/2022 21:11, Tilmann wrote: I think it is an admin update, so slightly more important than a commit. I am not sure where they go now, we would have to try. These messages were sent before I changed the email list targets. Til On 24/01/2022 06:44, Craig Russell wrote: 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: *priv...@db.apache.org *Reply-To: *priv...@db.apache.org The following changes were applied to db-site by mbo. GitHub Protected Branches has been enabled on branch=main With regards, ASF Infra. Craig L Russell c...@apache.org
Re: Github emails for db-site
I changed it (almost) as you proposed, Craig: commits: notificati...@db.apache.org issues: general@db.apache.org pullrequests: general@db.apache.org I used 'general' for issues because, though there shouldn't ever be issues reported, if there are, I think they are equally as important as pullrequests. I am 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 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 of changes but not necessarily details. WDYT? Craig Craig L Russell c...@apache.org
