Skip to content

politeia v1.2.0

Compare
Choose a tag to compare
@lukebp lukebp released this 27 Sep 15:34
· 122 commits to master since this release
29e31d9

This release includes the following feature additions, bug fixes and
improvements.

  • Proposal author updates (#1491).
    Proposal authors are now able to give updates on the status of their
    proposal. Once the proposal is approved, the author can can start new comment
    threads that server as update threads until the proposal has been marked as
    closed or completed by an admin.

  • Proposal billing statuses (#1480).
    Billing statuses (active, closed, completed) have been added to proposals.
    Once a proposal has been approved, the billing status is considered to be
    active. Admins can mark the billing status of a proposal as completed or
    closed in order to prevent further billing against the proposal. The
    completed billing status indicates the proposal has successfully delivered
    all promised work and is no longer being billed against. The closed billing
    status means that the proposal work has not been fully delivered, but further
    billing against the proposal is no longer allowed. These billing statuses
    will allow CMS, Decred's contractor management system, to further automate
    the Decred treasury billing process.

  • Proposal statuses (#1515).
    A proposal status type has been added to the pi plugin that is used to map
    all possible paths a proposal can take throughout its lifecycle. This status
    is determined at runtime by combining the metadata from the various plugins
    (record status changes, vote status changes, billing status changes, etc).
    This status removes complexity from the client and serves as the source of
    truth for how the various plugin metadata impacts a proposal.

  • OOM hardening.
    The Politeia servers have experienced a few "out of memory" errors since the
    last release. This was due to the combination of a memory leak in politeiad
    and a server config that was too restrictive with regards to allowed memory
    usage of the politeiad process. These issues have been fixed and additional
    measures have been implemented in order to increase the security and
    stability of the Politeia servers. (#1500) (#1505) (#1506) (#1507)

Note: In order to enable proposal author updates, the following plugin
setting must be added to the politeiad config file.

pluginsetting=comments,allowextradata,true

Changelog

This release consists of 26 commits from 7 contributors which totals to 81
files changed, 4,350 additional lines of code and 1,237 deleted lines of code.

multi: Add billing statuses. (#1480)
politeiawww: Add missing code blocks to README. (#1489)
docs: Add v1.1.0 release notes. (#1486)
politeiavoter: Update prompt pass placement. (#1490)
comments: Update signature and settings. (#1487)
Bump to Go 1.17. (#1492)
pictl: Improve human readable dollar printing. (#1488)
multi: Add proposal author updates. (#1491)
records: Add missing error return. (#1496)
multi: Document exported names. (#1497)
Add SECURITY.md file. (#1495)
pictl: cmdVoteStart help message typo. (#1498)
store: Close deblob reader. (#1500)
mysql: fix u_blub user table column bug. (#1499)
records: Fix SetStatusReply wrong username bug. (#1509)
politeiawww: Add server read limits. (#1506)
politeiad: Cleanup middleware. (#1507)
pictl: Add save as csv option to vote results. (#1478)
multi: Add read/write constraints to servers. (#1505)
politeiad: Setup fscks. (#1512)
politeiad: Remove politeiaimport tool. (#1513)
multi: Remove testpoliteiad package. (#1514)
docs: Add plugin overview. (#1519)
pi: Add proposal statuses. (#1515)
politeiawww: Add page sizes to policy replies. (#1518)
pi: Fix typo in Summary.Status field json key. (#1522)

Code Contributors (alphabetical order)

  • Amir Massarwa (amass01)
  • Đàm Việt Anh (vibros68)
  • David Hill (dajohi)
  • Degeri (degeri)
  • Luke Powell (lukebp)
  • Thiago F. Figueiredo (thi4go)
  • Victor Guedes (victorgcramos)