Re: Recommendation for how to handle workspace with "processing" contributions

[Tim Ruppert]

I've always kept a clean ofbiz-trunk with changes in them - which is where I create the patches from. Then in the individual projects that I'm working on, I maintain a set of patches that I must apply to the framework/applications area at least until the trunk gets updated with my patches. Then I've got the best of both worlds - the separate download where I maintain and build my patches as well as my project specific place where I wouldn't be creating my patches from.

Cheers,
Tim
--
Tim Ruppert
HotWax Media
http://www.hotwaxmedia.com

o:801.649.6594
f:801.649.6595

On Jul 31, 2009, at 4:47 PM, Bob Morley wrote:

Hope that helps - and if you have any other questions on exceptions to this rule, please feel free to ask some more Q's.

about how people handle their workspace while they are waiting for
contributions to be approved/rejected.


result in dependencies.


on how to manage this?  I am thinking about using Mylyn and the JIRA

...

Anyone have a better suggestion?
--
View this message in context: 
http://www.nabble.com/Recommendation-for-how-to-handle-workspace-with-%22processing%22-contributions-tp24764099p24764099.html
Sent from the OFBiz - Dev mailing list archive at Nabble.com.

While I have been working on Ofbiz for a while, I have not made a good enough effort to contribute back bug fixes and enhancements that I feel would be valuable to the product. I have started to do this, but I have a question I have created a few JIRAs and attached patch files to them for my changes. However, as I do more and more work I end up with more and more changes in my workspace that are updated. It will ultimately become very difficult to determine which files I should include in the next patch; moreover I may Does any non-contributor (or contributor for that matter) have a suggestion integration to relate the files. This does not help the patch generation

smime.p7s
Description: S/MIME cryptographic signature