Keeping source code

[HengJ]

Guys, I'm doing an assignment regarding FileZilla, and I really need your help.

Here are some of the tasks given,

-How do contributors keep their source code;
-How individual contributors retrieve the latest, or a specific version, of the source
code;
-How do they consolidate the modified code to generate the executables;
-What are the processes for them to release the software;
-How does one reports bug in their software;
-How do they keep the records of bugs;
-How do they prioritize their bug fixes or feature development;
-Ways to improve the workflow;

Can anyone help me in answering any of the questions

[botg]

Contributors as opposed to main developers?

Contributed source is posted in form of patches in FileZilla's Trac: http://trac.filezilla-project.org/, same for bug reports.

[HengJ]

Contributors as opposed to main developers?

Contributed source is posted in form of patches in FileZilla's Trac: http://trac.filezilla-project.org/, same for bug reports.

Thanks botg! This help me alots. How about the ways they keep their source code? I can't find any information in how they backup their source code

[botg]

While I don't know exactly how contributors keep their source, I'm certain that they at least check the source of FileZilla out of our Subversion repository. See https://filezilla-project.org/sourcecode.php

[HengJ]

How about the process of releasing their software ?

[HengJ]

and also how they prioritize the bug fixes ?

[botg]

To get a proposed contribution released, a main developer reviews the patch and, should everything be okay with it, it gets applied to the repository to be released with the next version.

There's no policy on how contributors prioritize bug fixes.