[Owncloud] Contributing

[Victor Dubiniuk]

Hi Nathan,

yes, it is correct.

All features and bug fixes go into the master branch so you need to clone
master first.
Thus, you need to use the master branch to validate bug report first.
For a new feature make your clone of master and start a new branch:

git checkout -b my-new-feature-name master


You will be switched to the my-new-feature-name branch automatically. If
you need switch back to the master for recent commits use

git checkout master


Good Luck.

----
Victor Dubiniuk

On Tue, Jun 19, 2012 at 11:11 PM, Nathan Anderson <nanderson at sum-ware.com>wrote:

> Hello all,
>
> I'm new to ownCoud and Git, and now that I've done some reading I want to
> make sure I understand the process of contributing.  That way I can set up
> my development environment correctly.
>
>  * If I have a simple fix to an existing bug report - attach a patch to
> the ticket
>  * If I have a new bug report and a fix - Create the ticket and attach a
> patch
>
>  * If I'm creating a new feature:
>    - Create a local clone of "master" (or other branch being modified)
>    - Code the feature until it is complete and known bugs are resolved
>    - Make a new clone of "master" on Gitorious
>    - Push local code to the clone on Gitorious
>    - Request a merge from Gitorious clone to "master"
>
> Does those processes sound correct?
>
> Thanks,
> Nathan
>
>
> _______________________________________________
> Owncloud mailing list
> Owncloud at kde.org
> https://mail.kde.org/mailman/listinfo/owncloud
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/owncloud/attachments/20120620/b5ee0810/attachment.html>