Bug 7837 - Revise masscheck so that it can operate on a pull from a branch when desired
Summary: Revise masscheck so that it can operate on a pull from a branch when desired
Status: NEW
Alias: None
Product: Spamassassin
Classification: Unclassified
Component: RuleQA (show other bugs)
Version: unspecified
Hardware: All All
: P2 enhancement
Target Milestone: Undefined
Assignee: SpamAssassin Developer Mailing List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-07-10 08:04 UTC by Loren Wilton
Modified: 2020-07-10 20:49 UTC (History)
2 users (show)


Attachment Type Modified Status Actions Submitter/CLA Status
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Loren Wilton 2020-07-10 08:04:00 UTC 
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.
Comment 1 Kevin A. McGrail 2020-07-10 08:36:39 UTC 
Recommend you join the list for SpamAssassin Sysadmins <sysadmins@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.
Comment 2 jidanni 2020-07-10 20:45:32 UTC 
Hmm, GitHub has something related,
https://docs.github.com/en/github/administering-a-repository/about-required-status-checks
Comment 3 Kevin A. McGrail 2020-07-10 20:49:02 UTC 
(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?