public inbox for [email protected]  

help / color / mirror / Atom feed

From: Devrim GÜNDÜZ <[email protected]>
To: [email protected]
Cc: PostgreSQL WWW <[email protected]>
Subject: Re: about yum.postgresql.org
Date: Tue, 03 Jul 2012 00:12:27 +0300
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>


Hi,

On Mon, 2012-07-02 at 18:43 +0200, Cédric Villemain wrote:

<snip>

> I believe it needs at least one for the NEWS (new build, fix, etc...)
> and for  bug-report.

http://svn.pgrpms.org/browser
http://wiki.pgrpms.org/report

You can use the former one to track updates that are in the queue, the
second one for the bug reports and the progress.

I got a set of emails from you and other folks last week, but, per:

http://wiki.pgrpms.org/wiki/PackageUpdatePolicies

I intend to reply them this week.

> Debian stuff got one: http://archives.postgresql.org/pgsql-pkg-debian/
> 
> Can we consider http://archives.postgresql.org/pgsql-pkg-yum/ ? 

Good idea, +1.

> I would also like to see the maintenance team of those packages been
> extended,  I believe Devrim is alone, which is not 'safe' (what
> happens if Devrim is in  holidays *without* internet, ... ok it is
> *rare*, but still). 

Well, there are two separate processes in here:

* Updating the spec file : I'm all for adding new people, who have
provided high quality patches so far. However, my experience has not
been that nice -- some people either tried to break packaging policies
of Fedora/Red Hat, some people tried to change the packaging layout
based on their personal/company/customer requirements. IIRC we have
Fetter and Magnus as the alternative committers in here, but I'm too
lazy to check it now. AFAIK, we don't have many Fedora packagers in the
community, except me and Tom (please feel to smack me if I am missing
someone else). Having some community packaging experience is strictly
what I personally am looking for, if I am in charge of adding new people
in here.

* Building packages: This requires extra permissions, extra caution,
extra experience. This process is half-automate, which is intended,
because we need a human *at least* to sign the packages (and check the
build status). This also requires access to a community machine, so that
probably something that our sysadmin team will also need to decide -- 

What if I decide to quit or die? No idea, but I believe the process is
more or less documented somewhere (sysadmins?), so someone can pick up
the packaging.

Regards,
-- 
Devrim GÜNDÜZ
Principal Systems Engineer @ EnterpriseDB: http://www.enterprisedb.com
PostgreSQL Danışmanı/Consultant, Red Hat Certified Engineer
Community: devrim~PostgreSQL.org, devrim.gunduz~linux.org.tr
http://www.gunduz.org  Twitter: http://twitter.com/devrimgunduz


Attachments:

  [application/pgp-signature] signature.asc (198B, 2-signature.asc)
  download

view thread (13+ messages)  latest in thread

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected]
  Subject: Re: about yum.postgresql.org
  In-Reply-To: <[email protected]>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox