From dev-return-66309-archive-asf-public=cust-asf.ponee.io@flex.apache.org Sat Jun 19 16:50:22 2021 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mxout1-ec2-va.apache.org (mxout1-ec2-va.apache.org [3.227.148.255]) by mx-eu-01.ponee.io (Postfix) with ESMTPS id 819DD18060E for ; Sat, 19 Jun 2021 18:50:22 +0200 (CEST) Received: from mail.apache.org (mailroute1-lw-us.apache.org [207.244.88.153]) by mxout1-ec2-va.apache.org (ASF Mail Server at mxout1-ec2-va.apache.org) with SMTP id 764F23EEA5 for ; Sat, 19 Jun 2021 16:50:21 +0000 (UTC) Received: (qmail 24059 invoked by uid 500); 19 Jun 2021 16:50:21 -0000 Mailing-List: contact dev-help@flex.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@flex.apache.org Delivered-To: mailing list dev@flex.apache.org Received: (qmail 24043 invoked by uid 99); 19 Jun 2021 16:50:21 -0000 Received: from mailrelay1-he-de.apache.org (HELO mailrelay1-he-de.apache.org) (116.203.21.61) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 19 Jun 2021 16:50:21 +0000 Received: from [IPv6:2601:649:280:9d60:bd73:ce88:4d3f:558e] (unknown [IPv6:2601:649:280:9d60:bd73:ce88:4d3f:558e]) by mailrelay1-he-de.apache.org (ASF Mail Server at mailrelay1-he-de.apache.org) with ESMTPSA id B968E3E848; Sat, 19 Jun 2021 16:50:19 +0000 (UTC) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.4\)) Subject: Re: CMS Migration for Flex From: Dave Fisher In-Reply-To: <21E9AAA3-AB24-4E55-8069-D6C51D66998A@apache.org> Date: Sat, 19 Jun 2021 09:49:06 -0700 Content-Transfer-Encoding: quoted-printable Message-Id: <031E40EB-A748-4DFA-A08D-3EAE41705581@apache.org> References: <0A67C1D6-4398-4A9E-961E-9DAB7D2635A6@apache.org> <21E9AAA3-AB24-4E55-8069-D6C51D66998A@apache.org> To: dev@flex.apache.org X-Mailer: Apple Mail (2.3608.120.23.2.4) The Migration from CMS to ASF-Pelican is completed! https://flex.apache.org/ is ready. https://github.com/apache/flex-site/ For information about ASF-Pelican: = https://infra.apache.org/asf-pelican.html Enjoy! Dave > On Jun 14, 2021, at 11:08 AM, Dave Fisher wrote: >=20 > The migrated website may be viewed at https://flex.staged.apache.org/ >=20 > The code is in https://github.com/apache/flex-site/tree/main >=20 > See the README there for links to details about the migration and ASF = pelican. >=20 > The FlexUnit tutorials required the most work. >=20 > Note the old cms git mirror (which is broken (that=E2=80=99s good)) of = the CMS was used. >=20 > Please review, I would like to make this production in the next week. >=20 > All The Best, > Dave >=20 >> On Jun 9, 2021, at 11:30 AM, Dave Fisher wrote: >>=20 >> As you may recall the Apache CMS has been deprecated for over five = years now and will be decommissioned >> by July 31, 2021. >>=20 >> I=E2=80=99ve been tasked with moving OpenWebBeans's website away from = the Apache CMS. >> I will migrate your website to a Pelican build with GitHub Flavored = Markdown (GFM). >> For your reference the already migrated www-site is here = https://github.com/apache/www-site/ >>=20 >> The following will occur. >> - flex-site git repository is already a mirror of the CMS content. = We=E2=80=99ll create a main branch. >> - CMS mdtext and Cmspage files are converted to md and stored in the = content tree. >> - Page templates will be converted essentially as is with some minor = improvements. >> - HTML files (apidocs) built separately are copied into the content = tree.=20 >>=20 >> The Apache CMS had a cumbersome process of individual checkouts -> = staging -> publishing. >> The new branching strategy is as follows: >> - main will have the site content sources and any additional docs = (like api docs). >> - asf-site will have the production website which is automatically = deployed to flex.apache.org. >> During the migration we will deploy to flex.staged.apache.org >> - preview/release will have the website prepared for the next = release. You will add release specific docs to this branch >> - preview/release-staging will have the built preview website which = is automatically deployed to flex-release.staged.apache.org >>=20 >> This new plan allows for a redesign of your site without danger of = premature deployment. >> If you decide that GFM is not for flex then you can switch to a = different process within a preview branch. >>=20 >> Release steps for the website could be: >> - Branch main as preview/release >> - Make your updates to preview/release >> - Confirm your changes on flex-release.staged.apache.org >> - Pull your changes from preview/release to main. flex.apache.org is = automatically updated. >>=20 >> All The Best, >> Dave Fisher >=20