public inbox for [email protected]help / color / mirror / Atom feed
Proposed changes to security.html 11+ messages / 6 participants [nested] [flat]
* Proposed changes to security.html @ 2013-02-06 20:01 Josh Berkus <[email protected]> 0 siblings, 4 replies; 11+ messages in thread From: Josh Berkus @ 2013-02-06 20:01 UTC (permalink / raw) To: pgsql-www Folks, I'd like to make two changes to the security.html page: 1) change all references from "contrib modules" to "extensions". Put a note on the bottom of the page explaining that they are the same thing. 2) create a second page, security-old.html. This page would archive the references to security issues patched on versions no longer under support (i.e. 8.2 and earlier). -- Josh Berkus PostgreSQL Experts Inc. http://pgexperts.com -- Sent via pgsql-www mailing list ([email protected]) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-www ^ permalink raw reply [nested|flat] 11+ messages in thread
* Re: Proposed changes to security.html @ 2013-02-06 20:08 Dave Page <[email protected]> parent: Josh Berkus <[email protected]> 3 siblings, 0 replies; 11+ messages in thread From: Dave Page @ 2013-02-06 20:08 UTC (permalink / raw) To: Josh Berkus <[email protected]>; +Cc: pgsql-www On Wed, Feb 6, 2013 at 8:01 PM, Josh Berkus <[email protected]> wrote: > Folks, > > I'd like to make two changes to the security.html page: > > 1) change all references from "contrib modules" to "extensions". Put a > note on the bottom of the page explaining that they are the same thing. > > 2) create a second page, security-old.html. This page would archive the > references to security issues patched on versions no longer under > support (i.e. 8.2 and earlier). No objection here. -- Dave Page Blog: http://pgsnake.blogspot.com Twitter: @pgsnake EnterpriseDB UK: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-www mailing list ([email protected]) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-www ^ permalink raw reply [nested|flat] 11+ messages in thread
* Re: Proposed changes to security.html @ 2013-02-06 21:41 Tom Lane <[email protected]> parent: Josh Berkus <[email protected]> 3 siblings, 1 reply; 11+ messages in thread From: Tom Lane @ 2013-02-06 21:41 UTC (permalink / raw) To: Josh Berkus <[email protected]>; +Cc: pgsql-www Josh Berkus <[email protected]> writes: > I'd like to make two changes to the security.html page: > 1) change all references from "contrib modules" to "extensions". Put a > note on the bottom of the page explaining that they are the same thing. > 2) create a second page, security-old.html. This page would archive the > references to security issues patched on versions no longer under > support (i.e. 8.2 and earlier). At this point, shouldn't 8.3 also go to the "old" page? regards, tom lane -- Sent via pgsql-www mailing list ([email protected]) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-www ^ permalink raw reply [nested|flat] 11+ messages in thread
* Re: Proposed changes to security.html @ 2013-02-07 01:57 Josh Berkus <[email protected]> parent: Tom Lane <[email protected]> 0 siblings, 1 reply; 11+ messages in thread From: Josh Berkus @ 2013-02-07 01:57 UTC (permalink / raw) To: Tom Lane <[email protected]>; +Cc: pgsql-www > At this point, shouldn't 8.3 also go to the "old" page? *After* the next update release, yes. I was figuring I'd wait for a couple weeks after that, and then archive it. -- Josh Berkus PostgreSQL Experts Inc. http://pgexperts.com -- Sent via pgsql-www mailing list ([email protected]) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-www ^ permalink raw reply [nested|flat] 11+ messages in thread
* Re: Proposed changes to security.html @ 2013-02-07 12:41 Magnus Hagander <[email protected]> parent: Josh Berkus <[email protected]> 0 siblings, 0 replies; 11+ messages in thread From: Magnus Hagander @ 2013-02-07 12:41 UTC (permalink / raw) To: Josh Berkus <[email protected]>; +Cc: Tom Lane <[email protected]>; pgsql-www On Thu, Feb 7, 2013 at 2:57 AM, Josh Berkus <[email protected]> wrote: > >> At this point, shouldn't 8.3 also go to the "old" page? > > *After* the next update release, yes. I was figuring I'd wait for a > couple weeks after that, and then archive it. Yeah, seems reasonable to keep it around for a while. -- Magnus Hagander Me: http://www.hagander.net/ Work: http://www.redpill-linpro.com/ -- Sent via pgsql-www mailing list ([email protected]) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-www ^ permalink raw reply [nested|flat] 11+ messages in thread
* Re: Proposed changes to security.html @ 2013-02-14 20:58 Stefan Kaltenbrunner <[email protected]> parent: Josh Berkus <[email protected]> 3 siblings, 1 reply; 11+ messages in thread From: Stefan Kaltenbrunner @ 2013-02-14 20:58 UTC (permalink / raw) To: Josh Berkus <[email protected]>; +Cc: pgsql-www On 02/06/2013 09:01 PM, Josh Berkus wrote: > Folks, > > I'd like to make two changes to the security.html page: > > 1) change all references from "contrib modules" to "extensions". Put a > note on the bottom of the page explaining that they are the same thing. > > 2) create a second page, security-old.html. This page would archive the > references to security issues patched on versions no longer under > support (i.e. 8.2 and earlier). +1 one on both - do you have a proposed wording or even better a patch for those changes? Stefan -- Sent via pgsql-www mailing list ([email protected]) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-www ^ permalink raw reply [nested|flat] 11+ messages in thread
* Re: Proposed changes to security.html @ 2013-02-14 22:48 Josh Berkus <[email protected]> parent: Stefan Kaltenbrunner <[email protected]> 0 siblings, 0 replies; 11+ messages in thread From: Josh Berkus @ 2013-02-14 22:48 UTC (permalink / raw) To: Stefan Kaltenbrunner <[email protected]>; +Cc: pgsql-www On 02/14/2013 12:58 PM, Stefan Kaltenbrunner wrote: > On 02/06/2013 09:01 PM, Josh Berkus wrote: >> Folks, >> >> I'd like to make two changes to the security.html page: >> >> 1) change all references from "contrib modules" to "extensions". Put a >> note on the bottom of the page explaining that they are the same thing. >> >> 2) create a second page, security-old.html. This page would archive the >> references to security issues patched on versions no longer under >> support (i.e. 8.2 and earlier). > > +1 one on both - do you have a proposed wording or even better a patch > for those changes? I'll submit a patch. I've just been kind of busy. -- Josh Berkus PostgreSQL Experts Inc. http://pgexperts.com -- Sent via pgsql-www mailing list ([email protected]) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-www ^ permalink raw reply [nested|flat] 11+ messages in thread
* Re: Proposed changes to security.html @ 2013-03-01 22:33 Peter Eisentraut <[email protected]> parent: Josh Berkus <[email protected]> 3 siblings, 1 reply; 11+ messages in thread From: Peter Eisentraut @ 2013-03-01 22:33 UTC (permalink / raw) To: Josh Berkus <[email protected]>; +Cc: pgsql-www On 2/6/13 3:01 PM, Josh Berkus wrote: > I'd like to make two changes to the security.html page: > > 1) change all references from "contrib modules" to "extensions". Put a > note on the bottom of the page explaining that they are the same thing. What would be the point of that, other than introducing the use of less accurate language? -- Sent via pgsql-www mailing list ([email protected]) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-www ^ permalink raw reply [nested|flat] 11+ messages in thread
* Re: Proposed changes to security.html @ 2013-03-02 00:22 Josh Berkus <[email protected]> parent: Peter Eisentraut <[email protected]> 0 siblings, 1 reply; 11+ messages in thread From: Josh Berkus @ 2013-03-02 00:22 UTC (permalink / raw) To: Peter Eisentraut <[email protected]>; +Cc: pgsql-www > What would be the point of that, other than introducing the use of less > accurate language? Oh, right, we have some contrib modules which are not extensions. However, the term "contrib" is confusing and not very helpful. Maybe I should use the term "Additional Supplied Modules" (shorthand "modules"), which is what we use in the docs? -- Josh Berkus PostgreSQL Experts Inc. http://pgexperts.com -- Sent via pgsql-www mailing list ([email protected]) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-www ^ permalink raw reply [nested|flat] 11+ messages in thread
* Re: Proposed changes to security.html @ 2013-03-02 04:16 Peter Eisentraut <[email protected]> parent: Josh Berkus <[email protected]> 0 siblings, 1 reply; 11+ messages in thread From: Peter Eisentraut @ 2013-03-02 04:16 UTC (permalink / raw) To: Josh Berkus <[email protected]>; +Cc: pgsql-www On Fri, 2013-03-01 at 16:22 -0800, Josh Berkus wrote: > > What would be the point of that, other than introducing the use of less > > accurate language? > > Oh, right, we have some contrib modules which are not extensions. > However, the term "contrib" is confusing and not very helpful. Maybe I > should use the term "Additional Supplied Modules" (shorthand "modules"), > which is what we use in the docs? That might be worthwhile consideration for introductory or marketing material, say, but for the purpose of tracking security issues, "contrib" is perfectly clear: If you are installing from source, it is code that lives under contrib/. If you are installing from binary, it is code that is in the postgresql-contrib package (usually). Calling it anything other than "contrib" cannot possibly make that more clear. -- Sent via pgsql-www mailing list ([email protected]) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-www ^ permalink raw reply [nested|flat] 11+ messages in thread
* Re: Proposed changes to security.html @ 2013-03-03 20:06 Josh Berkus <[email protected]> parent: Peter Eisentraut <[email protected]> 0 siblings, 0 replies; 11+ messages in thread From: Josh Berkus @ 2013-03-03 20:06 UTC (permalink / raw) To: Peter Eisentraut <[email protected]>; +Cc: pgsql-www > That might be worthwhile consideration for introductory or marketing > material, say, but for the purpose of tracking security issues, > "contrib" is perfectly clear: If you are installing from source, it is > code that lives under contrib/. If you are installing from binary, it > is code that is in the postgresql-contrib package (usually). Calling it > anything other than "contrib" cannot possibly make that more clear. Yeah, I suppose the security page is not the place to address this. We have a larger project problem in using three different bits of terminology for mostly the same set of software. We can fix the security page once we fix the terminology in general. -- Josh Berkus PostgreSQL Experts Inc. http://pgexperts.com -- Sent via pgsql-www mailing list ([email protected]) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-www ^ permalink raw reply [nested|flat] 11+ messages in thread
end of thread, other threads:[~2013-03-03 20:06 UTC | newest] Thread overview: 11+ messages (download: mbox mbox.gz follow: Atom feed) -- links below jump to the message on this page -- 2013-02-06 20:01 Proposed changes to security.html Josh Berkus <[email protected]> 2013-02-06 20:08 ` Dave Page <[email protected]> 2013-02-06 21:41 ` Tom Lane <[email protected]> 2013-02-07 01:57 ` Josh Berkus <[email protected]> 2013-02-07 12:41 ` Magnus Hagander <[email protected]> 2013-02-14 20:58 ` Stefan Kaltenbrunner <[email protected]> 2013-02-14 22:48 ` Josh Berkus <[email protected]> 2013-03-01 22:33 ` Peter Eisentraut <[email protected]> 2013-03-02 00:22 ` Josh Berkus <[email protected]> 2013-03-02 04:16 ` Peter Eisentraut <[email protected]> 2013-03-03 20:06 ` Josh Berkus <[email protected]>
This inbox is served by agora; see mirroring instructions for how to clone and mirror all data and code used for this inbox