Author Topic: Development report/checkout/patch/review workflow  (Read 6854 times)

Offline techtonik

  • Multiple posting newcomer
  • *
  • Posts: 24
Development report/checkout/patch/review workflow
« on: August 28, 2008, 01:25:33 pm »
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)?


Offline MortenMacFly

  • Administrator
  • Lives here!
  • *****
  • Posts: 9508
Re: Development report/checkout/patch/review workflow
« Reply #1 on: August 28, 2008, 04:44:25 pm »
Have anybody considered moving development to integrated SVN+bugtracker+patchtracker system (like Trac or Google Code)
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.
Compiler logging: Settings->Compiler & Debugger->tab "Other"->Compiler logging="Full command line"
C::B Manual: http://www.codeblocks.org/docs/main_codeblocks_en.html
C::B FAQ: http://wiki.codeblocks.org/index.php?title=FAQ

Offline techtonik

  • Multiple posting newcomer
  • *
  • Posts: 24
Re: Development report/checkout/patch/review workflow
« Reply #2 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?

Offline mandrav

  • Project Leader
  • Administrator
  • Lives here!
  • *****
  • Posts: 4291
    • Code::Blocks IDE
Re: Development report/checkout/patch/review workflow
« Reply #3 on: August 28, 2008, 09:16:24 pm »
If you already have something done and do not mind against a *good enough* "solution" then perhaps I can help with Trac scripting?

Thanks for volunteering :)
What do you have in mind when you say "trac scripting"?
Be patient!
This bug will be fixed soon...

Offline techtonik

  • Multiple posting newcomer
  • *
  • Posts: 24
Re: Development report/checkout/patch/review workflow
« Reply #4 on: August 29, 2008, 07:58:41 am »
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.

Offline MortenMacFly

  • Administrator
  • Lives here!
  • *****
  • Posts: 9508
Re: Development report/checkout/patch/review workflow
« Reply #5 on: August 29, 2008, 08:26:48 am »
What do you have in mind when you say "trac scripting"?
I believe he means the script to convert "BerliOS into Trac"... probably?!

@techtonik: You do know, that we use a scripting engine in C::B, right?! ;-)
Compiler logging: Settings->Compiler & Debugger->tab "Other"->Compiler logging="Full command line"
C::B Manual: http://www.codeblocks.org/docs/main_codeblocks_en.html
C::B FAQ: http://wiki.codeblocks.org/index.php?title=FAQ

Offline techtonik

  • Multiple posting newcomer
  • *
  • Posts: 24
Re: Development report/checkout/patch/review workflow
« Reply #6 on: August 29, 2008, 10:59:37 am »
Sorry for confusion. Indeed, I am speaking about exporting data from Berlios and importing them into Trac. About scripting engine in C::B I've heard some rumors, but haven't seen it yet.

Offline techtonik

  • Multiple posting newcomer
  • *
  • Posts: 24
Re: Development report/checkout/patch/review workflow
« Reply #7 on: September 12, 2008, 04:15:18 pm »

Offline MortenMacFly

  • Administrator
  • Lives here!
  • *****
  • Posts: 9508
Re: Development report/checkout/patch/review workflow
« Reply #8 on: September 13, 2008, 01:07:21 pm »
As Berlios seems to be based on SourceForge code, these links can help you migrate data:

http://bitten.edgewall.org/wiki/TracImport
http://trac.edgewall.org/browser/trunk/contrib/sourceforge2trac.py
http://svn.python.org/projects/tracker/roundup-src/scripts/import_sf.py
http://project.juiblex.co.uk/hg/sf2bz?cmd=summary;style=gitweb

http://developer.berlios.de/export/?group_id=5358

(Berlios export is limited to project admins only, so I couldn't test if these scripts work for CB)
...these are good ones.

@Yiannis: Is one of these the "tool" you are using?!
Compiler logging: Settings->Compiler & Debugger->tab "Other"->Compiler logging="Full command line"
C::B Manual: http://www.codeblocks.org/docs/main_codeblocks_en.html
C::B FAQ: http://wiki.codeblocks.org/index.php?title=FAQ

Offline mandrav

  • Project Leader
  • Administrator
  • Lives here!
  • *****
  • Posts: 4291
    • Code::Blocks IDE
Re: Development report/checkout/patch/review workflow
« Reply #9 on: September 13, 2008, 02:32:45 pm »
As Berlios seems to be based on SourceForge code, these links can help you migrate data:

http://bitten.edgewall.org/wiki/TracImport
http://trac.edgewall.org/browser/trunk/contrib/sourceforge2trac.py
http://svn.python.org/projects/tracker/roundup-src/scripts/import_sf.py
http://project.juiblex.co.uk/hg/sf2bz?cmd=summary;style=gitweb

http://developer.berlios.de/export/?group_id=5358

(Berlios export is limited to project admins only, so I couldn't test if these scripts work for CB)
...these are good ones.

@Yiannis: Is one of these the "tool" you are using?!

No, I wrote my own because those that I tested didn't work (either not satisfactory or not at all).
Be patient!
This bug will be fixed soon...