BTW we should use master branch from now on :) I'll drop `asf-site` branch as soon as I'll ensure everything works :)
On Tue, 1 Jun 2021 at 09:15, Maxim Solodovnik <solomax...@gmail.com> wrote: > I believe we should be OK now > I'll check again later today :)) > > On Tue, 1 Jun 2021 at 08:13, Maxim Solodovnik <solomax...@gmail.com> > wrote: > >> Yes, >> >> I'm going to perform necessary changes today :))) >> >> On Tue, 1 Jun 2021 at 04:17, seba.wag...@gmail.com <seba.wag...@gmail.com> >> wrote: >> >>> Hi, >>> >>> is below relevant to us? >>> >>> Thanks! >>> Seb >>> >>> Sebastian Wagner >>> Director Arrakeen Solutions, OM-Hosting.com >>> http://arrakeen-solutions.co.nz/ >>> https://om-hosting.com - Cloud & Server Hosting for HTML5 >>> Video-Conferencing OpenMeetings >>> < >>> https://www.youracclaim.com/badges/da4e8828-743d-4968-af6f-49033f10d60a/public_url >>> > >>> < >>> https://www.youracclaim.com/badges/b7e709c6-aa87-4b02-9faf-099038475e36/public_url >>> > >>> >>> >>> ---------- Forwarded message --------- >>> From: Daniel Gruno <humbed...@apache.org> >>> Date: Tue, 1 Jun 2021 at 01:41 >>> Subject: [NOTICE] Git web site publishing to be done via .asf.yaml only >>> as >>> of July 1st >>> To: Users <us...@infra.apache.org> >>> >>> >>> TL;DR: if your project web site is kept in subversion, disregard this >>> email please. If your project web site is using git, and you have not >>> deployed it via .asf.yaml, you MUST switch before July 1st or risk your >>> web site goes stale. >>> >>> >>> >>> Dear Apache projects, >>> In order to simplify our web site publishing services and improve >>> self-serve for projects and stability of deployments, we will be turning >>> off the old 'gitwcsub' method of publishing git web sites. As of this >>> moment, this involves 120 web sites. All web sites should switch to our >>> self-serve method of publishing via the .asf.yaml meta-file. We aim to >>> turn off gitwcsub around July 1st. >>> >>> >>> ## How to publish via .asf.yaml: >>> Publishing via .asf.yaml is described at: >>> https://s.apache.org/asfyamlpublishing >>> You can also see an example .asf.yaml with publishing and staging >>> profiles for our own infra web site at: >>> https://github.com/apache/infrastructure-website/blob/asf-site/.asf.yaml >>> >>> In short, one puts a file called .asf.yaml into the branch that needs to >>> be published as the project's web site, with the following two-line >>> content, in this case assuming the published branch is 'asf-site': >>> >>> publish: >>> whoami: asf-site >>> >>> >>> It is important to note that the .asf.yaml file MUST be present at the >>> root of the file system in the branch you wish to publish. The 'whoami' >>> parameter acts as a guard, ensure that only the intended branch is used >>> for publishing. >>> >>> >>> ## Is my project affected by this? >>> The quickest way to check if you need to switch to a .asf.yaml approach >>> is to check out site source page at >>> https://infra-reports.apache.org/site-source/ - if your site is listed >>> in yellow, you will need to switch. This page will also tell you which >>> branch you are currently publishing as your web site. This is (should >>> be) the branch that you must add a .asf.yaml meta file to. >>> >>> The web site source list updates every hour. If your project site >>> appears in green, you are already using .asf.yaml for publishing and do >>> not need to make any changes. >>> >>> >>> ## What happens if we miss the deadline? >>> If you miss the deadline, don't fret. Your site will of course still >>> remain online as is, but new updates will not appear till you >>> create/edit the .asf.yaml and set up publishing. >>> >>> >>> ## Who do we contact if we have questions? >>> Please contact us at us...@infra.apache.org if you have any additional >>> questions. >>> >>> >>> With regards, >>> Daniel on behalf of ASF Infra. >>> >> >> >> -- >> Best regards, >> Maxim >> > > > -- > Best regards, > Maxim > -- Best regards, Maxim
