Re: [DOCS] should we have a separate page that clearly defines what a minor release is and why it's a good idea to keep up with them?

>> > On the front page, we already have "Latest Releases" with links to the
>> > most recent release for each version still actively maintained and
>> > release notes.  (Would it make sense to change that title from "Latest
>> > Releases" to "Actively Maintained Releases")
>>
>> I think not. The meaning is "latest releases available for each branch",
>> not "these are the actively maintained branches".
>
> Why aren't 7.3.18, 7.2.8, 7.1.6, etc there then?
>
> Clearly there is some criteria for which branches are presented there.

<7.3 is EOL. We still back patch what we can but they are considered
deprecated.

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/