Re: Let's create a release team
От | Dan Langille |
---|---|
Тема | Re: Let's create a release team |
Дата | |
Msg-id | 3DF5AE31.6599.1FB06C14@localhost обсуждение исходный текст |
Ответ на | Re: Let's create a release team (Tom Lane <tgl@sss.pgh.pa.us>) |
Ответы |
Re: Let's create a release team
Re: Let's create a release team |
Список | pgsql-hackers |
On 10 Dec 2002 at 0:56, Tom Lane wrote: > "Dan Langille" <dan@langille.org> writes: > > Is the process documented? Any set procedure? Who knows how to do > > it? > > Er ... nope, nope, the core bunch ... Sounds like we need to do a brain dump then. I just happen to have some equipment left over from "The Matrix".... > > If these things are not documented, they should be. > > Most of the undocumented details of the release process are in the > heads of Marc Fournier and Bruce Momjian. If either of them falls off > the end of the earth, we have worse troubles than whether we remember > how to do a release On a project, anyone is replaceable. And anyone might leave for any number of reasons. If they do, the affect upon the project will be minimized by having the major processes documented. > --- for example: Marc owns, runs, and pays for the > postgresql.org servers. Is the cvs repo mirrored? > (Me, I just hack code, so I'm replaceable.) Yeah, yeah, stop being humble... ;) > But if you want to try to document the process better, there are some > details written down already (eg, src/tools/RELEASE_CHANGES) and I'm > sure Marc and Bruce would cooperate in writing down more. That's a good start. It looks like a list of things easily forgotten but if forgotten, make us look bad. -- Dan Langille : http://www.langille.org/
В списке pgsql-hackers по дате отправления: