Ofbiz in production. Things that can't be fixed when you're in dev cycle for
into the main line for release if the user knew the next release was coming.
should be the basis for this. it should be a requirement to have a test
>From: "David E. Jones" <
[hidden email]>
>Reply-To: OFBiz Users / Usage Discussion <
[hidden email]>
>To: OFBiz Users / Usage Discussion <
[hidden email]>
>Subject: Re: [OFBiz] Users - SSL Setup
>Date: Fri, 6 Jan 2006 14:21:14 -0700
>
>
>On Jan 6, 2006, at 12:22 PM, Adrian Grealish wrote:
>
>>When are you planning a new release? not for the consulting arm for the
>>open source community remember collaboration is the way to success?
>
>You are correct that collaboration is the way to success, but it is not
>true that official releases increase collaboration. In fact, they _reduce_
>collaboration. OFBiz is still maturing and the limited resources are
>dedicated to development and maintenance of the software by various groups
>with various different, but all overlapping, priorities.
>
>The point of the Sequoia project that Si Chen has put together is to have
>a community that is more dedicated to maintaining point releases with bug
>fixes and what not done there and back-patched from the open source
>project. That's the idea anyway...
>
>For OFBiz the only real purpose for a release is: marketing! Users of
>OFBiz who take a release instead of keeping up to date during their
>development process CAN NOT effectively collaborate with the community or
>contribute to the project. They are using older code and not updating to
>get work that others do nor can they base their changes on the latest
>stuff, so it's just impossible to collaborate. They can sometimes
>contribute, but generally not as effectively, depending on what it is and
>how much it has changed since the date of the revision they are using.
>
>So, releases aren't a big priority for OFBiz right now. The project has
>gone, and to some extent is still going, through some MAJOR additions and
>until these settle down it doesn't make much sense and isn't easy or cheap
>to do a release (including the necessary testing and bug fixing, related
>marketing artifacts for new features and announcements and what not, and
>so on). Creating a binary is easy, that's not the issue, but just a binary
>isn't a very valuable release and is guaranteed to have more problems than
>we'd like and so it does more _harm_ than good...
>
>We are working on becoming an Apache project, though I don't know if that
>will go through or not. If it does we will most likely do a release in a
>few months to push things along there, and mostly for marketing purposes
>to help new people interested in the project get an idea of what's up. If
>they are doing development though and customizing OFBiz we will still
>encourage groups/people to NOT use the releases, but rather to keep up
>with SVN until they are ready to start their pre-production integration
>and user level testing.
>
>>Why can't a user search the mailing lists? I tried codecomments.com but
>>their search doesn't work either.
>
>This simply isn't up yet after the mailing list move though it will be up
>in the future.
>
>As with all things: if it is important enough to you to do something about
>it, then do so! That is how every single little detail in OFBiz is
>handled...
>
>-David