On 17.01.2014 18:21, Mark Haney wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 1/16/2014 4:13 PM, Michael Friedrich wrote:
I didn't see if there was a temporary work around for 0.0.6, not
that it matters.
While the Icinga 2 releases happen on a 3 weeks schedule for our
development sprints, this is not true for holiday season. That's
mainly the reason why there isn't 0.0.7 already. But as a matter of
fact you should use the snapshot package repository, even that may
sound odd.
Our development model is git flow, and features are developed in
feature branches until they're considered stable. Fixes also last a
while in fix branches, and are only merged without --no-ff *if*
they are quickfixes. In general that means that 'git next' as a
base for snapshot package builds on every push is more fixed stable
than the master only representing the last tech preview release.
I'm all for opening bug reports, however, I always try to hit the
lists to see if I've done something wrong before I go throwing bug
reports in. I'm much more likely to have screwed something up rather
than finding a bug.
That's fine and also one of those reasons I regularly check my mails for
this list. Though, I tend to bulk-answer every week or so, unless i
consider it a critical issue - Icinga is very time consuming for all the
parts i like to do in and with it.
Therefore, other colleagues may step into, and if you feel yourself and
the bug unheard, creating an issue on dev.icinga.org will notify all
involved developers, even those not checking their mailinglist archive
;) (that's _not_ the call to create issues for every small problem!)
As far as using the snapshot builds, I game. But what's the
preferred/best method of doing so? Simply adding the snapshot repo
package? (And disabling the stable repo.)
Yep. They do not depend on each other (that means, boost is shipped in
both repos for SLES11). The only notable difference in regards of the
package name is the additional 'snapshot-<timestamp>' suffix but that
will only help to identify the version installed in case of a found bug.
The easiest way is running
icinga2 --version
though. The Icinga 2 buildsystem will add the git revision to the
version tag already.
Kind regards,
Michael
--
DI (FH) Michael Friedrich
mail: michael.friedr...@gmail.com
twitter: https://twitter.com/dnsmichi
jabber: dnsmi...@jabber.ccc.de
irc: irc.freenode.net/icinga dnsmichi
icinga open source monitoring
position: lead core developer
url: https://www.icinga.org
_______________________________________________
icinga-users mailing list
icinga-users@lists.icinga.org
https://lists.icinga.org/mailman/listinfo/icinga-users
