A site-wide freeze during which there was a huge, rushed code dump was not the most effective way to manage or review the large website changes last time, and I don't think it would be a good idea to attempt that again.
Instead, can we create a parallel directory/site in our repo, incrementally build/commit/review it in there, and once everyone is happy with it do a single switch with a small redirection commit (followed by deleting the old content). As for incorporating changes that happen during development, this is what every developer is already doing (on the code side) and we should take advantage of the revision control systems we use to make sure nothing is lost. - Robert On Sun, Jan 10, 2021 at 4:07 PM Griselda Cuevas <g...@apache.org> wrote: > Hi folks, > > As you know we've been working on a revamp for the website, and we're > getting ready to commit the work we've done. In order to minimize the risk > of losing changes other contributors make during this period, we'd like to > plan a freeze so we can work on making the revamp commits. A freeze in this > context would mean that we give notice to our dev community to do not make > any PRs or change to the site during this period. > > I'd like to propose we have a one-week freeze during the last week of > January or the first week in February. > > What do you think? > > G >
