Jun Aruga wrote:
> But in case of module, each developer can create any branch
> technically under their responsibility,
And that is the issue, really.
Kevin Kofler
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an e
> So Modularity will happily unleash experimental branches that were never
intended to be released onto unsuspecting users of stable releases? How can
this not be an absolute showstopper? This failed Modularity experiment needs
to end NOW!
As far as I know, there was no rule for the branch name, f
Coty Sutherland wrote:
> I'm working on (learning modularity) and developing a module for my
> package and created a not-so-great (super long) branch name in the
> dist-git rpm and module repo before I realized that it would be the
> stream's name too. Also, it seems that the incomplete module was
>> Yes, you can hide the branch from the result of "dnf module list". I
>> asked it to someone to hide "private-jaruga-master" stream.
>> But I forget the way.
>
>
> Maybe someone else can help :D
I remembered the way after searching my past emails. :D
You can open a ticket on releng to hide it li
Thanks for responding!
On Fri, Sep 27, 2019 at 8:54 AM Jun Aruga wrote:
> > I'm working on (learning modularity) and developing a module for my
> package and created a not-so-great (super long) branch name in the dist-git
> rpm and module repo before I realized that it would be the stream's name
> I'm working on (learning modularity) and developing a module for my package
> and created a not-so-great (super long) branch name in the dist-git rpm and
> module repo before I realized that it would be the stream's name too.
I faced similar situation. Ruby module was released as
"private-jaru
Hi all,
I'm working on (learning modularity) and developing a module for my package
and created a not-so-great (super long) branch name in the dist-git rpm and
module repo before I realized that it would be the stream's name too. Also,
it seems that the incomplete module was picked up and included
