"Fossies" - the Fresh Open Source Software Archive

Member "fail2ban-0.11.1/RELEASE" (11 Jan 2020, 6618 Bytes) of package /linux/misc/fail2ban-0.11.1.tar.gz:


As a special service "Fossies" has tried to format the requested text file into HTML format (style: standard) with prefixed line numbers. Alternatively you can here view or download the uninterpreted source code file.

    1 ..                       __      _ _ ___ _
    2                         / _|__ _(_) |_  ) |__  __ _ _ _
    3                        |  _/ _` | | |/ /| '_ \/ _` | ' \
    4                        |_| \__,_|_|_/___|_.__/\__,_|_||_|
    5 
    6 ================================================================================
    7 How to do a release for Fail2Ban
    8 ================================================================================
    9 
   10 Preparation
   11 ===========
   12 
   13 * Check distribution patches and see if they can be included
   14 
   15   * https://apps.fedoraproject.org/packages/fail2ban/sources
   16   * http://sources.gentoo.org/cgi-bin/viewvc.cgi/gentoo-x86/net-analyzer/fail2ban/
   17   * http://svnweb.freebsd.org/ports/head/security/py-fail2ban/
   18   * https://build.opensuse.org/package/show?package=fail2ban&project=openSUSE%3AFactory
   19   * http://sophie.zarb.org/sources/fail2ban (Mageia)
   20   * https://trac.macports.org/browser/trunk/dports/security/fail2ban
   21 
   22 
   23 * Check distribution outstanding bugs
   24 
   25   * https://github.com/fail2ban/fail2ban/issues?sort=updated&state=open
   26   * http://bugs.debian.org/cgi-bin/pkgreport.cgi?dist=unstable;package=fail2ban
   27   * https://bugs.launchpad.net/ubuntu/+source/fail2ban
   28   * http://bugs.sabayon.org/buglist.cgi?quicksearch=net-analyzer%2Ffail2ban
   29   * https://bugs.archlinux.org/?project=5&cat%5B%5D=33&string=fail2ban
   30   * https://bugs.gentoo.org/buglist.cgi?query_format=advanced&short_desc=fail2ban&bug_status=UNCONFIRMED&bug_status=CONFIRMED&bug_status=IN_PROGRESS&short_desc_type=allwords
   31   * https://bugzilla.redhat.com/buglist.cgi?query_format=advanced&bug_status=NEW&bug_status=ASSIGNED&component=fail2ban&classification=Red%20Hat&classification=Fedora
   32   * http://www.freebsd.org/cgi/query-pr-summary.cgi?text=fail2ban
   33   * https://bugs.mageia.org/buglist.cgi?quicksearch=fail2ban
   34   * https://build.opensuse.org/package/requests/openSUSE:Factory/fail2ban
   35 
   36 
   37 * Make sure the tests pass::
   38 
   39   ./fail2ban-testcases-all
   40 
   41 * Ensure the version is correct in:
   42 
   43   * ./fail2ban/version.py
   44   * top of ChangeLog
   45   * README.md
   46 
   47 
   48 * Ensure the MANIFEST is complete
   49 
   50   ad-hoc bash script to run in a clean clone:
   51 
   52      find -type f | grep -v -e '\.git' -e '/doc/' -e '\.travis' -e MANIFEST | sed -e 's,^\./,,g' | while read f; do grep -ne "^$f\$" MANIFEST >/dev/null || echo "$f" ; done
   53 
   54   or an alternative for comparison with previous release
   55 
   56      git diff 0.10.0 | grep -B2 'index 0000000..' | grep -B1 'new file mode' | sed -n -e '/^diff /s,.* b/,,gp' >> MANIFEST
   57      sort MANIFEST | uniq | sponge MANIFEST
   58 
   59 * Run::
   60 
   61   python setup.py sdist
   62 
   63 * Look for errors like::
   64 
   65    'testcases/files/logs/mysqld.log' not a regular file -- skipping
   66 
   67   * Which indicates that testcases/files/logs/mysqld.log has been moved or is a directory::
   68 
   69       tar -C /tmp -jxf dist/fail2ban-0.9.6.tar.bz2
   70 
   71 * clean up current directory::
   72 
   73     diff -rul --exclude \*.pyc . /tmp/fail2ban-0.10.0/
   74 
   75   * Only differences should be files that you don't want distributed.
   76 
   77 
   78 * Ensure the tests work from the tarball::
   79 
   80     cd /tmp/fail2ban-0.9.6/ && bin/fail2ban-testcases
   81 
   82 * Add/finalize the corresponding entry in the ChangeLog
   83 
   84   * To generate a list of committers use e.g.::
   85 
   86       git shortlog -sn 0.10.0.. | sed -e 's,^[ 0-9\t]*,,g' | tr '\n' '\|' | sed -e 's:|:, :g'
   87 
   88   * Ensure the top of the ChangeLog has the right version and current date.
   89   * Ensure the top entry of the ChangeLog has the right version and current date.
   90 
   91 * Update man pages::
   92 
   93     (cd man ; ./generate-man )
   94     git commit -m 'DOC/ENH: update man pages for release' man/*
   95 
   96 * Cleanout TODO file with the finished stuff
   97 
   98 * Prepare source and rpm binary distributions::
   99 
  100     python setup.py sdist
  101 
  102   * Broken for now:  python setup.py bdist_rpm
  103   * Broken for now:  python setup.py upload
  104 
  105 
  106 * Tag the release by using a signed (and annotated) tag.  Cut/paste
  107   release ChangeLog entry as tag annotation::
  108 
  109     git tag -s 0.10.0
  110 
  111 Pre Release
  112 ===========
  113 
  114 * Provide a release sample to distributors
  115 
  116   * Arch Linux:
  117 
  118     * https://www.archlinux.org/packages/community/any/fail2ban/
  119 
  120   * Debian: Yaroslav Halchenko <debian@onerussian.com>
  121 
  122     * http://packages.qa.debian.org/f/fail2ban.html
  123 
  124   * FreeBSD: Christoph Theis theis@gmx.at>
  125 
  126     * http://svnweb.freebsd.org/ports/head/security/py-fail2ban/Makefile?view=markup
  127     * http://www.freebsd.org/cgi/query-pr-summary.cgi?text=fail2ban
  128 
  129   * Fedora: Axel Thimm <Axel.Thimm@atrpms.net>
  130 
  131     * https://apps.fedoraproject.org/packages/fail2ban
  132     * http://pkgs.fedoraproject.org/cgit/fail2ban.git
  133     * https://admin.fedoraproject.org/pkgdb/acls/bugs/fail2ban
  134 
  135   * Gentoo: netmon@gentoo.org
  136 
  137     * http://sources.gentoo.org/cgi-bin/viewvc.cgi/gentoo-x86/net-analyzer/fail2ban/metadata.xml?view=markup
  138     * https://bugs.gentoo.org/buglist.cgi?quicksearch=fail2ban
  139 
  140   * openSUSE: Stephan Kulow <coolo@suse.com>
  141 
  142     * https://build.opensuse.org/package/show/openSUSE:Factory/fail2ban
  143 
  144   * Mac Ports: @Malbrouck on github (gh-49)
  145 
  146     * https://trac.macports.org/browser/trunk/dports/security/fail2ban/Portfile
  147 
  148   * Mageia:
  149 
  150     * https://bugs.mageia.org/buglist.cgi?quicksearch=fail2ban
  151 
  152   * And potentially to the fail2ban-users email list.
  153 
  154 
  155 * Wait for feedback from distributors
  156 
  157 * Prepare a release notice https://github.com/fail2ban/fail2ban/releases/new
  158 
  159 * Upload the source/binaries from the dist directory and tag the release using the URL
  160 
  161 * Upload source/binaries to sourceforge http://sourceforge.net/projects/fail2ban/
  162 
  163 * Run the following and update the wiki with output::
  164 
  165     python -c 'import fail2ban.protocol; fail2ban.protocol.printWiki()'
  166 
  167   * page: http://www.fail2ban.org/wiki/index.php/Commands
  168 
  169 
  170 * Update:
  171 
  172   * http://www.fail2ban.org/wiki/index.php?title=Template:Fail2ban_Versions&action=edit
  173 
  174   * http://www.fail2ban.org/wiki/index.php?title=Template:Fail2ban_News&action=edit
  175     * move old bits to http://www.fail2ban.org/wiki/index.php?title=Template:Fail2ban_OldNews&action=edit
  176 
  177   * http://www.fail2ban.org/wiki/index.php/ChangeLog
  178   * http://www.fail2ban.org/wiki/index.php/Requirements (Check requirement)
  179   * http://www.fail2ban.org/wiki/index.php/Features
  180 
  181 * See if any filters are upgraded:
  182   http://www.fail2ban.org/wiki/index.php/Special:AllPages
  183 
  184 * Email users and development list of release
  185 
  186 * notify distributors
  187 
  188 Post Release
  189 ============
  190 
  191 Add the following to the top of the ChangeLog::
  192 
  193   ver. 0.10.0 (2016/XX/XXX) - wanna-be-released
  194   -----------
  195   
  196   ### Fixes
  197   
  198   ### New Features
  199   
  200   ### Enhancements
  201 
  202 Alter the git shortlog command in the previous section to refer to the just
  203 released version.
  204 
  205 and adjust fail2ban/version.py to carry .dev0 suffix to signal
  206 a version under development.