[Slackbuilds-users] Question about git workflow
harald.achitz at gmail.com
Sun Mar 5 17:42:54 UTC 2017
I am pretty sure that this, more cvs/svn orientated branching strategy is
There is no need for users to have branches, they should have forks.
There they can branch, and create for these branches pull requests.
Of course you can create also branches per user, but this only pollutes the
repo with unnecessary stuff.
You could take pull requests from every trust able person fore each
package, the maintainer models is total obsolete that only scales bad,
distributes work bad, and is a bottleneck by design.
Honestly, if, for example, Niki would make a pull request for some package
update because he needs it in MELD, I would pull it in if he is the
maintainer or not.
Maybe with a 'next release branch' for some time to give early adopter
chance to do additional testing, which his more a useful branching strategy
than per 'trusted user'.
And this is more the open source, or general how it works, model of today,
but of course just IMHO and I do not want to convince anybody of anything,
as usual this are just my 2 cents ;-)
2017-03-05 17:24 GMT+01:00 Willy Sudiarto Raharjo <willysr at slackbuilds.org>:
> > For the moment SBo prefers tarballs, well, for the moment that's the
> > only option.
> > There is no git for ordinary users and maintainers as of now.
> That's not true
> we do allow "some" maintainers to have their own branches in our GIT
> repository. See https://slackbuilds.org/cgit/slackbuilds/
> Willy Sudiarto Raharjo
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the SlackBuilds-users