On Tue, Apr 7, 2015 at 7:08 PM, David S Hustace <da...@opennms.org> wrote:
> Have decided whether to make each new Horizon release (16, 17, 18, etc.) an
> upgrade or an update? My position is that:
>
> # yum update opennms
>
> should not move from 15.0.2 to 16.
I don't think yum is that smart unless you change the package name and
obsolete the old one. Otherwise update and upgrade usually do the
same thing. Unless you are talking about the separate stable/unstable
repositories - I thought you were getting away from that.
Anyway, from anyone else's perspective it is a question of how many
incompatibilities you are going to throw at us at once.
--
Les Mikesell
lesmikes...@gmail.com
------------------------------------------------------------------------------
BPM Camp - Free Virtual Workshop May 6th at 10am PDT/1PM EDT
Develop your own process in accordance with the BPMN 2 standard
Learn Process modeling best practices with Bonita BPM through live exercises
http://www.bonitasoft.com/be-part-of-it/events/bpm-camp-virtual- event?utm_
source=Sourceforge_BPM_Camp_5_6_15&utm_medium=email&utm_campaign=VA_SF
_______________________________________________
Please read the OpenNMS Mailing List FAQ:
http://www.opennms.org/index.php/Mailing_List_FAQ
opennms-devel mailing list
To *unsubscribe* or change your subscription options, see the bottom of this
page:
https://lists.sourceforge.net/lists/listinfo/opennms-devel
