[Ipmitool-devel] ipmitool 1.8.13 release

Discussion:

Jim Mankovich

2013-08-06 16:14:32 UTC

All,
I would like to start the 1.8.13 release process this week. Are there
any pending changes that you feel I should wait for before creating the
first release candidate tar bundle?

Thanks in Advance,
Jim

--
--- Jim Mankovich | ***@hp.com (US Mountain Time) ---

Zdenek Styblik

2013-08-06 17:57:22 UTC

Permalink

Post by Jim Mankovich
All,
I would like to start the 1.8.13 release process this week. Are there
any pending changes that you feel I should wait for before creating the
first release candidate tar bundle?
Thanks in Advance,
Jim
--

Jim,

I have two things to fix before 1.8.13 is released, but I don't feel
like creation of RC should be put on hold because of these.
One is pretty much just a commit, the other one is, I have to admit,
more complicated than that,

Regards,
Z.

Post by Jim Mankovich
------------------------------------------------------------------------------
Get 100% visibility into Java/.NET code with AppDynamics Lite!
It's a free troubleshooting tool designed for production.
Get down to code-level detail for bottlenecks, with <2% overhead.
Download for free and get started troubleshooting in minutes.
http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.clktrk
_______________________________________________
Ipmitool-devel mailing list
https://lists.sourceforge.net/lists/listinfo/ipmitool-devel

Dan Gora

2013-08-06 18:16:46 UTC

Permalink

As for me, I'd like to try and get the changes to be able to remove
the -Wno-unused-return flag from the Makefile since that breaks
builds. There are several patches pending to be merged for that (ID
65: Fixes for configure.in for cross compilation).

I also have two patches for ipmi_picmg.c that I'd like to try and get
in if possible. One is to change atoi to use the str2* and a small
one to fix up the help message for 'ipmitool picmg policy set'. I
haven't submitted those yet, but I was going to today.

Also Dmitry has some good looking changes for ipmi_hpmfwupg.c that he
submitted yesterday, but I don't think that they apply cleanly to the
CVS root. I don't know if he has any plans to try and fix those up or
not, but it would probably be nice to have.

Do we have any kind of hard time limits to get a release out? I too
would like to get a release sooner than later, but the more fixes we
can get into this release, the better IMO...

thanks
dan

Post by Zdenek Styblik

Jim,
I have two things to fix before 1.8.13 is released, but I don't feel
like creation of RC should be put on hold because of these.
One is pretty much just a commit, the other one is, I have to admit,
more complicated than that,
Regards,
Z.

Zdenek Styblik

2013-08-06 18:32:55 UTC

Permalink

Post by Dan Gora
As for me, I'd like to try and get the changes to be able to remove
the -Wno-unused-return flag from the Makefile since that breaks
builds. There are several patches pending to be merged for that (ID
65: Fixes for configure.in for cross compilation).

Stupid me. I forgot about these. However, we're talking about RC not release.

Post by Dan Gora
I also have two patches for ipmi_picmg.c that I'd like to try and get
in if possible. One is to change atoi to use the str2*

Huh? Where? I see no atoi() in ipmi_picmg.c. However, I see one atoi()
in ipmi_hpmfwupg.c which has slipped through. How's that even
possible, garrr!

Post by Dan Gora
and a small
one to fix up the help message for 'ipmitool picmg policy set'. I
haven't submitted those yet, but I was going to today.

Is it really crucial to get it into 1.8.13?

Post by Dan Gora
Also Dmitry has some good looking changes for ipmi_hpmfwupg.c that he
submitted yesterday, but I don't think that they apply cleanly to the
CVS root. I don't know if he has any plans to try and fix those up or
not, but it would probably be nice to have.

Again, same question. We have 1.8.12 for a year now; we know 1.8.13 is
going to be released for some time now, yet out of the blue new fixes,
very important no doubt, start rolling as the date comes closer.
I know I'm being sarcastic, I know I'm raining on the parade, I'm
sorry(not really), but somebody has to do it. We could go on like this
until the very last day. So let's say no. Let's say leave it for
1.8.14 which could be released anytime, say, 3+ months after 1.8.13,
depending on man power and pressure. I think there is enough of bugs
that go unfixed already and are going to slip into another release.

Post by Dan Gora
Do we have any kind of hard time limits to get a release out? I too
would like to get a release sooner than later, but the more fixes we
can get into this release, the better IMO...

No, but somebody has to review all of that. And if I knew how to
express next degree of being tight of time, I'd. Me, personally, I'll
be glad to fininish #65 mentioned above, DCMI, SEL and at most couple
reviews aside. As I said, there was plenty of time and it's kind of
proven this ``one more feature'' thing can go on forever.

Z.

Post by Dan Gora
thanks
dan

Post by Zdenek Styblik

Jim,
I have two things to fix before 1.8.13 is released, but I don't feel
like creation of RC should be put on hold because of these.
One is pretty much just a commit, the other one is, I have to admit,
more complicated than that,
Regards,
Z.

Dan Gora

2013-08-06 18:46:59 UTC

Permalink

Post by Zdenek Styblik

Stupid me. I forgot about these. However, we're talking about RC not release.

Post by Dan Gora
I also have two patches for ipmi_picmg.c that I'd like to try and get
in if possible. One is to change atoi to use the str2*

Huh? Where? I see no atoi() in ipmi_picmg.c. However, I see one atoi()
in ipmi_hpmfwupg.c which has slipped through. How's that even
possible, garrr!

ok, sorry.. I did the patch against an older version.. I didn't see
that those were fixed already... Never mind then...

Post by Zdenek Styblik
Is it really crucial to get it into 1.8.13?

eh...

Post by Zdenek Styblik

That's fine.. I just thought that if it's going to be another year
before the 1.8.14 release, that it's probably better to do it now if
possible.

Post by Zdenek Styblik
No, but somebody has to review all of that. And if I knew how to
express next degree of being tight of time, I'd. Me, personally, I'll
be glad to fininish #65 mentioned above, DCMI, SEL and at most couple
reviews aside. As I said, there was plenty of time and it's kind of
proven this ``one more feature'' thing can go on forever.

That's fine with me.. I'll submit the one patch for ipmi_picmg.c..
It's three lines of printf. You can include it if you'd like.. It's
not pressing.

thanks
d

Zdenek Styblik

2013-08-06 19:00:39 UTC

Permalink

On Tue, Aug 6, 2013 at 8:46 PM, Dan Gora <***@adax.com> wrote:
[...]

Post by Dan Gora
That's fine.. I just thought that if it's going to be another year
before the 1.8.14 release, that it's probably better to do it now if
possible.

Dan,

I understand. But from my point of view, number and interval between
releases depends on demand as well. If there is a demand, and it's
reasonable(having release every month isn't, imo; extreme case), I
don't see any reason why it shouldn't be satisfied.
Jim's aim was to shorten release cycle from three years and we're
doing it(now). Personally, I think release every 6 months(= 2 releases
a year) would be more than sufficient.

Post by Dan Gora
That's fine with me.. I'll submit the one patch for ipmi_picmg.c..
It's three lines of printf. You can include it if you'd like.. It's
not pressing.

Ok.

Z.