Re: How to coordinate web team for security releases?
От | Devrim GUNDUZ |
---|---|
Тема | Re: How to coordinate web team for security releases? |
Дата | |
Msg-id | 1170712415.3056.25.camel@laptop.gunduz.org обсуждение исходный текст |
Ответ на | Re: How to coordinate web team for security releases? (Magnus Hagander <magnus@hagander.net>) |
Ответы |
Re: How to coordinate web team for security releases?
Re: How to coordinate web team for security releases? |
Список | pgsql-www |
Hello, On Mon, 2007-02-05 at 20:52 +0100, Magnus Hagander wrote: > > What I need is a non-public list for this, so that I can ask for web > > site changes 3-4 days ahead without it becoming a news item. > > Will that really help? In this case, the files were uploaded to the > ftp site long before you made your post to the -www list... Does it > really make a difference? Here is what I have been thinking about this for a while: * As now, an announce to -packagers about the new release. * Upload the new tarballs to a private area (instead of public FTP site) so that only packagers and other related people can download them to build the packages, etc. * Win32 binaries, source tarballs and RPMs will be uploaded to another directory (not to FTP site in developer.postgresql.org) before the release. * After we are done with all of them, (that takes 2 days only), we'll move this directory to FTP site and wait for propagation. Does it look good? -- Devrim GÜNDÜZ PostgreSQL Replication, Consulting, Custom Development, 24x7 support Managed Services, Shared and Dedicated Hosting Co-Authors: plPHP, ODBCng - http://www.commandprompt.com/
В списке pgsql-www по дате отправления: