SEO
vBulletin Search Engine Optimization
| |||||||
| Register | FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
04-12-2008, 08:45 AM
| ||||
| ||||
 Re: Lack of urgency in 8.3 reviewing Jonah H. Harris wrote: > On 5/16/07, Marc G. Fournier <scrappy@hub.org> wrote: > > Set a fixed date (ie. 3 weeks) and whatever isn't in gets punted to 8.4 ... if > > that means those 'large patches' don't get applied, so be it ... > > I disagree with that approach. Larger more complex patches required > much more work and effort than small, simple ones. Not only do I > think it's unfair to the authors who spent considerably more time on > their work, but I think it also sets a bad precedent for future work; > saying, in short, that if you want to make large strides to improve > PostgreSQL, and you followed the community development process, you're > still potentially last in line for review. Yep. We lose a lot of credibility if we did that. -- Bruce Momjian <bruce@momjian.us> http://momjian.us EnterpriseDB http://www.enterprisedb.com + If your life is a hard drive, Christ can be your backup. + ---------------------------(end of broadcast)--------------------------- TIP 4: Have you searched our list archives? http://archives.postgresql.org      |
|
04-12-2008, 08:45 AM
| |||
| |||
| Re: Lack of urgency in 8.3 reviewing -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 - --On Wednesday, May 16, 2007 21:04:27 -0400 Bruce Momjian <bruce@momjian.us> wrote: > Jonah H. Harris wrote: >> On 5/16/07, Marc G. Fournier <scrappy@hub.org> wrote: >> > Set a fixed date (ie. 3 weeks) and whatever isn't in gets punted to 8.4 >> > ... if that means those 'large patches' don't get applied, so be it ... >> >> I disagree with that approach. Larger more complex patches required >> much more work and effort than small, simple ones. Not only do I >> think it's unfair to the authors who spent considerably more time on >> their work, but I think it also sets a bad precedent for future work; >> saying, in short, that if you want to make large strides to improve >> PostgreSQL, and you followed the community development process, you're >> still potentially last in line for review. > > Yep. We lose a lot of credibility if we did that. So, we lose no credibility if we sit in feature freeze indefinitely, with no direction, while we wait for reviewers to finish reviewing? - ---- Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) Email . scrappy@hub.org MSN . scrappy@hub.org Yahoo . yscrappy Skype: hub.org ICQ . 7615664 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (FreeBSD) iD8DBQFGS7E64QvfyHIvDvMRAmW9AJ0Q75300Atm6nFOFT+1Yf MRCtrcdQCffW2l htlQKO5dZRC2k2lWPGkjGvk= =BhsF -----END PGP SIGNATURE----- ---------------------------(end of broadcast)--------------------------- TIP 3: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faq |
|
04-12-2008, 08:45 AM
| |||
| |||
| Re: Lack of urgency in 8.3 reviewing Marc G. Fournier wrote: > > Jonah H. Harris wrote: > >> On 5/16/07, Marc G. Fournier <scrappy@hub.org> wrote: > >> > Set a fixed date (ie. 3 weeks) and whatever isn't in gets punted to 8.4 > >> > ... if that means those 'large patches' don't get applied, so be it ... > >> > >> I disagree with that approach. Larger more complex patches required > >> much more work and effort than small, simple ones. Not only do I > >> think it's unfair to the authors who spent considerably more time on > >> their work, but I think it also sets a bad precedent for future work; > >> saying, in short, that if you want to make large strides to improve > >> PostgreSQL, and you followed the community development process, you're > >> still potentially last in line for review. > > > > Yep. We lose a lot of credibility if we did that. > > So, we lose no credibility if we sit in feature freeze indefinitely, with no > direction, while we wait for reviewers to finish reviewing? Well, if we stay indefinitely, then we have no release and we close up the project. I think eventually we will release. -- Bruce Momjian <bruce@momjian.us> http://momjian.us EnterpriseDB http://www.enterprisedb.com + If your life is a hard drive, Christ can be your backup. + ---------------------------(end of broadcast)--------------------------- TIP 3: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faq |
|
04-12-2008, 08:45 AM
| ||||
| ||||
| Re: Lack of urgency in 8.3 reviewing Marc G. Fournier wrote: >>> I disagree with that approach. Larger more complex patches required >>> much more work and effort than small, simple ones. Not only do I >>> think it's unfair to the authors who spent considerably more time on >>> their work, but I think it also sets a bad precedent for future work; >>> saying, in short, that if you want to make large strides to improve >>> PostgreSQL, and you followed the community development process, you're >>> still potentially last in line for review. >> Yep. We lose a lot of credibility if we did that. > > So, we lose no credibility if we sit in feature freeze indefinitely, with no > direction, while we wait for reviewers to finish reviewing? *cough* that is hardly what is happening. Just today we had two people step up and commit to help reviewing. One of them is a committer (AndrewD). I believe under no uncertain terms, that if we continual proactive communication over the next several weeks that we will see a marked and steady improvement to our existing status. Let's keep this on earth shall we. Sincerely, Joshua D. Drake -- === The PostgreSQL Company: Command Prompt, Inc. === Sales/Support: +1.503.667.4564 || 24x7/Emergency: +1.800.492.2240 Providing the most comprehensive PostgreSQL solutions since 1997 http://www.commandprompt.com/ Donate to the PostgreSQL Project: http://www.postgresql.org/about/donate PostgreSQL Replication: http://www.commandprompt.com/products/ ---------------------------(end of broadcast)--------------------------- TIP 2: Don't 'kill -9' the postmaster |
Linear Mode
