[Infrastructure] Preparation of review period for SC30 and SC31

[Dimitris Zacharopoulos]

That's fine.

Do we have the artifacts from the current official master branch? I can create a PR on our official repo, that contains the commits of both ballots if that automatically creates new artifacts. Then, I can use MS word to compare the display the changes, thus creating a redline.

Would this work?

DZ.

Jul 17, 2020 18:32:10 Jos Purvis (jopurvis) <jopurvis at cisco.com>:

> Hmmm. So I know we’ve never produced uploaded artifacts from PRs from other people’s forks, which makes sense—I thought that was the discussion. We’ve been producing artifacts from PRs of branches actually on the cabforum repo, though, because a quick peruse of the S3 bucket contents shows a folder for each cabforum/documents branch up through pandoc-travis-changes.
> 
> --
> Jos Purvis (jopurvis at cisco.com)
> .:|:.:|:. cisco systems | Cryptographic Services
> PGP: 0xFD802FEE07D19105 | Controls and Trust Verification
> 
> From: Ryan Sleevi <sleevi at google.com>
> Date: Friday, July 17, 2020 at 11:07 AM
> To: "Jos Purvis (jopurvis)" <jopurvis at cisco.com>
> Cc: "Dimitris Zacharopoulos (HARICA)" <dzacharo at harica.gr>, "infrastructure at cabforum.org" <infrastructure at cabforum.org>
> Subject: Re: [Infrastructure] Preparation of review period for SC30 and SC31
> 
> On Fri, Jul 17, 2020 at 10:50 AM Jos Purvis (jopurvis) <jopurvis at cisco.com> wrote:
> 
>> Hi Dimitris,
>> 
>> For the current version in Word format, you can fetch it from this link:
>> https://cabforum-travis-artifacts.s3-us-west-2.amazonaws.com/builds/master/BR.docx
>> 
>> That's the same link as the PDF from the front page of the CABF repository, but with the extension changed to docx (we need to update the README on the repository to reflect the new formats and whatnot!).
>> 
>> For the SC30 and SC31 ballots, the Travis build completed successfully, but it doesn't look like it uploaded the resulting artifacts to S3. Ryan, is that something we need to fix? (Looks like that used to be the default and isn't anymore?)
>> 
> I think there's some confusion. It was never the default to upload artifacts for PRs. This is the whole discussion about the need to create a dedicated branch within the main CABF repository, then create a PR using that, to have the artifact produced. I'll see about doing that later today.
> 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.cabforum.org/pipermail/infrastructure/attachments/20200717/137e2942/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 5584 bytes
Desc: not available
URL: <http://lists.cabforum.org/pipermail/infrastructure/attachments/20200717/137e2942/attachment.p7s>