[pgpool-hackers: 1731] Re: Triaging to do items for 3.6

Ahsan Hadi ahsan.hadi at enterprisedb.com
Wed Jul 27 19:55:48 JST 2016


On Tue, Jul 26, 2016 at 5:35 PM, Tatsuo Ishii <ishii at postgresql.org> wrote:

> Remember that we have many bugs waiting for fixes. About half of them
> are assigned to Usama, because they are related to watchdog and
> pcp. He needs more time...
>

I believe it should be okay if we can push the overall release date by
couple of weeks. I can say for sure once we have gone through all the
must-have 3.6 items in our meeting on Friday.

I will try to come up with a list of must-have for 3.6 before our meeting
on friday. We can go through the list and discuss the release timing
accordingly.

Makes sense?


>
> > First of all, I agree that the documentation and language changes are
> very
> > important and they are must have for the release.
> >
> > However I would suggest that we move feature freeze by couple of weeks to
> > get pg_terminate_backend completed so we can include it in pgpool II 3.6.
> > We don't have many new features in this release so taking one more out
> that
> > we have already put in good amount of effort doesn't seem like a good
> idea
> > to me.
> >
> > #55 doesn't seem like a lot of work...but Usama can give his opinion
> about
> > that.
> >
> > my two cents...
> >
> > -- Ahsan
> >
> >
> >
> > On Tue, Jul 26, 2016 at 1:51 PM, Tatsuo Ishii <ishii at postgresql.org>
> wrote:
> >
> >> Usama,
> >> Pgpool-II developers,
> >>
> >> Now that we approaching the feature freeze (it's July 30th, this
> >> weekend), we need to triage some todo items.
> >>
> >> http://pgpool.net/mediawiki/index.php/pgpool-II_3.6_development
> >>
> >> Here is my ideas:
> >>
> >> #6: deal with pg_terminate_backend
> >> I propose to post pone to 3.7 because the proposed fix has more room
> >> to enhance. It would be better to aging the idea...
> >>
> >> #55: we should complete this in 3.6. Because: 1) it greatly enhance
> >> the usability 2) easy to implement 3) affect to docs
> >>
> >> We have tons of work before completing the SGML docs. Remember, we
> >> even have not done the English docs yet. We need to create Japanese
> >> docs at least (and Chinese docs if possible). We cannot release 3.6
> >> without the docs changes.
> >>
> >> What do you think?
> >>
> >> Best regards,
> >> --
> >> Tatsuo Ishii
> >> SRA OSS, Inc. Japan
> >> English: http://www.sraoss.co.jp/index_en.php
> >> Japanese:http://www.sraoss.co.jp
> >>
> >> _______________________________________________
> >> pgpool-hackers mailing list
> >> pgpool-hackers at pgpool.net
> >> http://www.pgpool.net/mailman/listinfo/pgpool-hackers
> >>
> >
> >
> >
> > --
> > Ahsan Hadi
> > Snr Director Product Development
> > EnterpriseDB Corporation
> > The Enterprise Postgres Company
> >
> > Phone: +92-51-8358874
> > Mobile: +92-333-5162114
> >
> > Website: www.enterprisedb.com
> > EnterpriseDB Blog: http://blogs.enterprisedb.com/
> > Follow us on Twitter: http://www.twitter.com/enterprisedb
> >
> > This e-mail message (and any attachment) is intended for the use of the
> > individual or entity to whom it is addressed. This message contains
> > information from EnterpriseDB Corporation that may be privileged,
> > confidential, or exempt from disclosure under applicable law. If you are
> > not the intended recipient or authorized to receive this for the intended
> > recipient, any use, dissemination, distribution, retention, archiving, or
> > copying of this communication is strictly prohibited. If you have
> received
> > this e-mail in error, please notify the sender immediately by reply
> e-mail
> > and delete this message.
>



-- 
Ahsan Hadi
Snr Director Product Development
EnterpriseDB Corporation
The Enterprise Postgres Company

Phone: +92-51-8358874
Mobile: +92-333-5162114

Website: www.enterprisedb.com
EnterpriseDB Blog: http://blogs.enterprisedb.com/
Follow us on Twitter: http://www.twitter.com/enterprisedb

This e-mail message (and any attachment) is intended for the use of the
individual or entity to whom it is addressed. This message contains
information from EnterpriseDB Corporation that may be privileged,
confidential, or exempt from disclosure under applicable law. If you are
not the intended recipient or authorized to receive this for the intended
recipient, any use, dissemination, distribution, retention, archiving, or
copying of this communication is strictly prohibited. If you have received
this e-mail in error, please notify the sender immediately by reply e-mail
and delete this message.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.sraoss.jp/pipermail/pgpool-hackers/attachments/20160727/9076be6b/attachment.html>


More information about the pgpool-hackers mailing list