You can subscribe to this list here.
2001 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(2) |
Dec
(11) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2002 |
Jan
(18) |
Feb
(17) |
Mar
(11) |
Apr
(12) |
May
(21) |
Jun
(76) |
Jul
(8) |
Aug
(156) |
Sep
(117) |
Oct
(67) |
Nov
(122) |
Dec
(134) |
2003 |
Jan
(170) |
Feb
(214) |
Mar
(121) |
Apr
(36) |
May
(25) |
Jun
(10) |
Jul
(13) |
Aug
(69) |
Sep
(3) |
Oct
(17) |
Nov
(2) |
Dec
(40) |
2004 |
Jan
(34) |
Feb
(50) |
Mar
(69) |
Apr
(10) |
May
(76) |
Jun
(126) |
Jul
(180) |
Aug
(32) |
Sep
(43) |
Oct
(31) |
Nov
(25) |
Dec
(21) |
2005 |
Jan
(23) |
Feb
(75) |
Mar
(32) |
Apr
(34) |
May
(23) |
Jun
(34) |
Jul
(25) |
Aug
(21) |
Sep
(31) |
Oct
(34) |
Nov
(6) |
Dec
(16) |
2006 |
Jan
(9) |
Feb
(19) |
Mar
(45) |
Apr
(64) |
May
(33) |
Jun
(29) |
Jul
(11) |
Aug
(24) |
Sep
(55) |
Oct
(24) |
Nov
(38) |
Dec
(40) |
2007 |
Jan
(47) |
Feb
(28) |
Mar
(89) |
Apr
(35) |
May
(58) |
Jun
(30) |
Jul
(103) |
Aug
(80) |
Sep
(57) |
Oct
(108) |
Nov
(45) |
Dec
(38) |
2008 |
Jan
(39) |
Feb
(45) |
Mar
(29) |
Apr
(46) |
May
(39) |
Jun
(20) |
Jul
(19) |
Aug
(38) |
Sep
(40) |
Oct
(49) |
Nov
(64) |
Dec
(31) |
2009 |
Jan
(20) |
Feb
(31) |
Mar
(28) |
Apr
(46) |
May
(45) |
Jun
(45) |
Jul
(32) |
Aug
(11) |
Sep
(34) |
Oct
(33) |
Nov
(40) |
Dec
(17) |
2010 |
Jan
(28) |
Feb
(55) |
Mar
(23) |
Apr
(78) |
May
(33) |
Jun
(11) |
Jul
(10) |
Aug
(12) |
Sep
(70) |
Oct
(89) |
Nov
(55) |
Dec
(33) |
2011 |
Jan
(33) |
Feb
(66) |
Mar
(33) |
Apr
(40) |
May
(20) |
Jun
(29) |
Jul
(199) |
Aug
(42) |
Sep
(76) |
Oct
(10) |
Nov
(29) |
Dec
(38) |
2012 |
Jan
(30) |
Feb
(52) |
Mar
(56) |
Apr
(25) |
May
(17) |
Jun
(93) |
Jul
(15) |
Aug
(19) |
Sep
(23) |
Oct
(78) |
Nov
(59) |
Dec
(2) |
2013 |
Jan
(62) |
Feb
(18) |
Mar
(12) |
Apr
(119) |
May
(47) |
Jun
(34) |
Jul
(34) |
Aug
(12) |
Sep
(69) |
Oct
(128) |
Nov
(14) |
Dec
(11) |
2014 |
Jan
(232) |
Feb
(62) |
Mar
(67) |
Apr
(165) |
May
(82) |
Jun
(54) |
Jul
(26) |
Aug
(70) |
Sep
(56) |
Oct
(59) |
Nov
(3) |
Dec
(16) |
2015 |
Jan
(9) |
Feb
(6) |
Mar
(2) |
Apr
(2) |
May
(3) |
Jun
(2) |
Jul
(1) |
Aug
(17) |
Sep
(6) |
Oct
(4) |
Nov
(2) |
Dec
(3) |
2016 |
Jan
(19) |
Feb
(5) |
Mar
(6) |
Apr
(3) |
May
(1) |
Jun
(10) |
Jul
(3) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
From: P R. <pa...@ma...> - 2014-10-18 23:09:44
|
Apparently your email address doesn't work correctly - at least (rather amusingly) google isn't allowing a google user to email another google user: Delivery to the following recipient failed permanently: dr...@ma... Technical details of permanent failure: Message rejected by Google Groups. Please visit http://mail.google.com/support/bin/answer.py?hl=en&answer=188131 to review our Bulk Email Senders Guidelines. ----- Original message ----- X-Received: by 10.180.85.102 with SMTP id g6mr8889617wiz.54.1413672671965; Sat, 18 Oct 2014 05:51:11 -0700 (PDT) Return-Path: <pa...@ma...> Received: from mail-wi0-f175.google.com (mail-wi0-f175.google.com. [209.85.212.175]) by mx.google.com with ESMTPS id r8si3539198wiy.73.2014.10.18.15.51.11 for <dr...@ma...> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sat, 18 Oct 2014 05:51:11 -0700 (PDT) Received-SPF: none (google.com: pa...@ma... does not designate permitted sender hosts) client-ip=209.85.212.175; Authentication-Results: mx.google.com; spf=neutral (google.com: pa...@ma... does not designate permitted sender hosts) smtp.mail=pa...@ma... Received: by mail-wi0-f175.google.com with SMTP id d1so4483466wiv.14 for <dr...@ma...>; Sat, 18 Oct 2014 05:51:11 -0700 (PDT) -----Original Message----- From: Damien Regad [mailto:dr...@ma...] Sent: 18 October 2014 23:23 To: Man...@li... Subject: [mantisbt-dev] 1.2.18 release Paul, As you know we have several open security issues including some fairly critical ones. I have fixes ready to go for the most recent ones, and to close the loop I want to release 1.2.18 as soon as possible. *I remind you that you owe us a series of security fixes since May*, and you agreed earlier this week on IRC [1] to send them to me via e-mail by Friday. It is now late Saturday (early Sunday actually), and I still haven't received anything from you. To be blunt: YOU ARE BLOCKING A SECURITY RELEASE This is really unprofressional. Please act responsibly, and put on hold some of the trivialities you've been working on for the past few weeks/months for the few minutes it will take to send me patches. And please don't give me any of that shit again about your SSH access. Damien [1] http://www.mantisbt.org/irclogs/mantisbt/2014/mantisbt.2014-10-15.log.html ---------------------------------------------------------------------------- -- Comprehensive Server Monitoring with Site24x7. Monitor 10 servers for $9/Month. Get alerted through email, SMS, voice calls or mobile push notifications. Take corrective actions from your mobile device. http://p.sf.net/sfu/Zoho _______________________________________________ mantisbt-dev mailing list man...@li... https://lists.sourceforge.net/lists/listinfo/mantisbt-dev |
From: P R. <pa...@ma...> - 2014-10-18 23:07:10
|
If I’m correct about what the issue is likely to be, the problem might actually be ‘worse’ in 1.3-dev – however unless I’m mistaken here: Unless you are saying that the INTERNAL and EXTERNAL path to mantis is different, it should be a case of setting $g_path to the final path: $g_path = $t_protocol . '://' . $t_host . $t_path; i.e. if you have mantis listening on http, with a loadbalancing reverse proxy in front running https, whilst Mantis will detect http://www.foo.com, if you set $g_path = https://www.foo.com in the config file that should work I believe. If you are saying that you use http://mantis.internal and www.foo.org <http://www.foo.org> depending on whether users are internal or external to the corporate network, then this might be more of an issue. Looking at the code, we seem to generate a mixture of absolute and relative links within a page in both 1.2 and 1.3 – the $g_path fix should be fine for the reverse proxy case, however, the absolute links will need to go to deal with the split-dns case. Paul From: Louis BAYLE [mailto:lba...@gm...] Sent: 18 October 2014 23:16 To: developer discussions Subject: Re: [mantisbt-dev] Mantis not working behind a reverse-proxy Yes, I can install a mantis 1.3-dev on our server and test it. I'm not sure I'll have time to do that next week, but I'll let you know. Louis BAYLE Tel: +33 (0)4.42.604.734 lba...@gm... <mailto:lba...@gm...> On Sat, Oct 18, 2014 at 11:55 PM, Paul Richards <gra...@bl... <mailto:gra...@bl...> > wrote: Are you able to test if the situation is any better with 1.3-dev? If this is an absolute vs relative link type issue, (which I’m guessing it is) I’m not sure if the situation is improved in 1.3 Paul From: Louis BAYLE [mailto: <mailto:lba...@gm...> lba...@gm...] Sent: 18 October 2014 22:44 To: developer discussions Subject: [mantisbt-dev] Mantis not working behind a reverse-proxy Is there a 'good patch' to fix this realy problematic bug in Mantis ? The patch I applied to our installation does not work very well. IMHO this is realy a critical bug. http://www.mantisbt.org/bugs/view.php?id=13056 http://www.mantisbt.org/bugs/view.php?id=9333 Louis BAYLE Tel: +33 (0)4.42.604.734 lba...@gm... <mailto:lba...@gm...> ------------------------------------------------------------------------------ Comprehensive Server Monitoring with Site24x7. Monitor 10 servers for $9/Month. Get alerted through email, SMS, voice calls or mobile push notifications. Take corrective actions from your mobile device. http://p.sf.net/sfu/Zoho _______________________________________________ mantisbt-dev mailing list man...@li... <mailto:man...@li...> https://lists.sourceforge.net/lists/listinfo/mantisbt-dev |
From: Damien R. <dr...@ma...> - 2014-10-18 22:23:31
|
Paul, As you know we have several open security issues including some fairly critical ones. I have fixes ready to go for the most recent ones, and to close the loop I want to release 1.2.18 as soon as possible. *I remind you that you owe us a series of security fixes since May*, and you agreed earlier this week on IRC [1] to send them to me via e-mail by Friday. It is now late Saturday (early Sunday actually), and I still haven't received anything from you. To be blunt: YOU ARE BLOCKING A SECURITY RELEASE This is really unprofressional. Please act responsibly, and put on hold some of the trivialities you've been working on for the past few weeks/months for the few minutes it will take to send me patches. And please don't give me any of that shit again about your SSH access. Damien [1] http://www.mantisbt.org/irclogs/mantisbt/2014/mantisbt.2014-10-15.log.html |
From: Louis B. <lba...@gm...> - 2014-10-18 22:16:57
|
Yes, I can install a mantis 1.3-dev on our server and test it. I'm not sure I'll have time to do that next week, but I'll let you know. Louis BAYLE Tel: +33 (0)4.42.604.734 lba...@gm... On Sat, Oct 18, 2014 at 11:55 PM, Paul Richards <gra...@bl...> wrote: > Are you able to test if the situation is any better with 1.3-dev? > > > > If this is an absolute vs relative link type issue, (which I’m guessing it > is) I’m not sure if the situation is improved in 1.3 > > > > Paul > > > > *From:* Louis BAYLE [mailto:lba...@gm...] > *Sent:* 18 October 2014 22:44 > *To:* developer discussions > *Subject:* [mantisbt-dev] Mantis not working behind a reverse-proxy > > > > Is there a 'good patch' to fix this realy problematic bug in Mantis ? > > The patch I applied to our installation does not work very well. > IMHO this is realy a critical bug. > > > http://www.mantisbt.org/bugs/view.php?id=13056 > http://www.mantisbt.org/bugs/view.php?id=9333 > > Louis BAYLE > Tel: +33 (0)4.42.604.734 > lba...@gm... > > > ------------------------------------------------------------------------------ > Comprehensive Server Monitoring with Site24x7. > Monitor 10 servers for $9/Month. > Get alerted through email, SMS, voice calls or mobile push notifications. > Take corrective actions from your mobile device. > http://p.sf.net/sfu/Zoho > _______________________________________________ > mantisbt-dev mailing list > man...@li... > https://lists.sourceforge.net/lists/listinfo/mantisbt-dev > > |
From: Paul R. <gra...@bl...> - 2014-10-18 21:55:28
|
Are you able to test if the situation is any better with 1.3-dev? If this is an absolute vs relative link type issue, (which I’m guessing it is) I’m not sure if the situation is improved in 1.3 Paul From: Louis BAYLE [mailto:lba...@gm...] Sent: 18 October 2014 22:44 To: developer discussions Subject: [mantisbt-dev] Mantis not working behind a reverse-proxy Is there a 'good patch' to fix this realy problematic bug in Mantis ? The patch I applied to our installation does not work very well. IMHO this is realy a critical bug. http://www.mantisbt.org/bugs/view.php?id=13056 http://www.mantisbt.org/bugs/view.php?id=9333 Louis BAYLE Tel: +33 (0)4.42.604.734 lba...@gm... <mailto:lba...@gm...> |
From: Louis B. <lba...@gm...> - 2014-10-18 21:44:14
|
Is there a 'good patch' to fix this realy problematic bug in Mantis ? The patch I applied to our installation does not work very well. IMHO this is realy a critical bug. http://www.mantisbt.org/bugs/view.php?id=13056 http://www.mantisbt.org/bugs/view.php?id=9333 Louis BAYLE Tel: +33 (0)4.42.604.734 lba...@gm... |
From: Louis B. <lba...@gm...> - 2014-10-16 21:56:26
|
Hi Paul, First of all, I fully agree with your analysis in the previous mails: EVENT_MANAGE_PROJECT_DELETE Delete from project_table EVENT_MANAGE_PROJECT_DELETED I was thinking the same and was a little anoyed when I worked on this (as you noticed in my comment!). Of course, I'd be pleased to help on this issue, but I cannot guarantee that I'll work on it: MantisBT is a great project and - luckily - has a huge amount of developpers. CodevTT is a big project with only one developper. I'm overwhelmed with work, so don't be mad at me if I don't take this point. Thank you for your help ! Louis Louis BAYLE Tel: +33 (0)4.42.604.734 lba...@gm... On Thu, Oct 16, 2014 at 11:23 PM, P Richards <pa...@ma...> wrote: > HI Louis (as this is aimed mainly at you ;)) > > > > I’m just taking some time to look at your application around mantis (I > think it’s probably fair to say application rather than plugin in this case) > > > > Whilst I could easily switch off at the site of mysql_query within the > plugin ;) > > > > I notice you have a comment on your plugin event: > > > > # check BEFORE DELETE (but unfortunately after the 'are you sure?' page...) > > 'EVENT_BUG_DELETED' => 'checkTimetracks', > > > > This strikes me as you are having to work around an issue with the > placements of hooks within Mantis – would you care to elaborate on the > issue? – as this might be a case of somewhere it would make sense for you > to add an additional hook or better placed hook. > > > > Paul > > > > > > > > > ------------------------------------------------------------------------------ > Comprehensive Server Monitoring with Site24x7. > Monitor 10 servers for $9/Month. > Get alerted through email, SMS, voice calls or mobile push notifications. > Take corrective actions from your mobile device. > http://p.sf.net/sfu/Zoho > _______________________________________________ > mantisbt-dev mailing list > man...@li... > https://lists.sourceforge.net/lists/listinfo/mantisbt-dev > > |
From: P R. <pa...@ma...> - 2014-10-16 21:23:19
|
HI Louis (as this is aimed mainly at you ;)) I'm just taking some time to look at your application around mantis (I think it's probably fair to say application rather than plugin in this case) Whilst I could easily switch off at the site of mysql_query within the plugin ;) I notice you have a comment on your plugin event: # check BEFORE DELETE (but unfortunately after the 'are you sure?' page...) 'EVENT_BUG_DELETED' => 'checkTimetracks', This strikes me as you are having to work around an issue with the placements of hooks within Mantis - would you care to elaborate on the issue? - as this might be a case of somewhere it would make sense for you to add an additional hook or better placed hook. Paul |
From: P R. <pa...@ma...> - 2014-10-16 21:13:40
|
Hi, Actually, the pull request I generated also handles VERSION deletions In terms of the code for the manage project deletion event, there’s a couple of subtle differences: Firstly – you currently place the code within manage_proj_delete.php – this is a problem in as much as – it’s possible to delete projects via the SOAP api. Equally other plugins may provide routes to delete projects. Making the assumption that the most likely reason for adding a plugin on a hook to handle project deletions is to allow either: a) Synchronisation of project information with a 3rd party source (I suspect in your case this the reason you are after this event is so you can handle project deletions within your time tracking software b) “Event log” monitoring of project deletions In both of these cases the correct placement of this hook is within project_delete – one of the issues in the current code IMO is that for some of the hooks I’ve slowly been submitting PR’s to relocate/fix there are cases where the event does not fire – for example, a bugnote added event that only fires if a bugnote is added via a particular route. In some cases I’d deem this to be the correct behaviour i.e. if we expect the plugin author to modify a particular page. In the case of deletion of project or version events, I think that it’s unlikely that we’d want to modify the page output – and that instead, the expectation would be to achieve either a or b above. If indeed, the expectation is to allow something specify to the manage page, then I’d argue we’d need to add a 2 new events – one to fire on A+B above, the other to fire on the manage project page. In terms of the naming of the hook, (and again, I think some of our existing hooks may have been thrown in in the wrong place in this regard) – we may like to add 2 events at some stage: EVENT_MANAGE_PROJECT_DELETE (Y) Delete from project_table EVENT_MANAGE_PROJECT_DELETED (Z) Consider 3 plugins: a) Plugin 1 checks project has been removed from a wiki before allowing deletion b) Plugin 2 checks project has been removed from a forum before allowing deletion from mantis c) Plugin 3 logs that a project has been deleted In the base above, we’d want to hook plugins 1+2 to event Y – this would allow a user to “block” the deletion of the project if the tidy up steps (delete from wiki, delete from forum) had not been completed. We’d then potentially want to hook plugin 3 to event Z – i.e. to perform the logging after the actual deletion – note, we’d need to be careful what arguments would be picked for this hook as it wouldn’t be possible to look up the information at this point. In any case, my point here is more that we need to make a good choice of naming for future use – calling an event “deleted” (past tense) before the actual deletion I’d argue is more confusing for long-term use. We describe the hook as a “pre-“ hook and then use past tense which doesn’t make that much sense – and I’m pretty sure we do that in a number of places already. Paul From: Louis BAYLE [mailto:lba...@gm...] Sent: 16 October 2014 21:26 To: developer discussions Subject: Re: [mantisbt-dev] EVENT_MANAGE_PROJECT_DELETE Hi Paul, I too, created a pull request on EVENT_MANAGE_PROJECT_DELETED: https://github.com/mantisbt/mantisbt/pull/383 So now we've got two :-) Note: i called it "..._DELETED" (instead of "..._DELETE", to be similar to the 'EVENT_BUG_DELETED' event. But it's exactly the same code. I tested in on my plugin, so it should be ok. Thank you, Louis Louis BAYLE Tel: +33 (0)4.42.604.734 lba...@gm... <mailto:lba...@gm...> On Thu, Oct 16, 2014 at 9:16 PM, Paul Richards <gra...@bl... <mailto:gra...@bl...> > wrote: Louis, As promised, I’ve generated the patch I had for PROJECT event deletion, and also VERSION event deletion. Whilst I managed to generate the patch at lunchtime today from previous experimental branches, we block SSH from our work network to “unknown” hosts so could only generate the PR now. I’ve created two bugs in Mantis to track these new events: http://www.mantisbt.org/bugs/view.php?id=17782 - 0017782: New Event: EVENT_MANAGE_VERSION_DELETE http://www.mantisbt.org/bugs/view.php?id=17783 - 0017783: New Event: EVENT_MANAGE_PROJECT_DELETE Can you see if the PR for this at https://github.com/mantisbt/mantisbt/pull/384 would achieve what you were after? I’ve got some similar patches still to generate PR’s for, so if there’s anything else you are missing say – it might be I already have a patch, or it might be something new that it would be helpful for you to work on implementing. Thanks Paul From: Paul Richards [mailto:pa...@ma... <mailto:pa...@ma...> ] Sent: 16 October 2014 10:08 To: developer discussions Subject: Re: [mantisbt-dev] EVENT_MANAGE_PROJECT_DELETE Hi Louis, I'd been reviewing some of the EVENT's in mantis recently for correct placement. Hooks on deleting project is one of the areas where we are missing events. I'll generate a PR either during a spare moment today or this evening for this. We actually miss being able to hook on a number of deletion activities across the code base - adding additional hooks to cover this is something that has been on my list to backport from the previous scrapped 2.x branches. In addition, when reviewing the events before in that branch, there were a number of events that I believe we mis-placed within the code base ( some of which are currently in as PR's and as those get reviewed and merged, i'll be continuing to submit the remaining ones) Paul On Thu, Oct 16, 2014 at 9:27 AM, Louis BAYLE <lba...@gm... <mailto:lba...@gm...> > wrote: Hi, I have not found any EVENT_MANAGE_PROJECT_DELETE in core/events_inc.php. Do you know if someone has already worked on this ? If not, I'll try to do it. Is there any chance that this would be integrated in future mantis 1.2.x releases or are you not interested in this event ? Is there any documentation on adding events in mantis ? Best regards, Louis BAYLE http://CodevTT.org lba...@gm... <mailto:lba...@gm...> ------------------------------------------------------------------------------ Comprehensive Server Monitoring with Site24x7. Monitor 10 servers for $9/Month. Get alerted through email, SMS, voice calls or mobile push notifications. Take corrective actions from your mobile device. http://p.sf.net/sfu/Zoho _______________________________________________ mantisbt-dev mailing list man...@li... <mailto:man...@li...> https://lists.sourceforge.net/lists/listinfo/mantisbt-dev ------------------------------------------------------------------------------ Comprehensive Server Monitoring with Site24x7. Monitor 10 servers for $9/Month. Get alerted through email, SMS, voice calls or mobile push notifications. Take corrective actions from your mobile device. http://p.sf.net/sfu/Zoho _______________________________________________ mantisbt-dev mailing list man...@li... <mailto:man...@li...> https://lists.sourceforge.net/lists/listinfo/mantisbt-dev |
From: Louis B. <lba...@gm...> - 2014-10-16 20:26:29
|
Hi Paul, I too, created a pull request on EVENT_MANAGE_PROJECT_DELETED: https://github.com/mantisbt/mantisbt/pull/383 So now we've got two :-) Note: i called it "..._DELETED" (instead of "..._DELETE", to be similar to the 'EVENT_BUG_DELETED' event. But it's exactly the same code. I tested in on my plugin, so it should be ok. Thank you, Louis Louis BAYLE Tel: +33 (0)4.42.604.734 lba...@gm... On Thu, Oct 16, 2014 at 9:16 PM, Paul Richards <gra...@bl...> wrote: > Louis, > > > > As promised, I’ve generated the patch I had for PROJECT event deletion, > and also VERSION event deletion. > > > > Whilst I managed to generate the patch at lunchtime today from previous > experimental branches, we block SSH from our work network to “unknown” > hosts so could only generate the PR now. > > > > I’ve created two bugs in Mantis to track these new events: > > > > http://www.mantisbt.org/bugs/view.php?id=17782 - 0017782: New Event: > EVENT_MANAGE_VERSION_DELETE > > http://www.mantisbt.org/bugs/view.php?id=17783 - 0017783: New Event: > EVENT_MANAGE_PROJECT_DELETE > > > > Can you see if the PR for this at > https://github.com/mantisbt/mantisbt/pull/384 would achieve what you > were after? > > > > I’ve got some similar patches still to generate PR’s for, so if there’s > anything else you are missing say – it might be I already have a patch, or > it might be something new that it would be helpful for you to work on > implementing. > > > > Thanks > > Paul > > > > *From:* Paul Richards [mailto:pa...@ma...] > *Sent:* 16 October 2014 10:08 > *To:* developer discussions > *Subject:* Re: [mantisbt-dev] EVENT_MANAGE_PROJECT_DELETE > > > > Hi Louis, > > > > I'd been reviewing some of the EVENT's in mantis recently for correct > placement. > > > > Hooks on deleting project is one of the areas where we are missing events. > > > > I'll generate a PR either during a spare moment today or this evening for > this. We actually miss being able to hook on a number of deletion > activities across the code base - adding additional hooks to cover this is > something that has been on my list to backport from the previous scrapped > 2.x branches. > > > > In addition, when reviewing the events before in that branch, there were a > number of events that I believe we mis-placed within the code base ( some > of which are currently in as PR's and as those get reviewed and merged, > i'll be continuing to submit the remaining ones) > > > > Paul > > > > > > > > On Thu, Oct 16, 2014 at 9:27 AM, Louis BAYLE <lba...@gm...> > wrote: > > Hi, > > I have not found any EVENT_MANAGE_PROJECT_DELETE in core/events_inc.php. > > Do you know if someone has already worked on this ? > > If not, I'll try to do it. Is there any chance that this would be > integrated in future mantis 1.2.x releases or are you not interested in > this event ? > > > > Is there any documentation on adding events in mantis ? > > Best regards, > > > Louis BAYLE > http://CodevTT.org > lba...@gm... > > > > ------------------------------------------------------------------------------ > Comprehensive Server Monitoring with Site24x7. > Monitor 10 servers for $9/Month. > Get alerted through email, SMS, voice calls or mobile push notifications. > Take corrective actions from your mobile device. > http://p.sf.net/sfu/Zoho > _______________________________________________ > mantisbt-dev mailing list > man...@li... > https://lists.sourceforge.net/lists/listinfo/mantisbt-dev > > > > > ------------------------------------------------------------------------------ > Comprehensive Server Monitoring with Site24x7. > Monitor 10 servers for $9/Month. > Get alerted through email, SMS, voice calls or mobile push notifications. > Take corrective actions from your mobile device. > http://p.sf.net/sfu/Zoho > _______________________________________________ > mantisbt-dev mailing list > man...@li... > https://lists.sourceforge.net/lists/listinfo/mantisbt-dev > > |
From: Paul R. <gra...@bl...> - 2014-10-16 19:27:37
|
I thought you could only push back on ssh though, or do you have to modify the command in some way? I cloned with git clone https://github.com/mantisbt/mantisbt.git and that didn't allow pushing back And ssh to gi...@gi...:mantisbt/mantisbt.git hit the regional firewall block - I should probably put in a CR to get a rule to allow ssh to github added at some point. Paul -----Original Message----- From: Robert Munteanu [mailto:rob...@gm...] Sent: 16 October 2014 20:19 To: developer discussions Subject: Re: [mantisbt-dev] EVENT_MANAGE_PROJECT_DELETE On Thu, Oct 16, 2014 at 10:16 PM, Paul Richards <gra...@bl...> wrote: > Whilst I managed to generate the patch at lunchtime today from > previous experimental branches, we block SSH from our work network to > “unknown” hosts so could only generate the PR now. You can use https for github access ; that's very likely to be allowed through firewalls. Robert -- http://robert.muntea.nu/ ------------------------------------------------------------------------------ Comprehensive Server Monitoring with Site24x7. Monitor 10 servers for $9/Month. Get alerted through email, SMS, voice calls or mobile push notifications. Take corrective actions from your mobile device. http://p.sf.net/sfu/Zoho _______________________________________________ mantisbt-dev mailing list man...@li... https://lists.sourceforge.net/lists/listinfo/mantisbt-dev |
From: Robert M. <rob...@gm...> - 2014-10-16 19:19:26
|
On Thu, Oct 16, 2014 at 10:16 PM, Paul Richards <gra...@bl...> wrote: > Whilst I managed to generate the patch at lunchtime today from previous > experimental branches, we block SSH from our work network to “unknown” hosts > so could only generate the PR now. You can use https for github access ; that's very likely to be allowed through firewalls. Robert -- http://robert.muntea.nu/ |
From: Paul R. <gra...@bl...> - 2014-10-16 19:17:10
|
Louis, As promised, I’ve generated the patch I had for PROJECT event deletion, and also VERSION event deletion. Whilst I managed to generate the patch at lunchtime today from previous experimental branches, we block SSH from our work network to “unknown” hosts so could only generate the PR now. I’ve created two bugs in Mantis to track these new events: http://www.mantisbt.org/bugs/view.php?id=17782 - 0017782: New Event: EVENT_MANAGE_VERSION_DELETE http://www.mantisbt.org/bugs/view.php?id=17783 - 0017783: New Event: EVENT_MANAGE_PROJECT_DELETE Can you see if the PR for this at https://github.com/mantisbt/mantisbt/pull/384 would achieve what you were after? I’ve got some similar patches still to generate PR’s for, so if there’s anything else you are missing say – it might be I already have a patch, or it might be something new that it would be helpful for you to work on implementing. Thanks Paul From: Paul Richards [mailto:pa...@ma...] Sent: 16 October 2014 10:08 To: developer discussions Subject: Re: [mantisbt-dev] EVENT_MANAGE_PROJECT_DELETE Hi Louis, I'd been reviewing some of the EVENT's in mantis recently for correct placement. Hooks on deleting project is one of the areas where we are missing events. I'll generate a PR either during a spare moment today or this evening for this. We actually miss being able to hook on a number of deletion activities across the code base - adding additional hooks to cover this is something that has been on my list to backport from the previous scrapped 2.x branches. In addition, when reviewing the events before in that branch, there were a number of events that I believe we mis-placed within the code base ( some of which are currently in as PR's and as those get reviewed and merged, i'll be continuing to submit the remaining ones) Paul On Thu, Oct 16, 2014 at 9:27 AM, Louis BAYLE <lba...@gm... <mailto:lba...@gm...> > wrote: Hi, I have not found any EVENT_MANAGE_PROJECT_DELETE in core/events_inc.php. Do you know if someone has already worked on this ? If not, I'll try to do it. Is there any chance that this would be integrated in future mantis 1.2.x releases or are you not interested in this event ? Is there any documentation on adding events in mantis ? Best regards, Louis BAYLE http://CodevTT.org lba...@gm... <mailto:lba...@gm...> ------------------------------------------------------------------------------ Comprehensive Server Monitoring with Site24x7. Monitor 10 servers for $9/Month. Get alerted through email, SMS, voice calls or mobile push notifications. Take corrective actions from your mobile device. http://p.sf.net/sfu/Zoho _______________________________________________ mantisbt-dev mailing list man...@li... <mailto:man...@li...> https://lists.sourceforge.net/lists/listinfo/mantisbt-dev |
From: Damien R. <dr...@ma...> - 2014-10-16 09:25:47
|
Louis BAYLE <lbayle.work@...> writes: > So there will be no more 1.2.x release ? We would only be releasing security and important bug fixes, but definitely no new features. > My application (CodevTT.org) is closely linked to the mantis database, is > there a description of the changes in the DB that you plan to do from > 1.2.x to 1.3 ? There are no major changes to the database; you can find full details about these by reviewing the the schema definition: https://github.com/mantisbt/mantisbt/blob/master/admin/schema.php#L729 Helper functions source code is in http://git.io/KxbWXw |
From: Paul R. <pa...@ma...> - 2014-10-16 09:08:32
|
Hi Louis, I'd been reviewing some of the EVENT's in mantis recently for correct placement. Hooks on deleting project is one of the areas where we are missing events. I'll generate a PR either during a spare moment today or this evening for this. We actually miss being able to hook on a number of deletion activities across the code base - adding additional hooks to cover this is something that has been on my list to backport from the previous scrapped 2.x branches. In addition, when reviewing the events before in that branch, there were a number of events that I believe we mis-placed within the code base ( some of which are currently in as PR's and as those get reviewed and merged, i'll be continuing to submit the remaining ones) Paul On Thu, Oct 16, 2014 at 9:27 AM, Louis BAYLE <lba...@gm...> wrote: > Hi, > I have not found any EVENT_MANAGE_PROJECT_DELETE in core/events_inc.php. > Do you know if someone has already worked on this ? > > If not, I'll try to do it. Is there any chance that this would be > integrated in future mantis 1.2.x releases or are you not interested in > this event ? > > Is there any documentation on adding events in mantis ? > > Best regards, > > Louis BAYLE > http://CodevTT.org > lba...@gm... > > > ------------------------------------------------------------------------------ > Comprehensive Server Monitoring with Site24x7. > Monitor 10 servers for $9/Month. > Get alerted through email, SMS, voice calls or mobile push notifications. > Take corrective actions from your mobile device. > http://p.sf.net/sfu/Zoho > _______________________________________________ > mantisbt-dev mailing list > man...@li... > https://lists.sourceforge.net/lists/listinfo/mantisbt-dev > > |
From: Louis B. <lba...@gm...> - 2014-10-16 08:58:32
|
Hi, thanks for your quick answer, I'll see what I can do. So there will be no more 1.2.x release ? My application (CodevTT.org) is closely linked to the mantis database, is there a description of the changes in the DB that you plan to do from 1.2.x to 1.3 ? thank you, Louis BAYLE http://CodevTT.org <lba...@gm...> On Thu, Oct 16, 2014 at 10:43 AM, Damien Regad <dr...@ma...> wrote: > Louis BAYLE <lbayle.work@...> writes: > > Hi Louis, > > > I have not found any EVENT_MANAGE_PROJECT_DELETE in core/events_inc.php. > > Do you know if someone has already worked on this ? > > If there is, I'm not aware of it. > > > If not, I'll try to do it. > > Your contribution would be welcome ! > > > Is there any chance that this would be integrated in future mantis 1.2.x > > releases or are you not interested in this event ? > > Please note that it is unlikely we would add any new features to the 1.2.x > branch, as we're focusing our efforts on releasing 1.3 now. > > Therefore, I suggest you submit your work as a pull request against our > master branch. > > > Is there any documentation on adding events in mantis ? > > All information there is would be in the developer's guide (see > http://mantisbt.org/documentation.php); When adding new events, they > should > be documented there. > > Hope this helps > > > > > ------------------------------------------------------------------------------ > Comprehensive Server Monitoring with Site24x7. > Monitor 10 servers for $9/Month. > Get alerted through email, SMS, voice calls or mobile push notifications. > Take corrective actions from your mobile device. > http://p.sf.net/sfu/Zoho > _______________________________________________ > mantisbt-dev mailing list > man...@li... > https://lists.sourceforge.net/lists/listinfo/mantisbt-dev > |
From: Damien R. <dr...@ma...> - 2014-10-16 08:44:12
|
Louis BAYLE <lbayle.work@...> writes: Hi Louis, > I have not found any EVENT_MANAGE_PROJECT_DELETE in core/events_inc.php. > Do you know if someone has already worked on this ? If there is, I'm not aware of it. > If not, I'll try to do it. Your contribution would be welcome ! > Is there any chance that this would be integrated in future mantis 1.2.x > releases or are you not interested in this event ? Please note that it is unlikely we would add any new features to the 1.2.x branch, as we're focusing our efforts on releasing 1.3 now. Therefore, I suggest you submit your work as a pull request against our master branch. > Is there any documentation on adding events in mantis ? All information there is would be in the developer's guide (see http://mantisbt.org/documentation.php); When adding new events, they should be documented there. Hope this helps |
From: Louis B. <lba...@gm...> - 2014-10-16 08:27:38
|
Hi, I have not found any EVENT_MANAGE_PROJECT_DELETE in core/events_inc.php. Do you know if someone has already worked on this ? If not, I'll try to do it. Is there any chance that this would be integrated in future mantis 1.2.x releases or are you not interested in this event ? Is there any documentation on adding events in mantis ? Best regards, Louis BAYLE http://CodevTT.org lba...@gm... |
From: Damien R. <dr...@ma...> - 2014-10-09 00:02:58
|
On 2014-10-08 01:33, P Richards wrote: > Webserver is taking a long time to load some pages: > > Time: 9.7297 seconds. That's really a crappy problem report... you should know better. For starters, knowing what page(s) are having issues might help In any case, as Victor said, performance is fast enough for me (pages generally load < 1s, except summary or complex filters) |
From: Victor B. <vb...@gm...> - 2014-10-08 01:01:09
|
I can’t reproduce. On Oct 7, 2014, at 4:33 PM, P Richards <pa...@ma...> wrote: > Webserver is taking a long time to load some pages: > > Time: 9.7297 seconds. > > > ------------------------------------------------------------------------------ > Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer > Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports > Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper > Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer > http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk_______________________________________________ > mantisbt-dev mailing list > man...@li... > https://lists.sourceforge.net/lists/listinfo/mantisbt-dev |
From: P R. <pa...@ma...> - 2014-10-07 23:33:55
|
Webserver is taking a long time to load some pages: Time: 9.7297 seconds. |
From: Paul R. <gra...@bl...> - 2014-10-06 18:44:57
|
HI victor, The temporary public key I created before I've now stopped using - so please do not add the previously issued key when you get around to it. The correct key is attached, and is valid until 10th October Paul -----Original Message----- From: Paul Richards [mailto:gra...@bl...] Sent: 20 August 2014 17:52 To: 'developer discussions' Subject: [mantisbt-dev] FW: FW: MantisBT 1.3 Release Status Check Hello, Victor, can you use the attached key instead of the previous one. I've expired the previous public key and have created a new public key to be added. Paul -----Original Message----- From: Paul Richards [mailto:gra...@bl...] Sent: 11 August 2014 20:16 To: 'developer discussions' Subject: [mantisbt-dev] FW: MantisBT 1.3 Release Status Check Victor, as promised on the github PR, here is a copy of my current SSH public key Paul -----Original Message----- From: P Richards [mailto:pa...@ma...] Sent: 18 June 2014 22:06 To: 'developer discussions' Subject: Re: [mantisbt-dev] MantisBT 1.3 Release Status Check Damien, I've resent my ssh key to Victor, as well as adding my public key to this email. As soon as the key has been added to the server, I can push the security fixes I have to a private repository on that box that people can clone form. Hopefully it'll get added soon as Victor has promised several times previously to do this. Paul -----Original Message----- From: Damien Regad [mailto:dr...@ma...] Sent: 16 June 2014 15:02 To: Man...@li... Subject: Re: [mantisbt-dev] MantisBT 1.3 Release Status Check >From my end, I only have https://github.com/mantisbt/mantisbt/pull/181 (adodb & related fixes) which must be merged before releasing alpha1. This is currently being blocked by grangeway, who as a sidenote seems to be spending a lot of time on nice to have but somewhat futile endeavors at the moment (e.g. the coding guidelines thing) instead of delivering on the more important topics (where are those security patches !?) as per his own committments. The rest is minor stuff which can easily go in a later release (beta or .x) as far as I'm concerned. --- This email is free from viruses and malware because avast! Antivirus protection is active. http://www.avast.com ---------------------------------------------------------------------------- -- HPCC Systems Open Source Big Data Platform from LexisNexis Risk Solutions Find What Matters Most in Your Big Data with HPCC Systems Open Source. Fast. Scalable. Simple. Ideal for Dirty Data. Leverages Graph Analysis for Fast Processing & Easy Data Exploration http://p.sf.net/sfu/hpccsystems _______________________________________________ mantisbt-dev mailing list man...@li... https://lists.sourceforge.net/lists/listinfo/mantisbt-dev |
From: Damien R. <dr...@ma...> - 2014-10-03 13:52:34
|
On 2014-10-02 08:43, Victor Boctor wrote: > The vector graphics are available for use by the project, and I gave the > logo to Damien before to set avatar on some site, but I just wasn’t sure > about having in the mantisbt repository without having usage guidelines > in place. > > We can go with any of the following options: > > 1. Share it in the mantibt-tools repository > 2. Share it in a private git repository > 3. Share it and distribute it with mantisbt I personally think that *3* is the best option, but I can live with 1 as well. Don't really see the point of 2. > We should publish the logo and usage guidelines for the logo at the same > time. For example, can other sites alter the logo, does it have to link > back to our website, can it be printed on merchandise, etc. I haven’t > done the research to see what other projects are doing in this space. > But seems like Paul is motivated to do the research. I'm fine with having reasonable usage guidelines / terms&conditions, whatever you want to call them, as long as somebody other than me takes care of writing them ;-) I'll gladly review any proposal. |
From: Paul R. <pa...@ma...> - 2014-10-02 07:34:29
|
One of the "issues" here is the loosely defined definition of 'team/mantisbt', and equally a lack of trademark over the word mantis For an opensource project that has a corporate entity e.g. wordpress, or a officially defined 'trust', it's easy - you state that any queries over logo use needs to be licensed by said corporate entity. So far, we've put a logo as a png in the repository (where we state the repository is GPL licensed) and haven't done anything separate for the logo. On the forum atrol's given the following advice previously: http://mantisbt.org/forums/viewtopic.php?f=2&t=22230&p=54875&hilit=logo#p54875 Damien/Myself have previously said the following: (and assumed the logo is gpl) http://article.gmane.org/gmane.comp.bug-tracking.mantis.general/3510/match=logo http://article.gmane.org/gmane.comp.bug-tracking.mantis.general/3512/match=logo and previously you've given users the ok to do colour modifications to the logo: http://article.gmane.org/gmane.comp.bug-tracking.mantis.general/839/match=logo I will try and do some proper research when I'm not at work, however whilst I think it's fairly obvious what we allow, equally where we are not an officially registered group with an officially registered trademark, or backed by a corporate entity etc etc, it probably actually makes it harder. At the moment, we currently define everything back to "MantisBT Team", as the overriding entity, which is a loosely defined term. Paul On Thu, Oct 2, 2014 at 7:43 AM, Victor Boctor <vb...@gm...> wrote: > The vector graphics are available for use by the project, and I gave the > logo to Damien before to set avatar on some site, but I just wasn’t sure > about having in the mantisbt repository without having usage guidelines in > place. > > We can go with any of the following options: > > 1. Share it in the mantibt-tools repository > 2. Share it in a private git repository > 3. Share it and distribute it with mantisbt > > We should publish the logo and usage guidelines for the logo at the same > time. For example, can other sites alter the logo, does it have to link > back to our website, can it be printed on merchandise, etc. I haven’t done > the research to see what other projects are doing in this space. But seems > like Paul is motivated to do the research. > > Thoughts? > > On Oct 1, 2014, at 10:09 AM, P Richards <pa...@ma...> wrote: > > When we originally changed the logo for Mantis in 2012, my understanding > was that we would be putting a copy of the logo in VECTOR format for people > to use in the source repository. > > Following damien’s comment @ > https://github.com/mantisbt/mantisbt/pull/328#issuecomment-57475687 , I’m > concerned whether as a team we now own and have royalty-free access to our > current logo. > > As an open source project that can be developed by different people and > other time the team has and I’m sure will continue to change, we should > ensure that our logo is in the public domain. > > When we originally discussed the logo before @ > http://www.mantisbt.org/bugs/view.php?id=7994 – we had a number of offers > from users to design for free a logo in the public domain and to give it to > us in vector format. > > So given damien’s comment back to me, and roland’s request back in > February 2012 below about having the logo available so we can freely modify > it. > > I have a simple question: > > Is the current logo a free logo that can be made available in Vector > format? If not, I suggest we reopen issue 7994 and look into designing a > logo that is completely free for our use. > > I work in a school and have some students and work colleagues that would > happily design a logo in vector format that would be royalty free and in > the public domain for our use if for some reason the existing logo cannot > be made available. In an ideal world, I’d hope that it is the case that the > logo we picked in 2012 was indeed a publicly available logo that was free > for our use for any purposes. At least, indeed this was what I was led to > believe when Victor originally emailed about the new logo and stated: “In > the issue you will find the old proposals, the new proposals, the > guidelines that I wrote about what we want,” referring to the guidelines > that stated: > > “- The logo should be available in image and vector formats (e.g. PNG, > Adobe Photoshop and Adobe Illustrator)” > > Victor: could you send a copy of the logo in Vector Format to the mailing > list, as per the original intention ? > > Thanks > Paul > > > *From:* Roland Becker [mailto:ro...@at... <ro...@at...>] > *Sent:* 09 February 2012 09:32 > *To:* developer discussions > *Subject:* Re: [mantisbt-dev] Misleading descriptions of MantisBT forks > at github > > > 1. Logo in Vector Format - I'll have the logo in Adobe Illustrator > format as well as PNG format. > > Please also SVG , so we could use open source solutions like Inkscape to > modify whatever we want. > At least it will show us whether Illustrator SVG export and Inkscape's PNG > rendering will produce the same result. > If the Inkscape output is different (I don't expect a 100% bit identical > output), but what you can see is ok, we should use this one. > > > > ------------------------------------------------------------------------------ > Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer > Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports > Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper > Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer > > http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk_______________________________________________ > mantisbt-dev mailing list > man...@li... > https://lists.sourceforge.net/lists/listinfo/mantisbt-dev > > > > > ------------------------------------------------------------------------------ > Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer > Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports > Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper > Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer > > http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk > _______________________________________________ > mantisbt-dev mailing list > man...@li... > https://lists.sourceforge.net/lists/listinfo/mantisbt-dev > > |
From: Victor B. <vb...@gm...> - 2014-10-02 06:43:58
|
The vector graphics are available for use by the project, and I gave the logo to Damien before to set avatar on some site, but I just wasn’t sure about having in the mantisbt repository without having usage guidelines in place. We can go with any of the following options: 1. Share it in the mantibt-tools repository 2. Share it in a private git repository 3. Share it and distribute it with mantisbt We should publish the logo and usage guidelines for the logo at the same time. For example, can other sites alter the logo, does it have to link back to our website, can it be printed on merchandise, etc. I haven’t done the research to see what other projects are doing in this space. But seems like Paul is motivated to do the research. Thoughts? On Oct 1, 2014, at 10:09 AM, P Richards <pa...@ma...> wrote: > When we originally changed the logo for Mantis in 2012, my understanding was that we would be putting a copy of the logo in VECTOR format for people to use in the source repository. > > Following damien’s comment @ https://github.com/mantisbt/mantisbt/pull/328#issuecomment-57475687 , I’m concerned whether as a team we now own and have royalty-free access to our current logo. > > As an open source project that can be developed by different people and other time the team has and I’m sure will continue to change, we should ensure that our logo is in the public domain. > > When we originally discussed the logo before @ http://www.mantisbt.org/bugs/view.php?id=7994 – we had a number of offers from users to design for free a logo in the public domain and to give it to us in vector format. > > So given damien’s comment back to me, and roland’s request back in February 2012 below about having the logo available so we can freely modify it. > > I have a simple question: > > Is the current logo a free logo that can be made available in Vector format? If not, I suggest we reopen issue 7994 and look into designing a logo that is completely free for our use. > > I work in a school and have some students and work colleagues that would happily design a logo in vector format that would be royalty free and in the public domain for our use if for some reason the existing logo cannot be made available. In an ideal world, I’d hope that it is the case that the logo we picked in 2012 was indeed a publicly available logo that was free for our use for any purposes. At least, indeed this was what I was led to believe when Victor originally emailed about the new logo and stated: “In the issue you will find the old proposals, the new proposals, the guidelines that I wrote about what we want,” referring to the guidelines that stated: > > “- The logo should be available in image and vector formats (e.g. PNG, Adobe Photoshop and Adobe Illustrator)” > > Victor: could you send a copy of the logo in Vector Format to the mailing list, as per the original intention ? > > Thanks > Paul > > > From: Roland Becker [mailto:ro...@at...] > Sent: 09 February 2012 09:32 > To: developer discussions > Subject: Re: [mantisbt-dev] Misleading descriptions of MantisBT forks at github > > > 1. Logo in Vector Format - I'll have the logo in Adobe Illustrator format as well as PNG format. > > Please also SVG , so we could use open source solutions like Inkscape to modify whatever we want. > At least it will show us whether Illustrator SVG export and Inkscape's PNG rendering will produce the same result. > If the Inkscape output is different (I don't expect a 100% bit identical output), but what you can see is ok, we should use this one. > > > ------------------------------------------------------------------------------ > Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer > Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports > Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper > Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer > http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk_______________________________________________ > mantisbt-dev mailing list > man...@li... > https://lists.sourceforge.net/lists/listinfo/mantisbt-dev |