[Nut-upsdev] Roadmap to 2.7.3

[Baruch Even]

Hi,

There is one issue that I would consider as a major issue and not fixed
yet. It is the use of wall time for scheduling ups polls instead of a
monotonic clock source. I provided a (partial) patch in the past and I
believe there was some work on it.

The bug manifests itself as a stop of monitoring with no alarm when the
clock is moved backwards in time.

Please consider adding this to the release.

Cheers,
Baruch

On Wed, Mar 4, 2015 at 4:04 PM, Charles Lepple <clepple at gmail.com> wrote:

> We only have a few open items that I think should be resolved before
> releasing 2.7.3. The list grew a bit in the past week, but we'll cover that
> later. Here is the list:
>
>  * #93: Devices Dumps Library improvements <
> https://github.com/networkupstools/nut/issues/93>
>  * #158: Powerware BCMXCP advanced features <
> https://github.com/networkupstools/nut/pull/158>
>  * #185: insecure storage of password in nut-monitor favorites file <
> https://github.com/networkupstools/nut/issues/185>
>  * #187: Wrong in/out voltage repported for PowerCom KIN2200APRM <
> https://github.com/networkupstools/nut/issues/187>
>  * #190: upsd: NSS SSL only working in debug mode <
> https://github.com/networkupstools/nut/issues/190>
>  * eaton_epdus branch: <
> https://github.com/networkupstools/nut/tree/eaton-epdus>
>
> Most of these are from the GitHub 2.7.3 milestone:
> https://github.com/networkupstools/nut/issues?q=milestone%3A2.7.3
>
> #93: The scope of this issue is a bit broad (encompassing a Gen3 dummy-ups
> driver, etc) but for 2.7.3, I think we can call this closed, so long as
> there are no issues pushing this to www.networkupstools.org. The current
> auto-generated DDL is here:
> http://buildbot.networkupstools.org/~buildbot/cayman/docs/latest/ddl/
>
> #158: I will rebase the commits, and replace the author's email address
> with the GitHub username at noreply address, but if someone has additional
> Powerware-based UPSes to test, that would be handy.
>
> #185: Debian patch is on a branch; I will bump the version number and
> merge.
>
> #187: This is a driver-specfic fix, but I haven't had time to work through
> the logic from the vendor driver. This is not listed on the GitHub 2.7.3
> milestone - should it be?
>
> #190 is a bit more complicated. We are still in the initial investigation
> stage, but it seems that this may have crept past the Ubuntu automated test
> suite. Running in the foreground is a bit of an ugly hack, but if it works
> with the Ubuntu init scripts...
>
> I'll let Arno cover the eaton_epdus branch. Also driver-specific
> (snmp-ups), so should not affect the rest of NUT. (Is this the same as
> issue #188? <https://github.com/networkupstools/nut/issues/188> )
>
> Glad to hear that Arno will have more time to work on NUT again!
>
> --
> Charles Lepple
> clepple at gmail
>
>
>
>
> _______________________________________________
> Nut-upsdev mailing list
> Nut-upsdev at lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsdev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.alioth.debian.org/pipermail/nut-upsdev/attachments/20150305/77c3aefc/attachment.html>