Re: Sourceforge PG release

Should we treat releases as projects, including pm's, taking care of
checklists while mitigating risks?

Note the "including a PM". One per release, tracking and delivering.
Community driven, public reporting.

I can help preparing a project template draft.

Gb.

2009/7/5, Bruce Momjian <bruce(at)momjian(dot)us>:
> Dave Page wrote:
>> On 7/5/09, Bruce Momjian <bruce(at)momjian(dot)us> wrote:
>> > Robert Treat wrote:
>> >> On Sunday 05 July 2009 06:22:42 Devrim G?ND?Z wrote:
>> >> > On Sun, 2009-07-05 at 11:32 +0300, Devrim G?ND?Z wrote:
>> >> > > > o Why do I not have release permissions for our project?
>> >> > >
>> >> > > You should
>> >> >
>> >> > Oops, I just saw that you were not granted permission for that.
>> >> > Fixed.
>> >>
>> >> This means we can start blaming Bruce for releases not getting put up,
>> >> right? :-D
>> >
>> > Perhaps. My big question is why we are doing this now, and not a few
>> > days ago. Updating external download sites was supposed to be on some
>> > checklist so we didn't have to fix this days after the official release.
>> > Where is it listed?
>> >
>>
>> http://wiki.postgresql.org/wiki/84WebTasks
>
> Thanks. Here is the line that I am interested in:
>
> 7/1 19:00 6/30 15:00 Update Freshmeat etc. Jonathan F.
> Josh & Devrim
>
> OK, so why wasn't this done? And who is Jonathan F.? Can we please
> spell out his full last name because if I don't know who he is, others
> don't as well. And Marc should be listed as a backup on that item, I
> think.
>
> --
> Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
> EnterpriseDB http://enterprisedb.com
>
> + If your life is a hard drive, Christ can be your backup. +
>
> --
> Sent via pgsql-www mailing list (pgsql-www(at)postgresql(dot)org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-www
>

--
Enviado desde mi dispositivo móvil