- From: David Singer <singer@apple.com>
- Date: Thu, 28 Sep 2017 10:36:28 -0700
- To: Fuqiao Xue <xfq@w3.org>
- Cc: Chaals McCathie Nevile <chaals@yandex.ru>, public-w3process <public-w3process@w3.org>, Léonie Watson <tink@tink.uk>
> On Sep 27, 2017, at 19:13 , Fuqiao Xue <xfq@w3.org> wrote: > > On 2017-09-28 05:02, David Singer wrote: >>>>> Some responses to this would be appreciated. >>>>> We intend to ‘freeze’ top-of-tree during AC review, so the document at github.io remains unchanged. Issues and pull requests that land as part of AC review will be held (or a branch will be made) so the AC has a consistent document to comment on. >>>> Makes sense. Suggest taking a branch as the stable snapshot, and allowing subsequent edits to happen on the default branch. >>> +1 >> I don’t know how to do this, as gh-pages is what gets published, and I >> don’t know how to get something displayed if it’s not gh-pages or >> master. So if Chaals knows how to do this... > > One option might be: > > 1. Change the default branch from gh-pages to master; > 2. Use the gh-pages branch for GitHub Pages publishing (which is already the case now); > 3. Change the base branch of the pull requests to master (which is pretty easy, with current GitHub UI); > 4. Use gh-pages as the "stable snapshot" branch; > 5. Optionally, we can change the publishing pages to master after the AC review. maybe...how does one view as a readable document the master branch, if github.io is configured to use gh-pages (or vice versa)? > > WDYT? > > Fuqiao David Singer Manager, Software Standards, Apple Inc.
Received on Thursday, 28 September 2017 17:36:51 UTC