<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div dir="ltr"><blockquote type="cite">On Jul 28, 2020, at 7:53 AM, Keith Wheeler wrote:<br>This also opens the question of do we have a repo for source and another for tagged released outputs.</blockquote><br></div><div dir="ltr">I’m curious as to why it might be a good idea to have separate repos for work and outputs. At first glance it would seem to me that this is just asking for version skew confusion and extra work.</div><blockquote type="cite"><div dir="ltr"><div dir="ltr"><ol><li><p style="margin-bottom:0in;line-height:100%;background:transparent none repeat scroll 0% 0%">Not all parties interested in the schematic and
layout source files will desire access to the tool. We should publish
these in a more common format (pdf?), perhaps at every tagged release.</p></li></ol></div></div></blockquote>Yes, we absolutely should. Even people who do have access to the tools may find it quicker and easier to open a PDF for reference. The semantics of the special source file formats can have dependencies on library files that could become separated (or version skewed) from the design, or on features of specific tool versions. A stable, widely recognized, print-oriented format like PDF gives a valuable point of reference for what the thing is supposed to look like. Ancillary text-based outputs like netlists can also be helpful for people working with the hardware.<div><br></div><div> -Paul KB5MU</div><div><br></div></body></html>