From: | Magnus Hagander <magnus(at)hagander(dot)net> |
---|---|
To: | Albe Laurenz <laurenz(dot)albe(at)wien(dot)gv(dot)at> |
Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: pgfoundry references in docs |
Date: | 2012-07-04 07:20:00 |
Message-ID: | CABUevEzmQioEmMViv45TS9DWgZbXNoPUPwudniP8XOSrGH191A@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Wed, Jul 4, 2012 at 9:18 AM, Albe Laurenz <laurenz(dot)albe(at)wien(dot)gv(dot)at> wrote:
> Magnus Hagander wrote:
>> Attached are two patches, one of which I'd like to apply. Open for
>> discussion on which one.
>>
>> The smaller one, pgfoundry_1.diff, removes the suggestion to apply for
>> new projects on pgfoundry. The reason for this being that pgfoundry
>> doesn't *accept* new projects anymore.
>>
>> The second one removes the reference to pgfoundry completely. As a
>> step in the deprecation.
>>
>> I'd prefer to apply the second one, but will settle for the first one
>> if people object ;)
>
> Well, I don't object to the documentation change, but I have a problem
> with the fact.
>
> Are there any other places that could be recommended for hosting
> my pgFoundry projects?
> If yes, that should be mentioned in the documentation.
Exiting pgfoundry projects are perfectly safe for now - but *new*
projects are not accepted.
There is a project underway (for a *long* time - it keeps getting
stalled) working on migration paths. Until such paths are available
and documented, existing projects will still be safe on pgfoundry.
--
Magnus Hagander
Me: http://www.hagander.net/
Work: http://www.redpill-linpro.com/
From | Date | Subject | |
---|---|---|---|
Next Message | Albe Laurenz | 2012-07-04 07:50:29 | Re: Oracle porting sample instr function |
Previous Message | Albe Laurenz | 2012-07-04 07:18:21 | Re: pgfoundry references in docs |