[Slackbuilds-users] Package versions

[Harald Achitz]

as mentioned in the earlier mail, for example
stable , testing, pull requests into testing, who wants can test, if no
problem reports, or some people say OK, (to be defined) it goes to stable.
the QA happens twice, once when apply the pull request,similar what is
already done today, so no more work, and than by using the testing by who
ever want.
the pull request into stable becomes a noop, but is a last additional check.

there might be other possibilities for creating work flows that include
some QA without adding additional work to 1 person, eventually even reduce
it, including using the issue tracker an gitlab or github,
but I miss the time now to make an introduction into project management at
this time
and for SBo I would see this, or something similar, as a possibility that
maybe works  together with existing tools (just use a different branch)
Important is to be able to discuss such topics without getting passive
aggressive destructive comments, because I think we all want to use the
spare time we have productive.


/Harald





2017-01-21 11:33 GMT+01:00 David Spencer <baildon.research at googlemail.com>:

> > difference between sending a patch / pull request to a project that
> simply
> > apply it if it passes QA,
> >  difference between such workflows, and that one of SBo, where you need
> to
> > contact maintainer
>
> Perhaps you can help me, because it's not clear.
> Exactly who in this workflow is going to do QA?
>
> -D.
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20170121/408a0697/attachment-0001.html>