[pgpool-hackers: 1758] RPM

[Tatsuo Ishii]

Our PRMs include incremental changes from the last minor releases. For
example, RPMs for Pgpool-II 3.5.3 include the fixes after Pgpool-II
3.5.3 released. Normally this is good because RPMs could have fixes
before next minor releases are out. However, this could raise a
headache for developers.

In this report:
http://www.pgpool.net/mantisbt/view.php?id=233

The reporter said that he is using Pgpool-II 3.5.3 but in his note:

[425-1] 2016-08-15 13:29:12 [2011] LOG: new connection received
[425-2] 2016-08-15 13:29:12 [2011] DETAIL: connecting host=xxx.xxx.xxx.xxx port=59168
[425-3] 2016-08-15 13:29:12 [2011] LOCATION: child.c:2110

The line number 2110 is different from the actual Pgpool-II 3.5.3
source code. I was confused by this and finally figured out that he is
using RPM which includes incremental diff against 3.5.3.

I think including incremental diffs in RPM gives more problem than
benefit because taking care bug report and fixing bugs consume
developer resource a lot. So I propose to remove the incremental diff
part from RPMs. We release new RPMs every 2 or 3 months and this is
convenient enough for users even without incremental fixes. If other
developers agree, we will apply the policy for next RPM release (we
plan to release new minor versions by the end of this month).

Objections? Comments?

Best regards,
--
Tatsuo Ishii
SRA OSS, Inc. Japan
English: http://www.sraoss.co.jp/index_en.php
Japanese:http://www.sraoss.co.jp