Thanks for the help! -Eric
On 8/24/11 6:27 PM, Steve Swinsburg wrote:
Hi, We are ramping up our work on uPortal and as such we are uncovering some issues that we have fixed locally but would like to contribute back. We are using uPortal 3.2.4 and that is tracked via this branch in SVN: https://source.jasig.org/uPortal/branches/rel-3-2-patches/ In previous projects, there was a strict policy that fixes must first go to trunk, be verified, then merged back to the branches. However since trunk is uPortal 4 which has been restructured and quite a lot of things changed, would it be reasonable that minor fixes go directly to the 3.2.x branch without appearing in trunk? We have no capacity to run up an instance of uP trunk and then to merge back to the branch as, given the restructure, it will most likely be required to be a manual merge or not applicable. If it's ok to commit directly to the branch, I can commit fixes as we come across them. They will all be tested. cheers, Steve
smime.p7s
Description: S/MIME Cryptographic Signature
