Using CodePlex - A Complete Novice/Beginners Guide?
I've always been curious of this, but as everyone on here has been so helpful I thought I would ask - In the coming weeks I'd be very keen on helping add features / suggestions to Umbraco via codeplex but have no idea how the process works?
Just create an account on Codeplex and you're set. Once registered, you can add work items, add comments, suggest features, blablabla...
Core team picks up those requests (either bugs or features) and either reject or accept those. If accepted, it's most likely to be taken care of in a future version.
If you plan on doing actual coding, then you probably won't have commit permissions now. Then just create your changes, and submit them as a patch. Then the core team can merge it with the trunk code.
Hate to bring this up again... But just been having a look around and the patch part is still *Hazy*... Lets say I find a problem in a project, do I upload just the files I made the changes to or the entire soltuion? Also there is a little box that says related to work items?
Are work items actually items in the Issue Tracker section? And therefore I use the issue # as a reference? If not what the heck is a work item?
Thank you please ;) ... Oh and Merry Xmas everyone and happy new year if you are in an advanced time zone!
Using CodePlex - A Complete Novice/Beginners Guide?
I've always been curious of this, but as everyone on here has been so helpful I thought I would ask - In the coming weeks I'd be very keen on helping add features / suggestions to Umbraco via codeplex but have no idea how the process works?
Just create an account on Codeplex and you're set. Once registered, you can add work items, add comments, suggest features, blablabla...
Core team picks up those requests (either bugs or features) and either reject or accept those. If accepted, it's most likely to be taken care of in a future version.
Cheers,
/Dirk
If you plan on doing actual coding, then you probably won't have commit permissions now. Then just create your changes, and submit them as a patch. Then the core team can merge it with the trunk code.
Awesome thank you :)
Hate to bring this up again... But just been having a look around and the patch part is still *Hazy*... Lets say I find a problem in a project, do I upload just the files I made the changes to or the entire soltuion? Also there is a little box that says related to work items?
Are work items actually items in the Issue Tracker section? And therefore I use the issue # as a reference? If not what the heck is a work item?
Thank you please ;) ... Oh and Merry Xmas everyone and happy new year if you are in an advanced time zone!
I would say just attach the files that you have changed. And yes, the workitem is from the issuetracker.
is working on a reply...