User forums > General (but related to Code::Blocks)

Development report/checkout/patch/review workflow

(1/2) > >>

techtonik:
I wonder is it really convenient for people here to follow development process?

Let me portray a bug workflow if a bug is encountered on horizon
1. spot the bug and discuss it in a nightly thread
2. describe new species in insectopedia at berlios
3. add bug-care instructions to patch tracker at berlios
4. wait for the next nightly to check patch works as expected
5. check SVN for third-party additions to the patch
6. get back to comment and/or close bugreport

Why the question? The major annoyance is that for each issue you need to remember 4 links: forum, bugtracker, patchtracker, WebSVN. They are not interconnected in any way and you need to store them manually. Especially annoying is that bugtracker and patchtracker are separate. You also need 2 accounts, one of which tend to expire from time to time and that's annoying too.

Have anybody considered moving development to integrated SVN+bugtracker+patchtracker system (like Trac or Google Code) where issues and commits are interlinked and very easy to review and follow? Which system was the most promising and what reasons were against the move (if any)?

MortenMacFly:

--- Quote from: techtonik on August 28, 2008, 01:25:33 pm ---Have anybody considered moving development to integrated SVN+bugtracker+patchtracker system (like Trac or Google Code)

--- End quote ---
Yes - the first. Hence the move takes time as it is combined with porting patches / bugs from BerliOS to Trac. Seems there is no *good* fully automised "solution". So stay tuned.

techtonik:
If you already have something done and do not mind against a *good enough* "solution" then perhaps I can help with Trac scripting?

mandrav:

--- Quote from: techtonik on August 28, 2008, 05:36:32 pm ---If you already have something done and do not mind against a *good enough* "solution" then perhaps I can help with Trac scripting?

--- End quote ---

Thanks for volunteering :)
What do you have in mind when you say "trac scripting"?

techtonik:
Scripting is almost the same as developing when your project is written in scripting language, except that the amount of code you write is significantly lower as you mostly use existing functionality to solve some specific (often one-time) task. Anything needed for importing data, linking to issues, parsing data and customizing plugins for specific installation.

Navigation

[0] Message Index

[#] Next page