[scribus-dev] Developers' checklist for new features

[mrdocs]

On Monday 20 April 2009 09:30:56 am Daniel Clemente wrote:
> Hi, I need to know which steps are needed to add a feature to Scribus. For
> instance:
>
> - should I provide translations for the texts I add? In which languages?
> - who should design the new icons used, if any?
> - which indentation style should I use?
> - should the code pass any tests?
> - which variable types should I use? (uint, ...)
> - should I adapt the documentation? In which languages?
> - which branch should I work on? (I know this: 1.3.5)
> - should I port my patch to other branches?
> - should I send patches to the mailing list or to the bug tracker?
> - are there any special steps to do when a release date is near?
>
>   Therefore I'm creating a new page in the wiki to hold this developers'
> information; at the moment only the questions are there, not the answers.
> http://wiki.scribus.net/index.php/How_to_file_a_bug_report
>
>   To the more experienced developers: Could you please place some hints
> there?
>
>
Great idea. I have bookmarked it to work on it soon.


> Thanks,
>   Daniel
>
>
> _______________________________________________
> scribus-dev mailing list
> scribus-dev at lists.scribus.net
> http://lists.scribus.net/mailman/listinfo/scribus-dev


Peter