The site is now published from the new automated staging process. Much less complicated to publish from the markdown now. :) Instructions in https://github.com/apache/fluo-website#publishing , if you aren't already familiar.
On Thu, Aug 13, 2020 at 4:29 PM Christopher <ctubb...@apache.org> wrote: > > INFRA has completed their part. I have an open PR to update the links > on the website now and to configure our automated site staging: > https://github.com/apache/fluo-website/pull/195 > After it is merged, I will need to verify the staged site build and do > some one-time steps to publish it. > > I have not yet looked at the docs for the other repos, but can > probably expect that some residual references to 'master' branches > exist in those that I can do PRs for soon. Maybe next week. > > On Tue, Aug 11, 2020 at 9:54 AM Christopher <ctubb...@apache.org> wrote: > > > > For reference, here's the INFRA ticket: > > https://issues.apache.org/jira/browse/INFRA-20671 > > > > > > On Tue, Aug 11, 2020 at 9:39 AM Christopher <ctubb...@apache.org> wrote: > > > > > > Okay, since there are no objections, I will proceed with implementing the > > > default branch changes first, and then will work on the updates to the > > > website build process. > > > > > > > > > On Mon, Aug 10, 2020 at 4:14 PM Arvind Shyamsundar > > > <arvin...@microsoft.com.invalid> wrote: > > >> > > >> +1 > > >> > > >> -----Original Message----- > > >> From: Billie Rinaldi <bil...@apache.org> > > >> Sent: Monday, August 10, 2020 1:12 PM > > >> To: dev@fluo.apache.org > > >> Subject: [EXTERNAL] Re: [LAZY][VOTE] Branch renames and automated site > > >> build from 'main' branch > > >> > > >> +1 > > >> > > >> On Sat, Aug 8, 2020 at 5:07 AM Christopher <ctubb...@apache.org> wrote: > > >> > > >> > We should use 'main' for our default branch in all of our Fluo repos > > >> > (including the 'fluo-website' repo, which currently uses 'gh-pages'). > > >> > Any content in 'master' branches should be moved into 'main' branches > > >> > instead. > > >> > > > >> > Additionally, for the 'fluo-website' repo, I'd like to configure it > > >> > for automatic staging to an `asf-staging` branch by leveraging ASF > > >> > INFRA's .asf.yaml features out of the new default 'main' branch, from > > >> > which we can publish by moving commits to `asf-site` with a simple git > > >> > one-liner. We have been doing this for some time now in the Apache > > >> > Accumulo project, and it is working out nicely, so I want to bring it > > >> > here also. If you have questions about how that works, please refer > > >> > to: > > >> > https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgith > > >> > ub.com%2Fapache%2Faccumulo-website%2Fblob%2Fmain%2FREADME.md%23publish > > >> > ing&data=02%7C01%7Carvindsh%40microsoft.com%7C23ce0ef1a25d405f8fee > > >> > 08d83d69a750%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637326871681 > > >> > 121000&sdata=TatMntzKeb3hw91RjJacYnxQQYrlVpr3cehzQdsjerI%3D&re > > >> > served=0 > > >> > (or ask me) > > >> > > > >> > This is a lazy vote, so it will pass unless there are any objections > > >> > raised, in which case, it becomes a majority vote. If there is a -1 > > >> > for the website build part only, but not for the branch rename, then > > >> > this vote will proceed on the branch renames only, and we will discuss > > >> > the website build separately. > > >> > > > >> > I'm happy to start working on these once the vote passes. > > >> > > > >> > This vote will end after Tue 11 Aug 2020 09:30:00 AM UTC (Tue 11 Aug > > >> > 2020 05:30:00 AM EDT / Tue 11 Aug 2020 02:30:00 AM PDT) > > >> > > > >> > Thanks, > > >> > Christopher > > >> >
