reproduce-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[task #15635] Stable branch and/or release candidates/official releases


From: Boud Roukema
Subject: [task #15635] Stable branch and/or release candidates/official releases
Date: Thu, 14 May 2020 23:06:04 -0400 (EDT)
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Firefox/68.0

Follow-up Comment #2, task #15635 (project reproduce):

Just to throw ideas around...

One idea is to have some sort of a table - plain text :) - maybe cvs for
example, or yaml, with commit numbers, and values such as developer IDs and
confirmation that that developer thinks that the commit works as expected, and
values for particular OSes, stating that the full cycle, including creating
the default paper.pdf, worked (or failed) on that OS.

We could then automatically convert that table into a compact form that is
human-understandable about the quality and likelihood of working as expected;
and/or into xml or html format for web pages.

Debian has a whole range of quality control pipelines, e.g.

https://tracker.debian.org/pkg/inhomog
https://tracker.debian.org/pkg/gnuastro

If we want to seriously claim all-POSIX validity, then we also need to find a
windows-with-POSIX volunteer.



    _______________________________________________________

Reply to this item at:

  <https://savannah.nongnu.org/task/?15635>

_______________________________________________
  Message sent via Savannah
  https://savannah.nongnu.org/




reply via email to

[Prev in Thread] Current Thread [Next in Thread]