You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@spamassassin.apache.org by bu...@spamassassin.apache.org on 2020/07/10 08:04:00 UTC
[Bug 7837] New: Revise masscheck so that it can operate on a pull
from a branch when desired
https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7837
Bug ID: 7837
Summary: Revise masscheck so that it can operate on a pull from
a branch when desired
Product: Spamassassin
Version: unspecified
Hardware: All
OS: All
Status: NEW
Severity: enhancement
Priority: P2
Component: spamassassin
Assignee: dev@spamassassin.apache.org
Reporter: lwilton@earthlink.net
Target Milestone: Undefined
Rationale: Currently a divisive and fragile sequence of patches are intended
for the trunk of SA and various components. Many requests have been made by
several people that these be carried out in a branch where the changes can be
tested by the committer rather than the general community at large. This is
described as not possible as "masscheck only works on trunk".
Solution: Change masscheck so it can be run on a specified branch when desired.
Discussion: This will allow a cohesive whole made of a long sequence of fragile
individual patches to be developed in an environment that will not affect
general development, SA users that use trunk, 3rd party developers, and others.
Exposing them to the trials and tribulations of probable constant project
breakage as small tightly inter-woven patches are committed without sufficient
testing (in the name of being able to generate that testing) is not desirable,
when the alternative would be adding a parameter to the masscheck scripts to
allow a pull and test from a specified branch.
--
You are receiving this mail because:
You are the assignee for the bug.
[Bug 7837] Revise masscheck so that it can operate on a pull from a
branch when desired
Posted by bu...@spamassassin.apache.org.
https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7837
--- Comment #3 from Kevin A. McGrail <km...@apache.org> ---
(In reply to jidanni from comment #2)
> Hmm, GitHub has something related,
> https://docs.github.com/en/github/administering-a-repository/about-required-
> status-checks
Are you volunteering to help with re-engineering masscheck, etc. over to a GH
back-end?
--
You are receiving this mail because:
You are the assignee for the bug.
[Bug 7837] Revise masscheck so that it can operate on a pull from a
branch when desired
Posted by bu...@spamassassin.apache.org.
https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7837
jidanni@jidanni.org changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jidanni@jidanni.org
--- Comment #2 from jidanni@jidanni.org ---
Hmm, GitHub has something related,
https://docs.github.com/en/github/administering-a-repository/about-required-status-checks
--
You are receiving this mail because:
You are the assignee for the bug.
[Bug 7837] Revise masscheck so that it can operate on a pull from a
branch when desired
Posted by bu...@spamassassin.apache.org.
https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7837
Kevin A. McGrail <km...@apache.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |kmcgrail@apache.org
Component|spamassassin |RuleQA
--- Comment #1 from Kevin A. McGrail <km...@apache.org> ---
Recommend you join the list for SpamAssassin Sysadmins
<sy...@spamassassin.apache.org> and volunteer to help with this goal. See
https://cwiki.apache.org/confluence/display/SPAMASSASSIN/InfraNotes2017 for
more information about the back-end.
Rules are only created in one branch (whether that is a branch or trunk) so you
have to solve that issue as well. There are discussions on the mailing list
about that issue right now.
There is currently an endeavor to change our backend to a new server
(https://issues.apache.org/jira/browse/INFRA-20449) so now would be a good time
to volunteer on this project.
Beyond that, I will state that trunk is a development branch currently in
standard C-T-R mode. Development branches by their very nature are unstable,
bleeding edge code. If you need stability, stick to released copies.
--
You are receiving this mail because:
You are the assignee for the bug.