Does this solve ASF's issue about having users access the main servers?
What do you put on the mirrors and how do you stop users from accessing
the development SVN which is ASF's concern?
Ron
On 13/11/2014 1:55 PM, Jacques Le Roux wrote:
For the licence free issues (an other related stuff) we could put a
disclaimer in the wiki page where all alternatives would be explained
Jacques
Le 13/11/2014 12:38, Jacopo Cappellato a écrit :
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 <
[email protected]> wrote:
Hi,
In a recent user ML
threadhttp://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
--
Ron Wheeler
President
Artifact Software Inc
email: [email protected]
skype: ronaldmwheeler
phone: 866-970-2435, ext 102
