Re: [HACKERS] commitfest.postgresql.org - Mailing list pgsql-www

From Tom Lane
Subject Re: [HACKERS] commitfest.postgresql.org
Date
Msg-id 26913.1246995720@sss.pgh.pa.us
Whole thread Raw
In response to Re: [HACKERS] commitfest.postgresql.org  (Peter Eisentraut <peter_e@gmx.net>)
List pgsql-www
Peter Eisentraut <peter_e@gmx.net> writes:
> With the wiki, the data of the old fests will pretty much stay what is
> was, unless we change the wiki templates in drastic ways, as I
> understand it.  But if we did changes like the above, or more
> complicated things, perhaps, what will happen?  Perhaps we simply
> don't care about the historical data.  But if we do, we better have
> pretty high confidence that the current application will do for a
> while or is easily upgradable.

I'm not convinced that we care in the least about commitfests that are
more than a fest or two back; especially since the mailing lists archive
all the interesting underlying data.  However, if we did, the answer
doesn't seem that hard: keep the old database instance on-line for
serving up the old data, and put a new one beside it.
        regards, tom lane


pgsql-www by date:

Previous
From: "Kevin Grittner"
Date:
Subject: Re: [HACKERS] commitfest.postgresql.org
Next
From: Robert Haas
Date:
Subject: Re: [HACKERS] commitfest.postgresql.org