Return-Path: X-Original-To: apmail-ofbiz-dev-archive@www.apache.org Delivered-To: apmail-ofbiz-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 52BC917BAF for ; Thu, 23 Oct 2014 17:46:55 +0000 (UTC) Received: (qmail 62743 invoked by uid 500); 23 Oct 2014 17:46:55 -0000 Delivered-To: apmail-ofbiz-dev-archive@ofbiz.apache.org Received: (qmail 62712 invoked by uid 500); 23 Oct 2014 17:46:55 -0000 Mailing-List: contact dev-help@ofbiz.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@ofbiz.apache.org Delivered-To: mailing list dev@ofbiz.apache.org Received: (qmail 62683 invoked by uid 99); 23 Oct 2014 17:46:54 -0000 Received: from mx1-us-east.apache.org (HELO mx1-us-east.apache.org) (54.164.171.186) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 23 Oct 2014 17:46:54 +0000 Received: from mx1-us-east.apache.org (localhost [127.0.0.1]) by mx1-us-east.apache.org (ASF Mail Server at mx1-us-east.apache.org) with ESMTP id BD29143869 for ; Thu, 23 Oct 2014 17:46:54 +0000 (UTC) Received: by mx1-us-east.apache.org (ASF Mail Server at mx1-us-east.apache.org, from userid 111) id B1FFB43864; Thu, 23 Oct 2014 17:46:54 +0000 (UTC) X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on mx1-us-east.apache.org X-Spam-Level: X-Spam-Status: No, score=0.0 required=10.0 tests=URIBL_BLOCKED autolearn=disabled version=3.4.0 Received: from smtp.artifact-software.com (modemcable202.79-37-24.static.videotron.ca [24.37.79.202]) by mx1-us-east.apache.org (ASF Mail Server at mx1-us-east.apache.org) with ESMTP id 206DA4386B for ; Thu, 23 Oct 2014 17:46:53 +0000 (UTC) Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp.artifact-software.com (Postfix) with ESMTP id CC47B6A657F for ; Thu, 23 Oct 2014 13:45:51 -0400 (EDT) X-Virus-Scanned: amavisd-new at artifact-software.com Received: from smtp.artifact-software.com ([127.0.0.1]) by localhost (smtp.artifact-software.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PsYH4PDkdFp6 for ; Thu, 23 Oct 2014 13:45:51 -0400 (EDT) Received: from [192.168.3.170] (unknown [192.168.3.170]) by smtp.artifact-software.com (Postfix) with ESMTP id 887E06A657E for ; Thu, 23 Oct 2014 13:45:51 -0400 (EDT) Message-ID: <54493ECD.6020201@artifact-software.com> Date: Thu, 23 Oct 2014 13:45:49 -0400 From: Ron Wheeler Reply-To: rwheeler@artifact-software.com Organization: Artifact Software User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0 MIME-Version: 1.0 To: dev@ofbiz.apache.org Subject: Re: specialpurpose in R13.07 demo References: <53887963.6060104@les7arts.com> <2826EDBC-52C8-4EB8-BB93-DC204A31E114@hotwaxmedia.com> <3F3E977D-D938-4046-A64E-E01AB2BB7C9D@hotwaxmedia.com> <5448EF7F.80507@les7arts.com> <5449132C.5060304@les7arts.com> <54491AB9.2030700@artifact-software.com> <54491FDF.70304@les7arts.com> <6BC29674-175E-4F5F-841E-952217643F09@gmail.com> In-Reply-To: <6BC29674-175E-4F5F-841E-952217643F09@gmail.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-Virus-Scanned: ClamAV using ClamSMTP I was referring to "real" customers that are paying OFBiz contributors like you, real money to get them set up using OFBiz. On 23/10/2014 12:30 PM, Pierre @GMail wrote: > Is it a good thing to not regard the ofbiz user as a customer? > > Regards, > > Pierre > > Sent from my iPhone > >> On 23 okt. 2014, at 17:33, Jacques Le Roux wrote: >> >> >> Le 23/10/2014 17:11, Ron Wheeler a écrit : >>> On 23/10/2014 10:39 AM, Jacques Le Roux wrote: >>>> Le 23/10/2014 15:01, Jacopo Cappellato a écrit : >>>>> On Oct 23, 2014, at 2:07 PM, Jacques Le Roux wrote: >>>>> >>>>>> I agree about the idea, but this applies only to releases or checked out code. Because there are no ways for users to enable/disable a component in demos, moreover demos are shared. >>>>> Could you please explain the above sentence? I don't understand the meaning of it. >>>> Your idea of disabling some specialpurpose component can't be applied in R13.07 demo until we decide which component should be disabled in trunk. >>>> In the meantime we should keep the current state (ie all specialpurpose components present in trunk should be available in R13.07 demo) >>> If they are in the demo they should be in the release. >> Actually the specialpurpose components are in the R13.07 demos because they can be there. But they are not maintained in the R13.07 branch (but ecommerce) only in trunk. >> >>> As you can guess, I am troubled about the relation between releases and the trunk and demos in OFBiz. >> Would you prefer to not have the specialpurpose components in R13.07 demo? >> >>> It is a bit odd and certainly goes against most product release strategies wherein the current release is the recommended download and carries whatever warranty that the project offers in terms of testing and rapidity of bug fixes and the trunk is usually called something that includes"nightly build" and "unstable" in the name and comes with no warranty and a warning about using it at your own risk. >>> >>> Demos should be of the latest release and should be stable and have a fixed functionality that can be documented in the wiki and marketing pages. >> They are, just that they use the branch instead of the packaged releases. For R13.07 (current stable) there is an exception, because I thought it was better to have the specialpurpose components available. This is what Jacopo contests >> >>> It could be maintained by the documentation team once it is set up since it should not require any technical skills to keep working and fed with demo data. >>> >>> >>> If the developers need a test site based on the nightly build, they should be free to set up as many combinations of configurations as they require and can support to be sure that the trunk still works but this should not be the public demo or even be called a "demo". >> It's also, there are no official mention of the trunk demo, it's only a developers thing. >> >>> Of course, this only works if a release is actually a Release and the team stands behind it and uses it when establishing new customers. >> We have no customers, only users >> >> Jacques >> >>> Does anyone have an opinion about the gap between 13.07.01 and what the main SI companies are getting from using the trunk instead. >>> Would a monthly release pattern reduce this gap to a point where it would be possible to use the official Release as the actual release? >>> >>>> I hope it's more clear >>>> >>>> Jacques >>>> >>>>> Thanks, >>>>> >>>>> Jacopo >>> -- Ron Wheeler President Artifact Software Inc email: rwheeler@artifact-software.com skype: ronaldmwheeler phone: 866-970-2435, ext 102