> Anyway I feel your pain, I couldn't find anything meeting my requirements either. > I even considered building it myself, using ZF of course :)
That is where I think I could be heading :-) - Robert rcastley wrote: > > Hi Karol, > > How do you handle issue/bug tracking? > > In Bugzilla I can choose the Product and then the component etc. > > More research tonight has unveiled the following projects: > > 1) Redmine (seems to be like Trac but written in Ruby). Not used Ruby > or Rails so not comfortable with this from a systems managament POV. > See Item 3! > 2) I used Gforge on the Mambo project, they now over an Advanced Version: > http://gforgegroup.com/es/download.php > 3) Retrospectiva - but look at the 'Quick'???? Install guide: > http://retrospectiva.org/wiki/Quick%20install. Now I know why I love > PHP > ;-) > > I think I am now getting myself down to Gforge AS or Trac. > > Why is nothing ever easy, eh? > > - Robert > > -----Original Message----- > From: Karol Grecki [mailto:kgre...@gmail.com] > Sent: 21 December 2008 21:46 > To: fw-general@lists.zend.com > Subject: Re: [fw-general] What do you use to manage your ZF projects? > > > Robert > > I had the same problem over a year ago and settled for Trac. It > doesn't support multiple projects but we use milestones for it e.g. > "project A sprint 1".... It integrates really well with Subversion and > there's a lot of plugins extending its functionality. It may still be > your best bet if you don't find anything matching all your > requirements. > > Karol > > > rcastley wrote: >> >> Hi, >> >> Just curious here. I/we currently use Bugzilla & CVS, no formal >> wiki but I do have a MediaWiki used for somethings. >> >> I am looking for a solution that fits all, so the obvious choices are >> 'Trac' >> like. >> >> My problem is that I need a solution that will support multiple projects. >> (Trac doesn't score well in this area.) >> >> Bugzilla is used by multiple PHP, Java & C/C++ products. CVS is used >> only by PHP developers the 'others' use VSS. >> MediaWiki is used for 'sparse' documentation. >> >> >> My gripes with the current setup: >> >> Bugzilla - v. slow and ugly but it fitted the bill at the time. >> CVS - I like, no love, CVS but I know that there are better solutions >> out there but am concerned about migration etc. >> MediaWiki - Probably too much of an overkill for what we need and it >> is not that easy to configured, extend etc. >> >> I now that the ZF team uses JIRA, Confluence etc but I have a budget >> of £0/$0 :-) and don't qualify for the OS licenses. >> >> So ... I would be interested on the views of others of a 'one hat >> fits all' >> solution that can handle multiple projects. >> The solution needs to offer Issues/Bug tracking and Wiki at a minimum. >> Integration with SCM not important but if it does it great. >> >> I would prefer a PHP based solution but happy to consider others i.e. >> Ruby, >> Perl, Java etc. >> >> - Robert >> > > -- View this message in context: http://www.nabble.com/What-do-you-use-to-manage-your-ZF-projects--tp21118310 p21120113.html Sent from the Zend Framework mailing list archive at Nabble.com. ________________________________________________________________________ This email has been scanned for all known viruses by the MessageLabs Email Security Service and the Macro 4 plc internal virus protection system. ________________________________________________________________________ ________________________________________________________________________ This email has been scanned for all known viruses by the MessageLabs Email Security Service and the Macro 4 plc internal virus protection system. ________________________________________________________________________
