Hi folks,
Let's create a release team. This strategy is one well established
in other projects and in industry. For lack of a better starting
reference, let me suggest http://www.freebsd.org/releng/charter.html
as a starting point for consideration. See also
http://www.freebsd.org/releng/in
"Dan Langille" <[EMAIL PROTECTED]> writes:
> Let's create a release team. This strategy is one well established
> in other projects and in industry. For lack of a better starting
> reference, let me suggest http://www.freebsd.org/releng/charter.html
> as a starting point for consideration. Se
On 9 Dec 2002 at 11:38, Tom Lane wrote:
> "Dan Langille" <[EMAIL PROTECTED]> writes:
> > Let's create a release team. This strategy is one well established
> > in other projects and in industry. For lack of a better starting
> > reference, let me suggest http://www.freebsd.org/releng/charter.htm
Hi Dan,
It's been mentioned a few times on the Advocacy and Marketing list that
we should put together a process for ensuring that all the parts
necessary for a release occur properly and smoothly.
***
Source code
- Initial packaging of the new releases' source code
Docs
- Confir
"Dan Langille" <[EMAIL PROTECTED]> writes:
> Is the process documented? Any set procedure? Who knows how to do
> it?
Er ... nope, nope, the core bunch ...
> Is 'core' the same as 'steering'?
Yes, the webpage takes some license here. 'core' is the most common
terminology for the-usual-suspect
Tom Lane wrote:
> as a result of their individual contributions). So ISTM such a
> reorganization would leave the core committee as a figurehead and make
> the release team into the effective new core.
I thought we were already only figureheads? ;-)
--
Bruce Momjian|
On 10 Dec 2002 at 0:56, Tom Lane wrote:
> "Dan Langille" <[EMAIL PROTECTED]> 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
"Dan Langille" <[EMAIL PROTECTED]> writes:
>> --- for example: Marc owns, runs, and pays for the
>> postgresql.org servers.
> Is the cvs repo mirrored?
Anyone running cvsup would have a complete copy of the source CVS,
I believe. It would be more troubling to reconstruct the mailing list
archive
On 10 Dec 2002 at 9:34, Tom Lane wrote:
> "Dan Langille" <[EMAIL PROTECTED]> writes:
> >> --- for example: Marc owns, runs, and pays for the
> >> postgresql.org servers.
>
> > Is the cvs repo mirrored?
>
> Anyone running cvsup would have a complete copy of the source CVS, I
> believe. It would
Dan Langille writes:
> On 10 Dec 2002 at 9:34, Tom Lane wrote:
> > Anyone running cvsup would have a complete copy of the source CVS, I
> > believe. It would be more troubling to reconstruct the mailing list
> > archives; I'm not sure that those are mirrored anywhere
> Do you mean the reposit
On Tue, 10 Dec 2002, Tom Lane wrote:
> "Dan Langille" <[EMAIL PROTECTED]> writes:
> >> --- for example: Marc owns, runs, and pays for the
> >> postgresql.org servers.
>
> > Is the cvs repo mirrored?
>
> Anyone running cvsup would have a complete copy of the source CVS,
> I believe. It would be mo
On Tuesday 10 December 2002 00:24, Justin Clift wrote:
> RPM's & SRPM's
> - Co-ordinate with Lamar to have these ready before the general
> announcement?
As I am merely a volunteer in this, the availability of RPMs is directly
impacted by my workload. There are several times during the year t
Dan Langille wrote:
> > 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 forgot
13 matches
Mail list logo
