| From: | Mike Blackwell <mike(dot)blackwell(at)rrd(dot)com> |
|---|---|
| To: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
| Cc: | Peter Geoghegan <pg(at)heroku(dot)com>, Magnus Hagander <magnus(at)hagander(dot)net>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Within CF app, "Bug Fixes" should be "Bug Fixes/Refactoring" |
| Date: | 2015-10-29 20:10:04 |
| Message-ID: | CANPAkgsRosW+43-n8TPueThSQ8Sc-gWObqJEY0zpCfoNyWYyow@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, Oct 29, 2015 at 2:45 PM, Michael Paquier <michael(dot)paquier(at)gmail(dot)com>
wrote:
> On Thu, Oct 29, 2015 at 8:33 PM, Peter Geoghegan <pg(at)heroku(dot)com> wrote:
> > I think that within the CF app, we should either rename the patch
> > topic "Bug Fixes" to "Bug Fixes/Refactoring", or introduce a new
> > "Refactoring" topic. I prefer the first approach.
>
> I would vote for the second approach, with a separate category for
> refactoring.
>
>
So if a bug fix involved some refactoring, which would you put it under?
Or would you
expect separate CF entries for the refactoring and the fix?
__________________________________________________________________________________
*Mike Blackwell | Technical Analyst, Distribution Services/Rollout
Management | RR Donnelley*
1750 Wallace Ave | St Charles, IL 60174-3401
Office: 630.313.7818
Mike(dot)Blackwell(at)rrd(dot)com
http://www.rrdonnelley.com
<http://www.rrdonnelley.com/>
* <Mike(dot)Blackwell(at)rrd(dot)com>*
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2015-10-29 20:10:31 | Re: Within CF app, "Bug Fixes" should be "Bug Fixes/Refactoring" |
| Previous Message | Michael Paquier | 2015-10-29 19:45:57 | Re: Within CF app, "Bug Fixes" should be "Bug Fixes/Refactoring" |