New web page for release status

Started by Bruce Momjianover 20 years ago5 messages
#1Bruce Momjian
pgman@candle.pha.pa.us

I have put together a new web page to show all the PostgreSQL status
pages I maintain, and I have added a "bugs to be fixed in 8.1" page that
will track must-fix bugs for this release. It is at:

http://momjian.postgresql.org/pgrelease

I think this should be added to the developers page somewhere.

-- 
  Bruce Momjian                        |  http://candle.pha.pa.us
  pgman@candle.pha.pa.us               |  (610) 359-1001
  +  If your life is a hard drive,     |  13 Roberts Road
  +  Christ can be your backup.        |  Newtown Square, Pennsylvania 19073
#2Tom Lane
tgl@sss.pgh.pa.us
In reply to: Bruce Momjian (#1)
Re: [pgsql-www] New web page for release status

Bruce Momjian <pgman@candle.pha.pa.us> writes:

I have put together a new web page to show all the PostgreSQL status
pages I maintain, and I have added a "bugs to be fixed in 8.1" page that
will track must-fix bugs for this release.

Looks good, but some comments:

We have several open plperl items at the moment, also some trigger/FK
questions (although these also exist in 8.0, so they need not hold up
a beta release).

Also, we need to understand Mary Edie's report of slowdowns in the last
couple of weeks --- that's surely an open item.

standard_compliant_strings is certainly not going to become modifiable
in this release cycle; the infrastructure for the "on" setting hasn't
even been written yet.

AFAIK the PageAddItem patch has been rejected; if it is to be applied
it will require evidence not supplied to date. So it doesn't belong
in the "to be applied" list. (Hm, I see it in the "hold for 8.2" list
also...)

regards, tom lane

#3Bruce Momjian
pgman@candle.pha.pa.us
In reply to: Tom Lane (#2)
Re: [pgsql-www] New web page for release status

OK, I have made those adjustments. The bugs page is only for items that
no one is currently working on --- it isn't an exhaustive list, but as
things become stuck and unfixed, they will be moved there.

---------------------------------------------------------------------------

Tom Lane wrote:

Bruce Momjian <pgman@candle.pha.pa.us> writes:

I have put together a new web page to show all the PostgreSQL status
pages I maintain, and I have added a "bugs to be fixed in 8.1" page that
will track must-fix bugs for this release.

Looks good, but some comments:

We have several open plperl items at the moment, also some trigger/FK
questions (although these also exist in 8.0, so they need not hold up
a beta release).

Also, we need to understand Mary Edie's report of slowdowns in the last
couple of weeks --- that's surely an open item.

standard_compliant_strings is certainly not going to become modifiable
in this release cycle; the infrastructure for the "on" setting hasn't
even been written yet.

AFAIK the PageAddItem patch has been rejected; if it is to be applied
it will require evidence not supplied to date. So it doesn't belong
in the "to be applied" list. (Hm, I see it in the "hold for 8.2" list
also...)

regards, tom lane

-- 
  Bruce Momjian                        |  http://candle.pha.pa.us
  pgman@candle.pha.pa.us               |  (610) 359-1001
  +  If your life is a hard drive,     |  13 Roberts Road
  +  Christ can be your backup.        |  Newtown Square, Pennsylvania 19073
#4Magnus Hagander
mha@sollentuna.net
In reply to: Bruce Momjian (#3)
Re: New web page for release status

I have put together a new web page to show all the PostgreSQL
status pages I maintain, and I have added a "bugs to be fixed
in 8.1" page that will track must-fix bugs for this release.
It is at:

http://momjian.postgresql.org/pgrelease

I think this should be added to the developers page somewhere.

I think it would be better if the page itself was moved to the developer
page, and just the stuff that it points to stays on the different site.

Actually, I think the best would be to move even more of it to the
actual developer page (I realise we can't do that for the patches lists
that are built from mail folders. I still think that those should be
moved to some kind of "patch tracker" both to make them easier to access
and to make it easier for people to "fill in" for you when you are out
of town etc, but that's a completely different thing). AFAICS the "Open
Items" is just a webpage, could it be moved to the main website?

(Doing static webpages on the main website is really easy once you have
the template in place - and doing the template for something like this
is also very very easy as it's just a webpage with a title. The actual
updating is just a normal case of editing standard HTML)

//Magnus

#5Jim C. Nasby
jnasby@pervasive.com
In reply to: Magnus Hagander (#4)
Re: [HACKERS] New web page for release status

It'd also be good to add
http://candle.pha.pa.us/main/writings/pgsql/sgml/release.html#RELEASE-8-1
to the page.

On Tue, Aug 23, 2005 at 01:38:53PM +0200, Magnus Hagander wrote:

I have put together a new web page to show all the PostgreSQL
status pages I maintain, and I have added a "bugs to be fixed
in 8.1" page that will track must-fix bugs for this release.
It is at:

http://momjian.postgresql.org/pgrelease

I think this should be added to the developers page somewhere.

I think it would be better if the page itself was moved to the developer
page, and just the stuff that it points to stays on the different site.

Actually, I think the best would be to move even more of it to the
actual developer page (I realise we can't do that for the patches lists
that are built from mail folders. I still think that those should be
moved to some kind of "patch tracker" both to make them easier to access
and to make it easier for people to "fill in" for you when you are out
of town etc, but that's a completely different thing). AFAICS the "Open
Items" is just a webpage, could it be moved to the main website?

(Doing static webpages on the main website is really easy once you have
the template in place - and doing the template for something like this
is also very very easy as it's just a webpage with a title. The actual
updating is just a normal case of editing standard HTML)

//Magnus

---------------------------(end of broadcast)---------------------------
TIP 3: Have you checked our extensive FAQ?

http://www.postgresql.org/docs/faq

--
Jim C. Nasby, Sr. Engineering Consultant jnasby@pervasive.com
Pervasive Software http://pervasive.com 512-569-9461