> For example a Bugzilla, where a bug can be easily reassigned to a different
> component .
GitHub can do this as well (it's a beta feature).
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
> That's what I'm been mulling over here. Pulling stuff from multiple places
> does complicate release-cutting considerably though (which tends to be hard
> enough as it is), and will mean that bugs will get reported on rpm, but the
> code will be someplace else, which I suspect would be a
> Perhaps separate git repos and a unified release are not mutually exclusive,
> though.
That's what I'm been mulling over here. Pulling stuff from multiple places does
complicate release-cutting considerably though (which tends to be hard enough
as it is), and will mean that bugs will get
> I know that Miro has expressed concerns about splitting language-specific
> tools into different repos because it tends to be more difficult to get those
> tools into broad use if they're separate releases.
I believe that was Neal.
--
You are receiving this because you are subscribed to
I know that Miro has expressed concerns about splitting language-specific tools
into different repos because it tends to be more difficult to get those tools
into broad use if they're separate releases. Perhaps separate git repos and a
unified release are not mutually exclusive, though.
What
I can see some benefits of having some standalone domain-specific repos, like a
repo for Python scripts. However, I think Python is one of the special cases,
splitting out all the scripts would seem to me an overkill. And if we split
only some and leave the rest in rpm, it's more mess than we
> Well, nothing prevents you having extensive testsuite for python, rust and
> whatnot in one repo.
Bad maintainability?
--
I think we need to have some sort of distro-wide SIGs that can own things. I
will take Python as an example (and we can pyoneer (hehe) this with Python and
see what
Well, nothing prevents you having extensive testsuite for python, rust and
whatnot in one repo.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
Having separate CI is a feature I think - different languages will prefer
different testing tools etc.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
I think having them in one repository makes more sense to me because of sharing
some code, knowledge and so on If there would be bunch of separate repos,
you'd need to implement CI for each of them and so on.
I think the best would be to get interested people aboard and move things like
@torsava @Conan-Kudo @hroncok @gordonmessmer @ignatenkobrain, opened this to
avoid further polluting #1195 with this. The topic is not Python specific but
the Python bits have an obviously active community around it so it's a good
candidate for splitting, feel free to tag others into discussion
The subject has been polluting numerous PR's lately, better to have this
discussion separately:
We've been on this road for a long time now, starting from rpm 4.9 introducing
the "new" drop-in dependency generator enabling generators to live at the
source instead of forcing them into rpm. More
12 matches
Mail list logo
