Thread: PostgreSQL passes MySQL for Freshmeat Downloads
Check it out, folks: http://freshmeat.net/ --Josh Berkus -- --Josh Josh Berkus PostgreSQL @ Sun San Francisco
Gavin, > Maybe, one day someone on pgsql-www can get access to keep it up to > date. Marc & Neil do. I pestered them already. Maybe I can get access. -- --Josh Josh Berkus PostgreSQL @ Sun San Francisco
On Thu, 2008-06-12 at 16:38 -0700, Josh Berkus wrote: > Gavin, > > > Maybe, one day someone on pgsql-www can get access to keep it up to > > date. > > Marc & Neil do. I pestered them already. Maybe I can get access. > I thought Devrim had access as well? This seems to be something that should be on pmt or as part of the release process no? Joshua D. Drake > -- > --Josh > > Josh Berkus > PostgreSQL @ Sun > San Francisco >
Hi, On Thu, 2008-06-12 at 16:53 -0700, Joshua D. Drake wrote: > > I thought Devrim had access as well? I have access to sf.net -- and I just finished updating it. Regards, -- Devrim GÜNDÜZ , RHCE PostgreSQL Replication, Consulting, Custom Development, 24x7 support Managed Services, Shared and Dedicated Hosting Co-Authors: plPHP, ODBCng - http://www.commandprompt.com/
Attachment
Josh Berkus wrote: > Check it out, folks: > > http://freshmeat.net/ And Freshmeat has 8.3.0! I thought we were going to keep this up to date, and if not, we were going to remove it. Well, we are not keeping it up to date! Updated: Wed, Mar 5th 2008 22:40 UTC (3 months, 10 days ago) -- Bruce Momjian <bruce@momjian.us> http://momjian.us EnterpriseDB http://enterprisedb.com + If your life is a hard drive, Christ can be your backup. +
On Thu, 2008-06-12 at 22:36 -0400, Bruce Momjian wrote: > Josh Berkus wrote: > > Check it out, folks: > > > > http://freshmeat.net/ > > And Freshmeat has 8.3.0! I thought we were going to keep this up to > date, and if not, we were going to remove it. Well, we are not keeping > it up to date! It is even part of the release prep: http://wiki.postgresql.org/wiki/ReleasePrep We need to be checking this stuff off. Joshua D. Drake
Bruce Momjian wrote: > Josh Berkus wrote: >> Check it out, folks: >> >> http://freshmeat.net/ > > And Freshmeat has 8.3.0! I thought we were going to keep this up to > date, and if not, we were going to remove it. Well, we are not keeping > it up to date! > > Updated: Wed, Mar 5th 2008 22:40 UTC (3 months, 10 days ago) > Actually it seems quite messy. The download links for the tarball etc point to 8.3.0 The branches listed have Dev as 8.0.0rc1 and stable as 8.2.4 -- Shane Ambler pgSQL (at) Sheeky (dot) Biz Get Sheeky @ http://Sheeky.Biz
Bruce Momjian wrote: > Josh Berkus wrote: > > Check it out, folks: > > > > http://freshmeat.net/ > > And Freshmeat has 8.3.0! I thought we were going to keep this up to > date, and if not, we were going to remove it. Well, we are not keeping > it up to date! _Please_ by all means let's remove it. It is always out of date. If we absolutely must keep a Freshmeat entry, then it should not list any "current release" at all -- let's make it just point to our own web site that's (almost) always up to date. -- Alvaro Herrera http://www.CommandPrompt.com/ The PostgreSQL Company - Command Prompt, Inc.
Devrim GÜNDÜZ wrote: > Hi, > > On Thu, 2008-06-12 at 16:53 -0700, Joshua D. Drake wrote: > > > > I thought Devrim had access as well? > > I have access to sf.net -- and I just finished updating it. I have no idea what you did, but it's still out of date. -- Alvaro Herrera http://www.CommandPrompt.com/ The PostgreSQL Company - Command Prompt, Inc.
Alvaro Herrera wrote: > Bruce Momjian wrote: > >> Josh Berkus wrote: >> >>> Check it out, folks: >>> >>> http://freshmeat.net/ >>> >> And Freshmeat has 8.3.0! I thought we were going to keep this up to >> date, and if not, we were going to remove it. Well, we are not keeping >> it up to date! >> > > _Please_ by all means let's remove it. It is always out of date. If we > absolutely must keep a Freshmeat entry, then it should not list any > "current release" at all -- let's make it just point to our own web site > that's (almost) always up to date. > But then we would drop behind MySQL in terms of downloads, since noone would be able to download from freshmeat. ;-) It's quite the conundrum.. Perhaps we can let them download a downloader, which downloads from the PostgreSQL site (j/k)... -- Chander Ganesan Open Technology Group, Inc. One Copley Parkway, Suite 210 Morrisville, NC 27560 919-463-0999/877-258-8987 http://www.otg-nc.com
On Fri, Jun 13, 2008 at 8:59 AM, Chander Ganesan <chander@otg-nc.com> wrote: > Alvaro Herrera wrote: >> >> _Please_ by all means let's remove it. It is always out of date. If we >> absolutely must keep a Freshmeat entry, then it should not list any >> "current release" at all -- let's make it just point to our own web site >> that's (almost) always up to date. >> > > But then we would drop behind MySQL in terms of downloads, since noone would > be able to download from freshmeat. ;-) It's quite the conundrum.. Perhaps > we can let them download a downloader, which downloads from the PostgreSQL > site (j/k)... > Although I agree it's better to present nothing at all than to present something consistently incorrect and out-of-date, I think that entry on freshmeat is too important to the project's public image to let it go. I think a solution as simple as a script that scrapes the PostgreSQL download site for the newest version (currently 8.3.3) and ensures it's mentioned in the freshmeat entry (currently, it's not) and then nags the people with access to edit the entry would be sufficient to solve this problem. I have no clout in this community, so I won't ask for access to edit the freshmeat entry. But I would be happy to write and maintain the script! -Jonathan
I'd rather step up to maintain it than let it go. It's a 5 minute change, 5 times a year? If I can get access, I will commit to keeping it up to date.
Gavin
On Fri, Jun 13, 2008 at 8:26 AM, Alvaro Herrera <alvherre@commandprompt.com> wrote:
Bruce Momjian wrote:_Please_ by all means let's remove it. It is always out of date. If we
> Josh Berkus wrote:
> > Check it out, folks:
> >
> > http://freshmeat.net/
>
> And Freshmeat has 8.3.0! I thought we were going to keep this up to
> date, and if not, we were going to remove it. Well, we are not keeping
> it up to date!
absolutely must keep a Freshmeat entry, then it should not list any
"current release" at all -- let's make it just point to our own web site
that's (almost) always up to date.
--
Alvaro Herrera http://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.
--
Sent via pgsql-advocacy mailing list (pgsql-advocacy@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-advocacy
Jonathan Fuerth wrote: > I think a solution as simple as a script that scrapes the PostgreSQL > download site for the newest version (currently 8.3.3) and ensures > it's mentioned in the freshmeat entry (currently, it's not) and then > nags the people with access to edit the entry would be sufficient to > solve this problem. Now that's a useful suggestion. > I have no clout in this community, so I won't ask for access to edit > the freshmeat entry. But I would be happy to write and maintain the > script! Please do. -- Alvaro Herrera http://www.CommandPrompt.com/ PostgreSQL Replication, Consulting, Custom Development, 24x7 support
Gavin M. Roy wrote: > I'd rather step up to maintain it than let it go. It's a 5 minute change, 5 > times a year? If I can get access, I will commit to keeping it up to date. Fine. I don't care who does it but last time we saw this problem a few months ago the community was assured Freshmeat would be kept up to date, but it wasn't. Exactly where is the release checklist that shows we should update Freshmeat? -- Bruce Momjian <bruce@momjian.us> http://momjian.us EnterpriseDB http://enterprisedb.com + If your life is a hard drive, Christ can be your backup. +
On Fri, 2008-06-13 at 11:35 -0400, Bruce Momjian wrote: > Gavin M. Roy wrote: > > I'd rather step up to maintain it than let it go. It's a 5 minute change, 5 > > times a year? If I can get access, I will commit to keeping it up to date. > > Fine. I don't care who does it but last time we saw this problem a few > months ago the community was assured Freshmeat would be kept up to date, > but it wasn't. > > Exactly where is the release checklist that shows we should update > Freshmeat? http://wiki.postgresql.org/wiki/ReleasePrep Joshua D. Drake
On Fri, Jun 13, 2008 at 11:35 AM, Alvaro Herrera <alvherre@commandprompt.com> wrote: > Jonathan Fuerth wrote: > >> I think a solution as simple as a script that scrapes the PostgreSQL >> download site for the newest version (currently 8.3.3) and ensures >> it's mentioned in the freshmeat entry (currently, it's not) and then >> nags the people with access to edit the entry would be sufficient to >> solve this problem. > > Now that's a useful suggestion. > >> I have no clout in this community, so I won't ask for access to edit >> the freshmeat entry. But I would be happy to write and maintain the >> script! > > Please do. > Sure! I already have the most important components worked out from previous projects, so I should be able to get it up and running tonight. How frequently and at what time(s) of day do you need to be nagged for this solution to be effective? :) -Jonathan
On Fri, 2008-06-13 at 08:27 -0400, Alvaro Herrera wrote: > > I have access to sf.net -- and I just finished updating it. > > I have no idea what you did http://sourceforge.net/projects/pgsql -- Devrim GÜNDÜZ , RHCE PostgreSQL Replication, Consulting, Custom Development, 24x7 support Managed Services, Shared and Dedicated Hosting Co-Authors: plPHP, ODBCng - http://www.commandprompt.com/
Attachment
On Fri, 2008-06-13 at 11:51 -0400, Jonathan Fuerth wrote: > On Fri, Jun 13, 2008 at 11:35 AM, Alvaro Herrera > <alvherre@commandprompt.com> wrote: > > Jonathan Fuerth wrote: > > Now that's a useful suggestion. > > > >> I have no clout in this community, so I won't ask for access to edit Not yet. > >> the freshmeat entry. But I would be happy to write and maintain the > >> script! Now you do. It is all about meritocracy. Thank you very much for stepping up. We need all hands we can get. Sincerely, Joshua D. Drake
Devrim, > > I have no idea what you did > > http://sourceforge.net/projects/pgsql That's Sourceforge, not Freshmeat. Different. Freshmeat still hasn't been updated because *only* Marc and Neil have access. Who do we contact to get more people access? -- --Josh Josh Berkus PostgreSQL @ Sun San Francisco
On Fri, 2008-06-13 at 10:29 -0700, Josh Berkus wrote: > That's Sourceforge, not Freshmeat. Different. Josh, could you please re-read what I wrote? I said "I don't have access to FM, but I have access to SF, and I updated it". -- Devrim GÜNDÜZ , RHCE PostgreSQL Replication, Consulting, Custom Development, 24x7 support Managed Services, Shared and Dedicated Hosting Co-Authors: plPHP, ODBCng - http://www.commandprompt.com/
Attachment
I'm working on Freshmeat, sorry for delay... ---- Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) Email . scrappy@hub.org MSN . scrappy@hub.org Yahoo . yscrappy Skype: hub.org ICQ . 7615664 On Fri, 13 Jun 2008, Devrim G�ND�Z wrote: > On Fri, 2008-06-13 at 10:29 -0700, Josh Berkus wrote: >> That's Sourceforge, not Freshmeat. Different. > > Josh, could you please re-read what I wrote? I said "I don't have access > to FM, but I have access to SF, and I updated it". > > -- > Devrim GÜNDÜZ , RHCE > PostgreSQL Replication, Consulting, Custom Development, 24x7 support > Managed Services, Shared and Dedicated Hosting > Co-Authors: plPHP, ODBCng - http://www.commandprompt.com/ >
At 1:29p -0400 on Fri, 13 Jun 2008, Josh Berkus wrote: >> http://sourceforge.net/projects/pgsql Hmm, given that patches /do/ come out every so often, and people will inevitably have downloaded Postgres before that time, would it also be prudent to offer the different patches since the initial release? All I see currently are the most recent versions of each release. Perhaps only offer the most recent version, and all previous patches? > That's Sourceforge, not Freshmeat. Different. I don't know Freshmeat, but looking at the web page, http://freshmeat.net/projects/pgsql/ it looks like there is an About section, as well as a bunch of links. In lieu of the nagging program to keep it up to date, what's wrong with mentioning in the about section something along the lines of "See the project home page for the most recent release and server patches" ? Kevin
Joshua D. Drake wrote: > > > On Fri, 2008-06-13 at 11:35 -0400, Bruce Momjian wrote: > > Gavin M. Roy wrote: > > > I'd rather step up to maintain it than let it go. It's a 5 minute change, 5 > > > times a year? If I can get access, I will commit to keeping it up to date. > > > > Fine. I don't care who does it but last time we saw this problem a few > > months ago the community was assured Freshmeat would be kept up to date, > > but it wasn't. > > > > Exactly where is the release checklist that shows we should update > > Freshmeat? > > http://wiki.postgresql.org/wiki/ReleasePrep Oh, that shows the problem more clearly. The items are: Day After Announce * Update Sourceforge * Update Freshmeat * Update #postgresql topic I did the IRC topic because I just usually grab that when I see the announcement, but others could do it as well. I am an admin on Sourceforge for the project but I have never updated it, and I see we never posted 8.3.1 there. Freshmeat has a similar problem. Who can take ownership of that list and has access to all those sites? If not, it is again not going to be done regularly. -- Bruce Momjian <bruce@momjian.us> http://momjian.us EnterpriseDB http://enterprisedb.com + If your life is a hard drive, Christ can be your backup. +
Marc G. Fournier wrote: > > I'm working on Freshmeat, sorry for delay... Can you please give access to it to someone else, so that they can help you in keeping it updated? -- Alvaro Herrera http://www.CommandPrompt.com/ The PostgreSQL Company - Command Prompt, Inc.
bruce@momjian.us (Bruce Momjian) writes: >> http://wiki.postgresql.org/wiki/ReleasePrep > > Oh, that shows the problem more clearly. The items are: > > Day After Announce > > * Update Sourceforge > * Update Freshmeat > * Update #postgresql topic > > I did the IRC topic because I just usually grab that when I see the > announcement, but others could do it as well. I am an admin on > Sourceforge for the project but I have never updated it, and I see we > never posted 8.3.1 there. Freshmeat has a similar problem. > > Who can take ownership of that list and has access to all those sites? > If not, it is again not going to be done regularly. FYI, I added the wikipedia page on PostgreSQL to this list, and updated that page, too. (It was still on 8.3.1) -- (reverse (concatenate 'string "ofni.secnanifxunil" "@" "enworbbc")) http://cbbrowne.com/info/wp.html "Parentheses? What parentheses? I haven't noticed any parentheses since my first month of Lisp programming. I like to ask people who complain about parentheses in Lisp if they are bothered by all the spaces between words in a newspaper..." -- Kenny Tilton <tilt@liii.com>
On Fri, Jun 13, 2008 at 2:35 PM, Bruce Momjian <bruce@momjian.us> wrote: > > Oh, that shows the problem more clearly. The items are: > > Day After Announce > > * Update Sourceforge > * Update Freshmeat > * Update #postgresql topic > [...] > > Who can take ownership of that list and has access to all those sites? > If not, it is again not going to be done regularly. > I would be happy to write, host, and maintain a facility for verifying that the freshmeat entry reflects the newest release on the FTP and Web sites, and emails the people responsible when it doesn't. Based on my experience, I believe this will ensure regular, timely updates to the freshmeat listing. In addition, I'm happy to volunteer to take responsibility for actually updating the entry in a timely manner. But I fully understand if you don't want to entrust someone you've never heard of with that responsibility. That's fair. I'm getting mixed messages from this thread about whether this nag script is desirable (Hi Alvaro and Joshua; thanks for welcoming me). If you want it, I am eager to make the contribution. I can do it tonight. If you don't want it, I'd prefer to know that before putting in the effort. :) -Jonathan
Jonathan, > I'm getting mixed messages from this thread about whether this nag > script is desirable (Hi Alvaro and Joshua; thanks for welcoming me). > If you want it, I am eager to make the contribution. I can do it > tonight. If you don't want it, I'd prefer to know that before putting > in the effort. :) It would be way keen. I'm pretty sure WWW will be happy to host it on community servers. Do you think you could make it extensible? So that we could have it check SF.net, Wikipedia, etc.? --Josh
On Fri, Jun 13, 2008 at 5:19 PM, Josh Berkus <josh@agliodbs.com> wrote: > > It would be way keen. I'm pretty sure WWW will be happy to host it on > community servers. > Great; I'll do it! Hosting is not a problem for me; I have a server of my own colocated on a reliable network, and an account on another machine in a carrier hotel. But if it's easy to get it hosted on a PostgreSQL-controlled server, all the better. > Do you think you could make it extensible? So that we could have it check > SF.net, Wikipedia, etc.? Wikipedia is doable for sure. The "edit this page" URL never changes and it's very easy to separate out the wiki content in the textarea from the surrounding HTML. sf.net is probably also fine, but it's fairly dynamic and there's no clear delineation between content and boilerplate. However, just looking for the string "8.3.3" in the HTML of the download page turns up 5 matches and no false positives. The moral is, "boneheaded web scraping works far better than you would hope or expect." :) -Jonathan
Hi again, I've finished the version alerter. It finds the latest version number at http://www.postgresql.org/ftp/source/, then verifies that version number appears in a configurable list of web pages. It's easy to add new ones. Right now, I've got it up and running against the PostgreSQL entries on freshmeat, SourceForge, and Wikipedia. Here's what a notification looks like: --- From: daemon@(no spam please) To: fuerth@(no spam please) To: other@(no spam please) Subject: Version check alert! Date: Sat, 14 Jun 2008 00:34:39 -0400 (EDT) Latest version: 8.3.3 freshmeat: needs update! SourceForge: up to date Wikipedia: up to date --- If all sites are up to date, no email is sent. If at least one site is out of date, an email like the above is sent to a configurable list of people. If the check itself fails for some reason (HTTP error, scrape fails to find latest version, ...) then it will email a different configurable list of people (especially me so I can fix it). So... who would like to be added to which list(s), and how frequently should I run the check? -Jonathan
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 - --On Saturday, June 14, 2008 00:04:05 -0400 Jonathan Fuerth <fuerth@sqlpower.ca> wrote: > Hi again, > > I've finished the version alerter. It finds the latest version number > at http://www.postgresql.org/ftp/source/, then verifies that version > number appears in a configurable list of web pages. It's easy to add > new ones. > > Right now, I've got it up and running against the PostgreSQL entries > on freshmeat, SourceForge, and Wikipedia. > > Here's what a notification looks like: > > --- > > From: daemon@(no spam please) > To: fuerth@(no spam please) > To: other@(no spam please) > Subject: Version check alert! > Date: Sat, 14 Jun 2008 00:34:39 -0400 (EDT) > > Latest version: 8.3.3 > > freshmeat: needs update! > SourceForge: up to date > Wikipedia: up to date > > --- > > If all sites are up to date, no email is sent. > > If at least one site is out of date, an email like the above is sent > to a configurable list of people. > > If the check itself fails for some reason (HTTP error, scrape fails to > find latest version, ...) then it will email a different configurable > list of people (especially me so I can fix it). > > So... who would like to be added to which list(s), and how frequently > should I run the check? Add me for freshmeat ... Thx - -- Marc G. Fournier Hub.Org Hosting Solutions S.A. (http://www.hub.org) Email . scrappy@hub.org MSN . scrappy@hub.org Yahoo . yscrappy Skype: hub.org ICQ . 7615664 -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (FreeBSD) iEYEARECAAYFAkhTRUEACgkQ4QvfyHIvDvO9awCgjcMBYby4ZItMz/grJeR/vGzu wJIAoI8CPbIMwqhPuH37IVBaWLHCg2Je =/uPm -----END PGP SIGNATURE-----
Jonathan Fuerth wrote: > Hi again, > If the check itself fails for some reason (HTTP error, scrape fails to > find latest version, ...) then it will email a different configurable > list of people (especially me so I can fix it). > > So... who would like to be added to which list(s), and how frequently > should I run the check? pgsql-www, say --- once a month? Joshua D. Drake P.S. Great work! > > -Jonathan >
Joshua D. Drake wrote: > Jonathan Fuerth wrote: >> Hi again, > >> If the check itself fails for some reason (HTTP error, scrape fails to >> find latest version, ...) then it will email a different configurable >> list of people (especially me so I can fix it). >> >> So... who would like to be added to which list(s), and how frequently >> should I run the check? > > pgsql-www, say --- once a month? What would be cool is if it could track the version RSS feed from www.postgresql.org to figure out when it needs to go out and check the others... //Magnus
On Sat, Jun 14, 2008 at 2:25 AM, Magnus Hagander <magnus@hagander.net> wrote: > > What would be cool is if it could track the version RSS feed from > www.postgresql.org to figure out when it needs to go out and check the > others... > Well, which one is most likely to be correct? If the RSS feed needs to be updated manually after the new release is added to the FTP site, maybe it would make more sense to add the RSS to the list of "pages" to verify for up-to-dateness. The primary source of information should be correct by default (which is why I'm looking at FTP directory names--assuming the release exists iff you can download the source code). But I'm assuming the RSS is not generated automatically and the content at http://www.postgresql.org/ftp/source/ is. I could very well have the wrong idea about how everything fits together. Either way, I like your idea of optimizing the checker not to check all the other pages unless the primary source's version number changes. Remembering the previous maximum version number would also allow warnings such as "maximum version is now 8.3.2; last time I checked it was 8.3.3." -Jonathan
On Sat, Jun 14, 2008 at 1:25 PM, Jonathan Fuerth <fuerth@sqlpower.ca> wrote: > On Sat, Jun 14, 2008 at 2:25 AM, Magnus Hagander <magnus@hagander.net> wrote: >> >> What would be cool is if it could track the version RSS feed from >> www.postgresql.org to figure out when it needs to go out and check the >> others... >> > > Well, which one is most likely to be correct? If the RSS feed needs to > be updated manually after the new release is added to the FTP site, > maybe it would make more sense to add the RSS to the list of "pages" > to verify for up-to-dateness. The primary source of information should > be correct by default (which is why I'm looking at FTP directory > names--assuming the release exists iff you can download the source > code). The RSS feed is the definitive source. We preload binaries and source tarballs onto the ftp site a few days before the release, so we don't want your script bugging us prior to the actual launch otherwise it'll end up getting forgotten. The data source for the RSS feed is one of the things that gets updated *at* release time. Oh, and I would suggest running it daily. If the folks updating the sites cannot handle same-day updates, or on the odd occasion ignoring a couple of emails until they can do the update, then they're probably not the most appropriate people for handling this kind of task anyway. -- Dave Page EnterpriseDB UK: http://www.enterprisedb.com
On Sat, Jun 14, 2008 at 9:22 AM, Dave Page <dpage@pgadmin.org> wrote: > On Sat, Jun 14, 2008 at 1:25 PM, Jonathan Fuerth <fuerth@sqlpower.ca> wrote: >> On Sat, Jun 14, 2008 at 2:25 AM, Magnus Hagander <magnus@hagander.net> wrote: >>> >>> What would be cool is if it could track the version RSS feed from >>> www.postgresql.org to figure out when it needs to go out and check the >>> others... >>> >> >> Well, which one is most likely to be correct? If the RSS feed needs to >> be updated manually after the new release is added to the FTP site, >> maybe it would make more sense to add the RSS to the list of "pages" >> to verify for up-to-dateness. The primary source of information should >> be correct by default (which is why I'm looking at FTP directory >> names--assuming the release exists iff you can download the source >> code). > > The RSS feed is the definitive source. We preload binaries and source > tarballs onto the ftp site a few days before the release, so we don't > want your script bugging us prior to the actual launch otherwise it'll > end up getting forgotten. The data source for the RSS feed is one of > the things that gets updated *at* release time. Thanks for the clarification, Dave! I will poll the RSS feed instead of the FTP directory listing. I'm going to assume every title in the feed is a release number. This is true now; is it a safe assumption in the medium-to-long run? > Oh, and I would suggest running it daily. If the folks updating the > sites cannot handle same-day updates, or on the odd occasion ignoring > a couple of emails until they can do the update, then they're probably > not the most appropriate people for handling this kind of task anyway. I tend to agree with you there. Once all the secondary sources are up-to-date, it's only going to start nagging again when a new release comes out. Better to get the reminder starting the next day rather than at the end of the week or month. -Jonathan
On Sat, Jun 14, 2008 at 5:16 PM, Jonathan Fuerth <fuerth@sqlpower.ca> wrote: > Thanks for the clarification, Dave! I will poll the RSS feed instead > of the FTP directory listing. I'm going to assume every title in the > feed is a release number. This is true now; is it a safe assumption in > the medium-to-long run? Yeah, I think so. The purpose of that feed really is just for the version numbers. -- Dave Page EnterpriseDB UK: http://www.enterprisedb.com
Dave Page wrote: > On Sat, Jun 14, 2008 at 5:16 PM, Jonathan Fuerth <fuerth@sqlpower.ca> wrote: >> Thanks for the clarification, Dave! I will poll the RSS feed instead >> of the FTP directory listing. I'm going to assume every title in the >> feed is a release number. This is true now; is it a safe assumption in >> the medium-to-long run? > > Yeah, I think so. The purpose of that feed really is just for the > version numbers. Yes, that is the idea. The only real reason there is a text on the items at all is that it's required for the feed to validate :-) It's there for automatic scrpits to be able to rely on, so we're not going to change the format of the title unless there's a *very* compelling reason. //magnus
Marc, So, can we also see about getting someone else authorized on Freshmeat? We can take Neil off, if necessary; he's hardly more available than you. Good other candidates are me, Robert, and Magnus. -- Josh Berkus PostgreSQL @ Sun San Francisco
Alvaro Herrera wrote: > Marc G. Fournier wrote: >> I'm working on Freshmeat, sorry for delay... > > Can you please give access to it to someone else, so that they can help > you in keeping it updated? > O.k. this is getting ridiculous, the freshmeat entry is still not updated. Whoever has access, please get in touch with others on the web team to make sure we are actually being responsible about the entry. Joshua D. Drake
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 - --On Thursday, June 12, 2008 22:36:40 -0400 Bruce Momjian <bruce@momjian.us> wrote: > Josh Berkus wrote: >> Check it out, folks: >> >> http://freshmeat.net/ > > And Freshmeat has 8.3.0! I thought we were going to keep this up to > date, and if not, we were going to remove it. Well, we are not keeping > it up to date! Actually, I had updated it last release, apparently, for some reason, the update was rejected ... I just re-updated for 8.3.3, and it went through fine ... don't believe I did anything different with the last release then I've ever done, or did this last time *shrug* - -- Marc G. Fournier Hub.Org Hosting Solutions S.A. (http://www.hub.org) Email . scrappy@hub.org MSN . scrappy@hub.org Yahoo . yscrappy Skype: hub.org ICQ . 7615664 -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (FreeBSD) iEYEARECAAYFAkhV9iMACgkQ4QvfyHIvDvNBLwCfcclZj3nbT0TUUlLQPSFhNk+9 SvQAnRAc/yZWLcmKyOlnRCOTJb4mYRqS =9/rV -----END PGP SIGNATURE-----
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Is there a way of removing 'branches'? Or do we want to list all the old versions that we are still supporting? Can you have 'multiple stable'? - --On Friday, June 13, 2008 15:10:18 +0930 Shane Ambler <pgsql@Sheeky.Biz> wrote: > Bruce Momjian wrote: >> Josh Berkus wrote: >>> Check it out, folks: >>> >>> http://freshmeat.net/ >> >> And Freshmeat has 8.3.0! I thought we were going to keep this up to >> date, and if not, we were going to remove it. Well, we are not keeping >> it up to date! >> >> Updated: Wed, Mar 5th 2008 22:40 UTC (3 months, 10 days ago) >> > Actually it seems quite messy. > > The download links for the tarball etc point to 8.3.0 > > The branches listed have Dev as 8.0.0rc1 and stable as 8.2.4 > > > > > -- > > Shane Ambler > pgSQL (at) Sheeky (dot) Biz > > Get Sheeky @ http://Sheeky.Biz > > -- > Sent via pgsql-advocacy mailing list (pgsql-advocacy@postgresql.org) > To make changes to your subscription: > http://www.postgresql.org/mailpref/pgsql-advocacy - -- Marc G. Fournier Hub.Org Hosting Solutions S.A. (http://www.hub.org) Email . scrappy@hub.org MSN . scrappy@hub.org Yahoo . yscrappy Skype: hub.org ICQ . 7615664 -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (FreeBSD) iEYEARECAAYFAkhV95YACgkQ4QvfyHIvDvNFsQCgini+yJQ/dDTx3J5DsHAQyFte l8YAoNPBu9JkrMJQgDrDNeOAPbOVsEsQ =P7qT -----END PGP SIGNATURE-----
On Mon, Jun 16, 2008 at 02:12:03AM -0300, Marc G. Fournier wrote: > Actually, I had updated it last release, apparently, for some reason, the > update was rejected ... I just re-updated for 8.3.3, and it went through fine > ... don't believe I did anything different with the last release then I've ever > done, or did this last time *shrug* This doesn't address the need to have more people than just you with that access. A -- Andrew Sullivan ajs@commandprompt.com +1 503 667 4564 x104 http://www.commandprompt.com/
Josh Berkus wrote:
> Marc,
>
> So, can we also see about getting someone else authorized on Freshmeat? We
> can take Neil off, if necessary; he's hardly more available than you. Good
> other candidates are me, Robert, and Magnus.
Marc, two people volunteered to also be admins on the PostgreSQL
Freshmeat page, but I saw no reply from you and they are not listed:
http://freshmeat.net/projects/pgsql/
We need to have more than one admin for that, as Josh suggested.
--
Bruce Momjian <bruce@momjian.us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ If your life is a hard drive, Christ can be your backup. +
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Josh was added as Admin a few weeks ago ... which you would know if you had taken to actually check the entry :) - --On Wednesday, July 16, 2008 21:31:10 -0400 Bruce Momjian <bruce@momjian.us> wrote: > Josh Berkus wrote: >> Marc, >> >> So, can we also see about getting someone else authorized on Freshmeat? We >> can take Neil off, if necessary; he's hardly more available than you. Good >> other candidates are me, Robert, and Magnus. > > Marc, two people volunteered to also be admins on the PostgreSQL > Freshmeat page, but I saw no reply from you and they are not listed: > > http://freshmeat.net/projects/pgsql/ > > We need to have more than one admin for that, as Josh suggested. > > -- > Bruce Momjian <bruce@momjian.us> http://momjian.us > EnterpriseDB http://enterprisedb.com > > + If your life is a hard drive, Christ can be your backup. + - -- Marc G. Fournier Hub.Org Hosting Solutions S.A. (http://www.hub.org) Email . scrappy@hub.org MSN . scrappy@hub.org Yahoo . yscrappy Skype: hub.org ICQ . 7615664 -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (FreeBSD) iEYEARECAAYFAkh+qbgACgkQ4QvfyHIvDvO1UQCg2oMzv+3yXW3VXFzXLttk4FwF CrsAoOjqF0SXHGdNyK0uoYEKsK9IJw8g =CYQm -----END PGP SIGNATURE-----
Marc G. Fournier wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > > Josh was added as Admin a few weeks ago ... which you would know if you had > taken to actually check the entry :) Oh, I see it now. Sorry. :-( -- Bruce Momjian <bruce@momjian.us> http://momjian.us EnterpriseDB http://enterprisedb.com + If your life is a hard drive, Christ can be your backup. +