On Wed, 2021-01-27 at 10:25 -0800, Kevin Fenzi wrote:
On Tue, Jan 26, 2021 at 06:42:58PM -0800, Michel Alexandre Salim
wrote:
> On Mon, 2021-01-25 at 11:40 -0500, Matthew Miller wrote:
> > On Mon, Jan 25, 2021 at 04:43:21PM +0100, Fabio Valentini wrote:
> > > But that would involve at least six new steps that would've to
> > > be
> > > automated: 1) Creating a fork on src.fp.o (plus error handling
> > > around
> > > already existing forks), 2) Cloning the fork instead of the
> > > main
> > > repo,
> > > 3) Automatically creating a PR after a git push, 4)
> > > Automatically
> > > merging the PR if CI passes, 5) Deleting the fork, 6)
> > > Automatically
> > > building the package in koji ...
> >
> > Yeah, honestly, this is also a pretty serious hardship for the
> > long
> > tail of
> > people maintaining a handful of infrequently updated packages.
> > I'm
> > hugely in
> > favor of not checking in work in progress on the main or release
> > branches,
> > but let's not make more steps.
> >
> Similar to the (optional) playground repo we have for epel8 --
> would
> having a 'rawhide-playground' repo help?
With what goals?
With the goal to have experimental commits go there, but on
further
thought forking the package and doing such tests there is probably a
better idea.
Best regards,
--
Michel Alexandre Salim
profile:
https://keyoxide.org/michel@michel-slm.name