It might also be interesting/useful to throw in things like high level package layouts and (for C binary packages) standards on compilers to be used.

Maybe even co-ordinating releases between sub-projects where there are heavy inter-relationships?

Mind you, it'd be so easy to fall into the trap of over-regulating if we started down that path.

Cheers,
   Berin

Ted Leung wrote:

One thing that's on my list of things for the PMC to tackle is the issue of
releases.

The most important item to me is that we start to use the ASF mirroring
standards so that we can take
the load off of the ASF machines and spread it around.

----- Original Message -----
From: "Christian Geisert" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, February 25, 2003 7:12 AM
Subject: Re: Guidelines for releases




Berin Lautenbach wrote:


Peoples,

The xml-security project has recently grown somewhat in terms of
committers, and the question has come up around putting a process in
place around releases. When, how, pre-requisites, shakedown testing


etc.


Is there anything we can "lift" from the other projects in terms of such
a process, rather than re-inventing the wheel?


http://cvs.apache.org/viewcvs.cgi/*checkout*/ant/ReleaseInstructions
http://cvs.apache.org/viewcvs.cgi/*checkout*/xml-batik/MAINTAIN

And FOP should have something soon too ..

Christian


--------------------------------------------------------------------- In case of troubles, e-mail: [EMAIL PROTECTED] To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]





---------------------------------------------------------------------
In case of troubles, e-mail:     [EMAIL PROTECTED]
To unsubscribe, e-mail:          [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]







--------------------------------------------------------------------- In case of troubles, e-mail: [EMAIL PROTECTED] To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]



Reply via email to