Skip site navigation (1) Skip section navigation (2)

Re: Updating Freshmeat & Sourceforge?

From: Josh Berkus <josh(at)agliodbs(dot)com>
To: "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>
Cc: Bruce Momjian <bruce(at)momjian(dot)us>, PostgreSQL Advocacy <pgsql-advocacy(at)postgresql(dot)org>
Subject: Re: Updating Freshmeat & Sourceforge?
Date: 2012-03-23 17:34:38
Message-ID: 4F6CB42E.9050709@agliodbs.com (view raw or flat)
Thread:
Lists: pgsql-advocacy
> It seems to me that the solution is to make updating Freecode (freshmeat
> doesn't exist anymore) and sourceforge should be part of the committers
> job as part of the release process.

That seems unreasonable.  The release team has enough to do, and if
Freecode gets updated a couple of days later, it's not really a problem.
 I think continuing to do it through separate advocacy volunteers makes
sense.

-- 
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com

In response to

pgsql-advocacy by date

Next:From: Josh BerkusDate: 2012-03-25 20:22:21
Subject: Re: Open Database Camp at 2012 SouthEast LinuxFest
Previous:From: Joshua D. DrakeDate: 2012-03-23 17:12:06
Subject: Re: Updating Freshmeat & Sourceforge?

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group