From dev-return-25134-apmail-directory-dev-archive=directory.apache.org@directory.apache.org Thu May 08 12:38:47 2008 Return-Path: Delivered-To: apmail-directory-dev-archive@www.apache.org Received: (qmail 85711 invoked from network); 8 May 2008 12:38:47 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 8 May 2008 12:38:47 -0000 Received: (qmail 33973 invoked by uid 500); 8 May 2008 12:38:48 -0000 Delivered-To: apmail-directory-dev-archive@directory.apache.org Received: (qmail 33924 invoked by uid 500); 8 May 2008 12:38:48 -0000 Mailing-List: contact dev-help@directory.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "Apache Directory Developers List" Delivered-To: mailing list dev@directory.apache.org Received: (qmail 33913 invoked by uid 99); 8 May 2008 12:38:48 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 08 May 2008 05:38:48 -0700 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of elecharny@gmail.com designates 72.14.220.156 as permitted sender) Received: from [72.14.220.156] (HELO fg-out-1718.google.com) (72.14.220.156) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 08 May 2008 12:37:53 +0000 Received: by fg-out-1718.google.com with SMTP id 19so675463fgg.3 for ; Thu, 08 May 2008 05:38:15 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:reply-to:user-agent:mime-version:to:subject:references:in-reply-to:content-type:content-transfer-encoding:sender; bh=GO/0WicRJo6U1pAmnfXbQbKnspZGnw66upDgoOm8n3c=; b=DzLiVdCwTAm0wb+ihuGKn5SxtP2FfdDOlWcO1MioeoSvtAtZtTYqu+RYlBjEDbfUuLluC4X0ecL0BYnS2LhynY4HwW4Cy3KDMgsJjGliMuMvOtGj49qPTKPaXfI873tPFIRnbXwdKeZ+gqoF731/ZSGcSb0e9GgueYixjVcZraQ= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:reply-to:user-agent:mime-version:to:subject:references:in-reply-to:content-type:content-transfer-encoding:sender; b=Eh0VUU0jJIS84NBidHFL6WvxF7Sq9FX+7RfSk35hjnyF5EF2bnhlUDfsQZoXDuZvoCn8y5ygverT/mNiYq3O9MBCoEwmJlfQxWJG0bDxyZn9FLjyeppFFuRIC1rUWdhBDChM6XXo7h/7Bk3tD6Jluft7TDU16XGHFkeWr+ymi00= Received: by 10.86.26.11 with SMTP id 11mr3968718fgz.23.1210250295105; Thu, 08 May 2008 05:38:15 -0700 (PDT) Received: from ?192.168.0.2? ( [82.66.216.176]) by mx.google.com with ESMTPS id e20sm3068468fga.7.2008.05.08.05.38.09 (version=TLSv1/SSLv3 cipher=RC4-MD5); Thu, 08 May 2008 05:38:11 -0700 (PDT) Message-ID: <4822F42D.406@apache.org> Date: Thu, 08 May 2008 14:38:05 +0200 From: Emmanuel Lecharny Reply-To: elecharny@apache.org User-Agent: Thunderbird 2.0.0.14 (X11/20080505) MIME-Version: 1.0 To: Apache Directory Developers List Subject: Re: [ApacheDS] Replaced trunks with bigbang References: In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Sender: Emmanuel Lecharny X-Virus-Checked: Checked by ClamAV on apache.org Ersin Er wrote: > Hi, > > I suggest we do not have such "giant" branches as bigbang. This is the first time in 4 years we are working on such a branch. It takes longer than expected, as we were supposed to have finished with it back in february. Obviously we were too optimistic. The idea is to close this branch as soon as the JNDI removal will be over. > I think it may prevent some developers working on the project, at > least it may make people think twice with what they are doing (in a > stressful manner). There is always a working trunk, in which developpers can work. We are merging from time to time trunk with bigbang, and occasionaly, we replace trunk with bigbang (this is the third time we did it yesturday). So for people not working on bigbang, trunk is the place, and trunk is 100% guaranted to compile (ok, 99.9% ;) Bigbang is nothing more than a branch, all in all ... > Instead of trying to keep trunk perfectly building, we can always work > on the trunk and avoid merging problems; I don't think that's a viable option. Some of our users are currently maintaining some patches on their own, against trunk, just because we are not fast enough to fix all the existing bugs, or to apply their patches. If we can't offer at least a stable trunk to them, then we are in trouble, IMO. > and we can sometimes (svn) tag the trunk when it perfectly builds and > makes sense as a whole. So people can be referred to those tagged > versions if they want to go with the edge version of the server. Every single revision is a tag everyone can use to refer to a working version. Do we need to define a Tag directory, as we have branches and releases directories ? That could be an option, sure. I'm truly sorry about all the problem this big refactoring is causing, and I wish they will be fixed asap. We are really doing our best to get rid of bigbang as fast as possible ... Thanks ! -- -- cordialement, regards, Emmanuel Lécharny www.iktek.com directory.apache.org