Majic Projects
Majic Ansible Roles
Go to the previous open issue
Go to the previous issue (open or closed)
star_faded.png
Please log in to bookmark issues
icon_project.png Majic Ansible Roles / Closed Feature request MAR-139 Switch to using stable branch nightly builds for Prosody in XMPP server role (backport to 2.0)
action_vote_minus_faded.png
0
Votes
 action_vote_plus_faded.png
Go to the next issue (open or closed)
Go to the next open issue
There are no more issues in that direction.
This issue has been closed with status "Closed" and resolution "RESOLVED".
Issue basics
  • Type of issue
    Feature request
  • Category
    Not determined
  • Targetted for
    2.0.1
  • Status
    Closed
  • Progress
  • Priority
    Not determined
User pain
  • Type of bug
    Not triaged
  • Likelihood
    Not triaged
  • Effect
    Not triaged
Affected by this issue (0)
There are no items
People involved
Times and dates
  • Posted at
  • Last updated
  • Estimated time
    4 hours
  • Time spent
    30 minutes
    Click here to see time logged against this issue
Issue details
  • Resolution
    RESOLVED
Attachments (0)
There is nothing attached to this issue
Duplicate issues (0)
This issue does not have any duplicates
Show / hide more details »
Description

Current implementation of the XMPP server role is using latest stable Prosody releases through Prosody project's own repository.

This is problematic because the version will get bumped from one minor release to next one, causing compatibility issues (see issue MAR-137 (Closed) for a good example).

Unfortunately, it would be better to switch to using nightly builds on the relevant stable branch instead. These are not official releases, however, but at the moment this seems to be the best way to go about solving future breakages. The nightly stable branch releases should still be good enough since they are supposed to receive only bug-fixes.

The following should be done:

  • Update the XMPP server role.
  • Switch to using the prosody-0.10 package as default (the nightly builds).
  • Make the package name configurable.
  • Update role reference documentation
  • Update release notes.

This is essentially a bug-fix because the current deployment of Prosody is broken in terms of LDAP integration.

Todos (0 / 0)
Options
There are no comments