We are talking about components (applications) that are good and nobody complains about. Code that is being used by our users. Code that is being evaluated and contributors work on to improve it. And this is left out of releases? Crazy....
If that were to be the policy, we could also start to chuck out humanres, marketing, cmssite, parts of accounting. And the rest not mentioned... Release branches and trunk are good for contributors to work on the code and such (bug fixes, improvements). Using it as a source to base a production environment upon is up to the users. It should not be the thing this project advocates and promotes. We have a responsibility to cary out. Not only to our users, but also the ASF. If you want to change the way we work, start working on a proposal that will find consensus within the community. And by forcing an implementation methodology upon us that doesn't have the consensus of the community, that leads to more misunderstanding (within the user part of the community) and more work for the rest. Pierre Smits *ORRTIZ.COM <http://www.orrtiz.com>* Services & Solutions for Cloud- Based Manufacturing, Professional Services and Retail & Trade http://www.orrtiz.com On Thu, Nov 13, 2014 at 12:38 PM, Jacopo Cappellato < jacopo.cappell...@hotwaxmedia.com> wrote: > In the past the ASF Board asked to the OFBiz PMC to fix the release > strategy of the project by providing officially voted release files thru > the ASF mirrors: at that time we were pushing the users to get the trunk. > Officially asking the user to use a release branch would be better than the > trunk but would bring back similar concerns: an official vote is required > to publish a product to the outside of the project in order to guarantee > License free issues etc... > > On Thu, Nov 13, 2014 at 11:38 AM, Jacques Le Roux < > jacques.le.r...@les7arts.com> wrote: > > > Hi, > > > > In a recent user ML thread http://markmail.org/message/ivjocjr2ull7lwqe > I > > suggested we could propose our users to use a release branch strategy > > rather than downloaded packages. > > And that we could expose this way of doing in our download page, or > maybe > > better with a link to an explaining page (in details) in the wiki. > > > > I know it's not the recommended way of doing at the ASF. But we all know > > the OFBiz differences when compared with other TLPs which are mostly > libs, > > and even mostly jars. > > Most of us are actually using this way in their custom projects and I > have > > a feeling it would not only help our users but also us to support them. > > > > What do you think? > > > > Jacques > > > > >
