Return-Path: Delivered-To: apmail-cocoon-dev-archive@www.apache.org Received: (qmail 61768 invoked from network); 20 Apr 2004 13:51:14 -0000 Received: from daedalus.apache.org (HELO mail.apache.org) (208.185.179.12) by minotaur-2.apache.org with SMTP; 20 Apr 2004 13:51:14 -0000 Received: (qmail 74416 invoked by uid 500); 20 Apr 2004 13:51:06 -0000 Delivered-To: apmail-cocoon-dev-archive@cocoon.apache.org Received: (qmail 74356 invoked by uid 500); 20 Apr 2004 13:51:06 -0000 Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: dev@cocoon.apache.org Delivered-To: mailing list dev@cocoon.apache.org Received: (qmail 74339 invoked from network); 20 Apr 2004 13:51:05 -0000 Received: from unknown (HELO mail.s-und-n.de) (212.8.217.2) by daedalus.apache.org with SMTP; 20 Apr 2004 13:51:05 -0000 Received: from notes.sundn.de (ntsrv5.sundn.de [10.10.2.10]) by mail.s-und-n.de (postfix) with ESMTP id F27B419F59E for ; Tue, 20 Apr 2004 15:51:06 +0200 (CEST) Received: from hw0386 ([10.10.2.54]) by notes.sundn.de (Lotus Domino Release 6.5) with ESMTP id 2004042015440068-73712 ; Tue, 20 Apr 2004 15:44:00 +0200 From: "Carsten Ziegeler" To: Subject: RE: Proposal: release management guide (was Re: [RT] Versions) Date: Tue, 20 Apr 2004 15:53:35 +0200 Organization: S&N AG MIME-Version: 1.0 X-Mailer: Microsoft Office Outlook, Build 11.0.5510 In-Reply-To: <408522EC.80502@outerthought.org> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1409 Thread-Index: AcQm2OWYaDcdeba6TgKgIfesI5NP6wABOQMw X-MIMETrack: Itemize by SMTP Server on PBSN1/Systeme und Netzwerke(Release 6.5|September 26, 2003) at 20.04.2004 15:44:00, Serialize by Router on PBSN1/Systeme und Netzwerke(Release 6.5|September 26, 2003) at 20.04.2004 15:44:01, Serialize complete at 20.04.2004 15:44:01 Message-ID: Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii" 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 Marc Portier wrote: > here goes: > I see some difference between what I would call 'extension' > vs. 'usage' > compatibility > > I like the distinction and I totally agree with the vision of 'usage'. In my RT about versions I was only refering to the 'extension' are when it comes to incompatible changes. > > I currently don't think we have a release scheme that > supports one or the other: i.e. reality seems pretty much > like what Carsten is saying: > we just have 1,2,... 1004 (based on some gut feeling we seem > to be distributing those numbers over tripplets) > Yes, I think this is really the truth. And in reality things get very complicated as compatibility for Cocoon as a whole applies not only to what we develop but to most other projects we incorporate. We are - for example - very eager in updating to new releases of external libraries. So it happens, that we change from Xalan 2.4 to Xalan 2.6 between 2.1.3 and 2.1.4. (just a fictional sample). It's a major change for Xalan, so it's not required to be compatible. But if Cocoon or a users application relies on some things that have changed between 2.4 and 2.6, then Cocoon isn't compatible between 2.1.3 and 2.1.4 for them. And of course, they blame Cocoon (which isn't soo wrong). And in fact, these updates to the external libraries cause a lot of problems to users when they try to update from one version to another of Cocoon. So, what do we do with all these infos? Carsten