Code Monkey home page Code Monkey logo

Comments (6)

drAlberT avatar drAlberT commented on July 20, 2024

Just to clarify, on GitHub I mean ..

from docker-nagios.

JasonRivers avatar JasonRivers commented on July 20, 2024

I actually switched to branches for this, Branches mean that if there's a problem it can be fixed, but perhaps creating a tag/release at that branch is a good way of doing it.

from docker-nagios.

drAlberT avatar drAlberT commented on July 20, 2024

yep :) branches and tags/releases are complementary 👍

from docker-nagios.

drAlberT avatar drAlberT commented on July 20, 2024

Anyway .. I think you are adopting a too expensive model to handle the code

My suggestion is to have only a few branches (master, version X, version Y) in which you do:

  • development
  • maintain X.x.x releases
  • maintain Y.y.y releases

You can add (only if and when requested) additional X.Z.z branches . in case you want to support that particular minor release releasing patches for it but, in general you would only maintain a few main branches, tagging on it the releases.

Everytime you release a new patch (in the semver meaning) you drop a new release (tagging it)

example:

  • master -> development of the latest features
  • branch 4.x -> stable branch for version 4.x.x (it requires php 7.x)
  • branche 3.x -> stable branch for version 3.x.x (it requires and supports php 5.x)

Hope to had been clear .. hope to not be boring or annoying too ;)

from docker-nagios.

JasonRivers avatar JasonRivers commented on July 20, 2024

You are probably right, The reason for having docker hub builds of the version (as either a branch or a tag) was for the users that don't want to upgrade to the latest version all the time "just in case".

I probably won't ever maintain a Nagios3, the reason I created this image was that everything I found at the time was either Nagios3 or didn't really work, But I will probably continue to maintain "the latest nagios4" when Nagios 5 drops, at least for a while.

Overall, it doesn't actually take a lot of maintenance, Both dockerhub and Travis build when I commit and tell me when I'm being a muppet, and I generally build and deploy to a test environment before committing to master.

I haven't committed to any of versioned branches for a while, I can probably just create tags for those now, and as you say, maintain a 4.x branch instead.

Thanks for your input.

from docker-nagios.

drAlberT avatar drAlberT commented on July 20, 2024

from docker-nagios.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.