On Tue, Dec 1, 2009 at 5:46 PM, Alain O'Dea <alain.o...@gmail.com> wrote:
> On 2009-12-01, at 5:36 PM, Vlad Dumitrescu wrote:
>
> Hi guys,
>
> I'd like to ask everyone that wants to contribute to the project to
> read and use the recommendations at
> http://wiki.github.com/erlide/erlide about how to do fixes and how to
> deliver them. This would help me a lot when checking the fixes and
> when merging them into the main repository.
>
> The main thing to remember is that it's each contributor's job to make
> sure that the fix merges cleanly to the upstream.
>
> Thanks for the cooperation.
>
> BTW, do you think we should adopt the same model for contributing to
> erlide as the OTP team uses for erlang? The model is the same as the
> git project and the linux kernel use. See
> http://wiki.github.com/erlang/otp/branches for details.
> The difference is small, the meaning of the branches in the main repo
> is different and there is a "proposed updates" branch to gather all
> suggestions.
>
> regards,
> Vlad
>
>
> I like the simple model described at
> http://wiki.github.com/erlide/erlide/contributing-a-bug-fix
>
Some more clarity on which milestones to work on and what the
New/Accepted/Test Status means in Assembla would be very helpful. At work
"New" means don't touch. I am guessing after observing the tickets for a
while that New means free to take and Accepted means someone is already
working on it.
------------------------------------------------------------------------------
Join us December 9, 2009 for the Red Hat Virtual Experience,
a free event focused on virtualization and cloud computing.
Attend in-depth sessions from your desk. Your couch. Anywhere.
http://p.sf.net/sfu/redhat-sfdev2dev
_______________________________________________
Erlide-devel mailing list
Erlide-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/erlide-devel
