http://ci.apache.org/waterfall?show=ofbiz-trunkwill give you the last sucessful build from the trunk.
then you can create your mods and additions but doing an
ant create-component
that puts them in the hotdeploy.
this way you can update trunk and not effect your code.
then if you created test units in your components you can verify if your
code still works.
now if you don't what to go to all of that, then plan on using a release
which does not change except for bugs.
you would then have to watch the commit ml for updates and see if you ca
n use them.
my 2 cents.
=========================
BJ Freeman
http://bjfreeman.elance.comStrategic Power Office with Supplier Automation <
http://www.businessesnetwork.com/automation/viewforum.php?f=93>
Specialtymarket.com <
http://www.specialtymarket.com/>
Systems Integrator-- Glad to Assist
Chat Y! messenger: bjfr33man
Linkedin
<
http://www.linkedin.com/profile?viewProfile=&key=1237480&locale=en_US&trk=tab_pro>
Olivier Tremblay sent the following on 4/26/2010 10:31 AM:
> Hi people!
>
> I'd need some guidance towards which version of OFBiz to choose from. I have a few things to take into account:
>
> I'm a single developer, and will in due time be committed full-time by my boss to work on an OFBiz setup for the business. In my line of work I will be asked to:
>
> -Develop new features they would like
> -Enhance features they don't like
> -Adjust the interface to their needs
>
> So I see that there will be a new release branch. Should I use that in production, and use another instance reserved for development? Should I use trunk to provide my users with the bleeding edge version of OFBiz, or will that be far too unstable for their taste?
>
> Thank you!
>
Locked
