| From: | Kevin Hunter <hunteke(at)earlham(dot)edu> |
|---|---|
| To: | Josh Berkus <josh(at)agliodbs(dot)com> |
| Cc: | Postgres Advocacy List <pgsql-advocacy(at)postgresql(dot)org>, Devrim Gündüz <devrim(at)commandprompt(dot)com>, Alvaro Herrera <alvherre(at)commandprompt(dot)com>, "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>, "Gavin M(dot) Roy" <gmr(at)myyearbook(dot)com> |
| Subject: | Re: PostgreSQL passes MySQL for Freshmeat Downloads |
| Date: | 2008-06-13 17:57:54 |
| Message-ID: | 4852B522.7010300@earlham.edu |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-advocacy |
At 1:29p -0400 on Fri, 13 Jun 2008, Josh Berkus wrote:
>> http://sourceforge.net/projects/pgsql
Hmm, given that patches /do/ come out every so often, and people will
inevitably have downloaded Postgres before that time, would it also be
prudent to offer the different patches since the initial release? All I
see currently are the most recent versions of each release.
Perhaps only offer the most recent version, and all previous patches?
> That's Sourceforge, not Freshmeat. Different.
I don't know Freshmeat, but looking at the web page,
http://freshmeat.net/projects/pgsql/ it looks like there is an About
section, as well as a bunch of links. In lieu of the nagging program to
keep it up to date, what's wrong with mentioning in the about section
something along the lines of "See the project home page for the most
recent release and server patches" ?
Kevin
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2008-06-13 18:30:52 | Problem with press release |
| Previous Message | Marc G. Fournier | 2008-06-13 17:52:28 | Re: PostgreSQL passes MySQL for Freshmeat Downloads |