mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Zach van Rijn <me@zv.io>
To: musl@lists.openwall.com
Subject: Re: [musl] Current state and future of musl development infrastructure
Date: Thu, 16 Dec 2021 13:20:27 -0600	[thread overview]
Message-ID: <b3e7100ce3b7df263767ce2d282c88aae90e4ec8.camel@zv.io> (raw)
In-Reply-To: <20211216050220.GL7074@brightrain.aerifal.cx>

On Thu, 2021-12-16 at 00:02 -0500, Rich Felker wrote:
> ...
> 
> I'd really love if the CI were optimized to do incremental
> builds and reuse artifacts as much as possible for rapid
> results, but doing that right probably requires fixing missing
> dependency tracking in the build.

I'd recommend taking ccache for a spin before investing time in a
more involved solution. What type of security/access requirements
do you have? E.g. a mechanism to keep some code/tests private?


> A manually curated TODO list/wishlist on the wiki was how this
> was managed for the last N years, and it wasn't really good
> because it failed to link community discussion of the issue and
> didn't capture things not already valued by me or community.
> Even with a bug tracker it would be perfectly fine (and much
> more effective than it is now) to have a TODO/roadmap, since it
> could *link to* the relevant tracker items for more detail and
> record of what exactly is wanted or proposed and why.

Leah suggested Request Tracker [0] yesterday in IRC but setup is
pretty nasty [1] (quote):

    Some modules require user input or environment variables to
    install correctly, so it may be necessary to install them
    manually. Some modules also require external source
    libraries, so you may need to install additional packages.

Not to mention database backups, upgrades, and other maintenance.

One might consider Mantis [2]. It's brilliantly simple, so I've
put together a quick example of a minimal setup [3]. Someone will
need to figure out how to enable email support in this example.

A live demo (official Mantis bug tracker) is here [4].


ZV

[0]: https://bestpractical.com/download-page
[1]: https://docs.bestpractical.com/rt/5.0.2/README.html
[2]: https://www.mantisbt.org/
[3]: https://git.zv.io/t/musl-rt
[4]: https://mantisbt.org/bugs/my_view_page.php


      parent reply	other threads:[~2021-12-16 19:20 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-15 21:22 jvoisin
2021-12-15 22:52 ` Zach van Rijn
2021-12-16  5:02   ` Rich Felker
2021-12-16 11:40     ` Natanael Copa
2021-12-16 13:50       ` Rich Felker
2021-12-16 19:20     ` Zach van Rijn [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=b3e7100ce3b7df263767ce2d282c88aae90e4ec8.camel@zv.io \
    --to=me@zv.io \
    --cc=musl@lists.openwall.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/musl/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).