[Nut-upsdev] Roadmap to 2.7.3
arnaud.quette at gmail.com
Thu Mar 19 18:00:15 UTC 2015
Hi Charles and the list,
a complementary update...
2015-03-16 13:46 GMT+01:00 Charles Lepple <clepple at gmail.com>:
> On Mar 4, 2015, at 9:04 AM, Charles Lepple 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 <
> > * #158: Powerware BCMXCP advanced features <
> > * #185: insecure storage of password in nut-monitor favorites file <
> > * #187: Wrong in/out voltage repported for PowerCom KIN2200APRM <
> > * #190: upsd: NSS SSL only working in debug mode <
> > * eaton_epdus branch: <
> > Most of these are from the GitHub 2.7.3 milestone:
> A quick status update:
> * #93: most of the DDL stuff is merged; anything else can wait for 2.7.4.
> * #158: the branch has been collapsed into one commit, but additional
> documentation (nut-names.txt) is needed:
branch updated for nut-names.txt + few minor updates.
I've also rebased on master, but will need another round (following the 2
branches pushed below)
I'm still lagging behind the HW tests, so if you can, let's move on...
otherwise, I'll do, but not today.
I'll check whenever possible, but Igor's feedback seems good to me, until
proven the opposite.
Note that I've added an issue to track battery.charger.status needed
* #185: merged
> * #187: no update from original comment: "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?"
if it can be addressed quickly, maybe. Otherwise, for 2.7.4...
> * #190: no update on NSS SSL bug. Since it fails safe, I am willing to
> document around it (foreground hack). Has anyone else had a chance to look
> at it?
sadly, no, not yet. Still head underwater, as you can see...
> * eaton_epdus branch: Arnaud, you may need to refresh my memory on what
> there the latest code is (pushed to same branch, or another issue?), and
> what needs to be agreed upon for the new names?
I pushed to the same branch and documented the new vars: input.*.load,
input.*.realpower and input.*.power
No much need for a hard agreement, more for info...
I've rebased and pushed this branch to master.
I've also fixed the eaton-energysave branch as per the names pushed in in
Note that I've proposed and made an addition for
Just rebased and merged the branch few minutes ago.
The rest is good to me too.
So is everything good to go from your PoV Charles?
thanks for this update and all your work, as usual Charles!
Eaton Data Center Automation - Opensource Leader
NUT (Network UPS Tools) Project Leader - http://www.networkupstools.org
Debian Developer - http://www.debian.org
Free Software Developer - http://arnaud.quette.fr
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Nut-upsdev