xml-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ted Leung" <twle...@sauria.com>
Subject Re: Guidelines for releases
Date Wed, 26 Feb 2003 20:57:24 GMT
I think that package layouts and stuff are up to the sub-projects.

Co-ordination between the subprojects on releases would be good, if the
subprojects want to get together on this, the PMC can be a place where the
coordination can happen.  Again, I don't think this should be legislated.

The mirroring thing is different because it involves how we use the ASF
resources.  Our hardware and network bandwidth are donations, so its
important to use them as wisely as possible.  In the past the XML site was
one of the worst bandwidth hogs due to all the graphics on the old home
page.  The new Forrest generated page is helping that a lot.   Mirroring is
something we can do to conserve resources.

Ted
----- Original Message -----
From: "Berin Lautenbach" <berin@ozemail.com.au>
To: <general@xml.apache.org>
Sent: Wednesday, February 26, 2003 1:28 AM
Subject: Re: Guidelines for releases


> 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" <christian.geisert@isu-gmbh.de>
> >To: <general@xml.apache.org>
> >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:     webmaster@xml.apache.org
> >>To unsubscribe, e-mail:          general-unsubscribe@xml.apache.org
> >>For additional commands, e-mail: general-help@xml.apache.org
> >>
> >>
> >>
> >
> >
> >---------------------------------------------------------------------
> >In case of troubles, e-mail:     webmaster@xml.apache.org
> >To unsubscribe, e-mail:          general-unsubscribe@xml.apache.org
> >For additional commands, e-mail: general-help@xml.apache.org
> >
> >
> >
> >
>
>
>
> ---------------------------------------------------------------------
> In case of troubles, e-mail:     webmaster@xml.apache.org
> To unsubscribe, e-mail:          general-unsubscribe@xml.apache.org
> For additional commands, e-mail: general-help@xml.apache.org
>


---------------------------------------------------------------------
In case of troubles, e-mail:     webmaster@xml.apache.org
To unsubscribe, e-mail:          general-unsubscribe@xml.apache.org
For additional commands, e-mail: general-help@xml.apache.org


Mime
View raw message