|
SA Bugzilla – Full Text Bug Listing |
Summary: | Revise masscheck so that it can operate on a pull from a branch when desired | ||
---|---|---|---|
Product: | Spamassassin | Reporter: | Loren Wilton <lwilton> |
Component: | RuleQA | Assignee: | SpamAssassin Developer Mailing List <dev> |
Status: | NEW --- | ||
Severity: | enhancement | CC: | jidanni, kmcgrail |
Priority: | P2 | ||
Version: | unspecified | ||
Target Milestone: | Undefined | ||
Hardware: | All | ||
OS: | All | ||
Whiteboard: |
Description
Loren Wilton
2020-07-10 08:04:00 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. Hmm, GitHub has something related, https://docs.github.com/en/github/administering-a-repository/about-required-status-checks (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? |