HackMD
  • Prime
    Prime  Full-text search on all paid plans
    Search anywhere and reach everything in a Workspace with Prime plan.
    Got it
      • Create new note
      • Create a note from template
    • Prime  Full-text search on all paid plans
      Prime  Full-text search on all paid plans
      Search anywhere and reach everything in a Workspace with Prime plan.
      Got it
      • Options
      • Versions and GitHub Sync
      • Transfer ownership
      • Delete this note
      • Template
      • Save as template
      • Insert from template
      • Export
      • Dropbox
      • Google Drive
      • Gist
      • Import
      • Dropbox
      • Google Drive
      • Gist
      • Clipboard
      • Download
      • Markdown
      • HTML
      • Raw HTML
      • Sharing Link copied
      • /edit
      • View mode
        • Edit mode
        • View mode
        • Book mode
        • Slide mode
        Edit mode View mode Book mode Slide mode
      • Note Permission
      • Read
        • Owners
        • Signed-in users
        • Everyone
        Owners Signed-in users Everyone
      • Write
        • Owners
        • Signed-in users
        • Everyone
        Owners Signed-in users Everyone
      • More (Comment, Invitee)
      • Publishing
        Everyone on the web can find and read all notes of this public team.
        After the note is published, everyone on the web can find and read this note.
        See all published notes on profile page.
      • Commenting Enable
        Disabled Forbidden Owners Signed-in users Everyone
      • Permission
        • Forbidden
        • Owners
        • Signed-in users
        • Everyone
      • Invitee
      • No invitee
    Menu Sharing Create Help
    Create Create new note Create a note from template
    Menu
    Options
    Versions and GitHub Sync Transfer ownership Delete this note
    Export
    Dropbox Google Drive Gist
    Import
    Dropbox Google Drive Gist Clipboard
    Download
    Markdown HTML Raw HTML
    Back
    Sharing
    Sharing Link copied
    /edit
    View mode
    • Edit mode
    • View mode
    • Book mode
    • Slide mode
    Edit mode View mode Book mode Slide mode
    Note Permission
    Read
    Owners
    • Owners
    • Signed-in users
    • Everyone
    Owners Signed-in users Everyone
    Write
    Owners
    • Owners
    • Signed-in users
    • Everyone
    Owners Signed-in users Everyone
    More (Comment, Invitee)
    Publishing
    Everyone on the web can find and read all notes of this public team.
    After the note is published, everyone on the web can find and read this note.
    See all published notes on profile page.
    More (Comment, Invitee)
    Commenting Enable
    Disabled Forbidden Owners Signed-in users Everyone
    Permission
    Owners
    • Forbidden
    • Owners
    • Signed-in users
    • Everyone
    Invitee
    No invitee
       owned this note    owned this note      
    Published Linked with GitHub
    Like1 BookmarkBookmarked
    Subscribed
    • Any changes
      Be notified of any changes
    • Mention me
      Be notified of mention me
    • Unsubscribe
    Subscribe
    # Community package: To LTS or not to LTS ## Context Before Ansible 2.10, the project typically maintained N, N-1 for bug fixes and N-2 for security fixes, for example ([here](https://github.com/ansible/ansible/blob/0b4b832f9cbab4246ec9aab7bd36c0447e04549d/docs/docsite/rst/reference_appendices/release_and_maintenance.rst)): ![release-and-maintenance](https://i.imgur.com/GUeOeyN.png) When Ansible 3.0.0 released, we suggested that we would no longer ship updated releases for 2.10.x unless someone needed it or showed up to do the work. Unless mistaken, we have not seen interest from the community so far in pursuing updates for 2.10.x. This document seeks to write down what are the implications of maintaining updates for 3.x once 4.x releases and how we might continue maintaining 4.x once 5.x releases and so on. ## About the ``ansible`` package on PyPi Before delving into the details, some basics about the package so we are on the same wavelength: - It's a package that depends on the latest version of ansible-core at the time of the initial release (i.e, ``ansible-core>=2.11,<2.12``) - It's a package that includes a selected [list of over 85 collections](https://github.com/ansible-community/ansible-build-data/blob/main/3/ansible.in) and ships their [latest minor versions](https://github.com/ansible-community/ansible-build-data/blob/main/3/ansible-3.build) - After Ansible 4.0.0, it will have major releases every 6 months (5.0.0, 6.0.0, and so on) - It has minor releases every 3 weeks (3.1.0, 3.2.0, 3.3.0 and so on) ## The use case for maintaining the ``ansible`` package Broadly speaking, maintaining the Ansible community package means allowing the included collections to be updated independently of ansible-core, adding new backwards-compatible features and security/bug fixes. This is simple and convenient for users who privilege or otherwise prefer the "batteries included" approach of installing one package and getting all the modules and plugins. Another appeal of the community package is to continue getting updates while limiting exposure to major and breaking changes by way of semantic versioning for the included collections as well as the package itself. Users who want increased control over their installation might opt for ``ansible-core`` instead and then cherry-pick the collections they want from galaxy or elsewhere. These users can get updates for collections that are otherwise included in the ``ansible`` package "out-of-band" by controlling which versions they download from galaxy. ## What it means to maintain N and N-1 There are benefits to continue maintaining 3.x once 4.x is released: - It would allow users to continue getting updates for a time while they prepare to upgrade - It would be consistent with how Ansible has historically maintained /at least/ N and N-1 - Included collections can continue shipping fixes by backporting to stable branches if they have such a mechanism in place In practice, maintaining past major releases is not without questions and challenges that should be addressed in order to move forward: - Not every collection has the concept of stable branches to which they continue backporting fixes: how to manage user expectations vs unfixed bugs and security issues ? - What kind of burden does this place on the community and the collection maintainers ? - Even considering improved automation and testing of the release process, who will do the work ? - Would we continue shipping a minor release every three weeks ? ## What it means to not maintain N-1 If we no longer maintain 3.x once 4.x is out, it can play out in one of two ways: 1) While users will continue getting minor updates for ansible-core (due to pinning such as ``>=2.11,<2.12``), they will no longer receive updates for included collections. We would encourage users to upgrade to 4.x ASAP to benefit from bug and security fixes in spite of potential major/breaking changes. 2) We encourage users to use ``ansible-core`` and cherry-pick the collection versions they want. This shifts the burden of maintenance to the user while allowing them to continue receiving the updates they care about. ## Expectations and considerations for downstream users Our decision is not without impact for downstream consumers of the package like Linux distributions who have release and maintenance cycles that far exceed 6 months. For example, the latest Debian stable still has Ansible 2.7.7. ## In summary There are benefits to a longer maintenance cycle and while we are open to the idea, it is a non-negligible amount of work without even considering the implications of patching collections that do not backport bug and security fixes. Maintaining a single major version of the `ansible` package for six months while providing the ability to install and update collections out-of-band leveraging `ansible-core` and `ansible-galaxy` is likely a good middle ground until the need for a longer maintenance cycle is voiced by the wider community.

    Import from clipboard

    Advanced permission required

    Your current role can only read. Ask the system administrator to acquire write and comment permission.

    This team is disabled

    Sorry, this team is disabled. You can't edit this note.

    This note is locked

    Sorry, only owner can edit this note.

    Reach the limit

    Sorry, you've reached the max length this note can be.
    Please reduce the content or divide it to more notes, thank you!

    Import from Gist

    Import from Snippet

    or

    Export to Snippet

    Are you sure?

    Do you really want to delete this note?
    All users will lost their connection.

    Create a note from template

    Create a note from template

    Oops...
    This template is not available.


    Upgrade

    All
    • All
    • Team
    No template found.

    Create custom template


    Upgrade

    Delete template

    Do you really want to delete this template?

    This page need refresh

    You have an incompatible client version.
    Refresh to update.
    New version available!
    See releases notes here
    Refresh to enjoy new features.
    Your user state has changed.
    Refresh to load new user state.

    Sign in

    Forgot password

    or

    By clicking below, you agree to our terms of service.

    Sign in via Facebook Sign in via Twitter Sign in via GitHub Sign in via Dropbox Sign in via Google

    New to HackMD? Sign up

    Help

    • English
    • 中文
    • Français
    • Deutsch
    • 日本語
    • Español
    • Català
    • Ελληνικά
    • Português
    • italiano
    • Türkçe
    • Русский
    • Nederlands
    • hrvatski jezik
    • język polski
    • Українська
    • हिन्दी
    • svenska
    • Esperanto
    • dansk

    Documents

    Tutorials

    Book Mode Tutorial

    Slide Mode Tutorial

    YAML Metadata

    Contacts

    Facebook

    Twitter

    Feedback

    Send us email

    Resources

    Releases

    Pricing

    Blog

    Policy

    Terms

    Privacy

    Cheatsheet

    Syntax Example Reference
    # Header Header 基本排版
    - Unordered List
    • Unordered List
    1. Ordered List
    1. Ordered List
    - [ ] Todo List
    • Todo List
    > Blockquote
    Blockquote
    **Bold font** Bold font
    *Italics font* Italics font
    ~~Strikethrough~~ Strikethrough
    19^th^ 19th
    H~2~O H2O
    ++Inserted text++ Inserted text
    ==Marked text== Marked text
    [link text](https:// "title") Link
    ![image alt](https:// "title") Image
    `Code` Code 在筆記中貼入程式碼
    ```javascript
    var i = 0;
    ```
    var i = 0;
    :smile: :smile: Emoji list
    {%youtube youtube_id %} Externals
    $L^aT_eX$ LaTeX
    :::info
    This is a alert area.
    :::

    This is a alert area.

    Versions

    Versions and GitHub Sync

    Sign in to link this note to GitHub Learn more
    This note is not linked with GitHub Learn more
     
    Add badge Pull Push GitHub Link Settings
    Upgrade now

    Version named by    

    More Less
    • Edit
    • Delete

    Note content is identical to the latest version.
    Compare with
      Choose a version
      No search result
      Version not found

    Feedback

    Submission failed, please try again

    Thanks for your support.

    On a scale of 0-10, how likely is it that you would recommend HackMD to your friends, family or business associates?

    Please give us some advice and help us improve HackMD.

     

    Thanks for your feedback

    Remove version name

    Do you want to remove this version name and description?

    Transfer ownership

    Transfer to
      Warning: is a public team. If you transfer note to this team, everyone on the web can find and read this note.

        Link with GitHub

        Please authorize HackMD on GitHub

        Please sign in to GitHub and install the HackMD app on your GitHub repo. Learn more

         Sign in to GitHub

        HackMD links with GitHub through a GitHub App. You can choose which repo to install our App.

        Push the note to GitHub Push to GitHub Pull a file from GitHub

          Authorize again
         

        Choose which file to push to

        Select repo
        Refresh Authorize more repos
        Select branch
        Select file
        Select branch
        Choose version(s) to push
        • Save a new version and push
        • Choose from existing versions
        Available push count

        Upgrade

        Pull from GitHub

         
        File from GitHub
        File from HackMD

        GitHub Link Settings

        File linked

        Linked by
        File path
        Last synced branch
        Available push count

        Upgrade

        Danger Zone

        Unlink
        You will no longer receive notification when GitHub file changes after unlink.

        Syncing

        Push failed

        Push successfully