From forrest-dev-return-6969-apmail-xml-forrest-dev-archive=xml.apache.org@xml.apache.org Tue Sep 09 06:24:11 2003 Return-Path: Delivered-To: apmail-xml-forrest-dev-archive@www.apache.org Received: (qmail 85118 invoked from network); 9 Sep 2003 06:24:11 -0000 Received: from daedalus.apache.org (HELO mail.apache.org) (208.185.179.12) by minotaur-2.apache.org with SMTP; 9 Sep 2003 06:24:11 -0000 Received: (qmail 81402 invoked by uid 500); 9 Sep 2003 06:23:11 -0000 Delivered-To: apmail-xml-forrest-dev-archive@xml.apache.org Received: (qmail 81262 invoked by uid 500); 9 Sep 2003 06:23:09 -0000 Mailing-List: contact forrest-dev-help@xml.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: forrest-dev@xml.apache.org Delivered-To: mailing list forrest-dev@xml.apache.org Received: (qmail 81140 invoked from network); 9 Sep 2003 06:23:08 -0000 Received: from unknown (HELO mail.spm.de) (62.96.197.7) by daedalus.apache.org with SMTP; 9 Sep 2003 06:23:08 -0000 Received: from hermes.spmtechnologies.com (magelan.spm.de [62.96.197.131]) by mail.spm.de (Postfix) with ESMTP id 8B43838B44 for ; Tue, 9 Sep 2003 08:23:16 +0200 (CEST) X-MIMEOLE: Produced By Microsoft Exchange V6.0.6249.0 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Subject: Release Process... Date: Tue, 9 Sep 2003 08:23:16 +0200 Message-ID: <4291C06A54E398479B852264EA22303121C4A3@hermes.spmtechnologies.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Mixed-namespace support (Re: cvs commit: ...) Thread-Index: AcN2YMDHBF69F+x8RvCF85IDH9jMCQAODYfQ From: "Andre Anneck" To: X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N Hi dev-team, in order to circumvent such conflicts I recommend using CVS branches = (early branching): 1. Announce Code-Freeze 2. Open branch RC_0-5 =3D> Now people can continue work on MAIN, without interference of the = release branch 3. Start tagging inside the branch to test release candidates (Maybe = Tag-Names =3D=3D Jira Release-Names) =3D> Bugs fixed in release branch need merge into MAIN branch, ok thats = the overhead work you have using this approach 4. Once satisfied with stability of RC_05, do the final TAG and produce = the release artifacts. Just my 2EUR's ;), Take care, Andr=E9 _________________________________ Software Development Andre Anneck=20 Tel +49 30 55115-305 Fax +49 30 55115-143 andre.anneck@spmtechnologies.com SPM Technologies Deutschland GmbH An den Treptowers 1 12435 Berlin, Germany www.spmtechnologies.com -----Urspr=FCngliche Nachricht----- Von: Jeff Turner [mailto:jefft@apache.org] Gesendet: Dienstag, 9. September 2003 01:27 An: forrest-dev@xml.apache.org Betreff: Mixed-namespace support (Re: cvs commit: ...) On Mon, Sep 08, 2003 at 01:48:15PM -0000, nicolaken@apache.org wrote: > nicolaken 2003/09/08 06:48:15 >=20 > Modified: . status.xml > = src/resources/fresh-site/src/documentation/content/xdocs > site.xml > src/resources/fresh-site forrest.properties > src/resources/skins/common/xslt/html document2html.xsl > Added: = src/resources/fresh-site/src/documentation/content/xdocs/samples > multiple-namespaces.xml html-sample.html > Log: > > In the common skin and derivatives, allow xhtml-namespaced = elements in > document elements to passthrough when rendering to html. > Added also example in the forrest seed (fresh-site). > ... > -#forrest.validate.xdocs.excludes=3Dsite.xml > = +forrest.validate.xdocs.excludes=3Dsite.xml,samples/multiple-namespaces.x= ml Does all this stuff (and @class) *have* to happen a few hours before 0.5 gets released? Couldn't it wait 24 hours for 0.6, when we have a decent multi-namespace validation system[1] in place? Same for @class attributes -- I don't care whether it's good or bad; I don't want to even consider it for 0.5. We can do a 0.5.1 any time. --Jeff