Menu
▾
▴
mantisbt-dev — MantisBT development discussions
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: Damien R. <dr...@ma...> - 2015-08-02 19:37:05
|
On 2015-08-02 10:32, Roland Becker wrote: >> Robert Munteanu <rob...@gm...> hat am 30. Juli 2015 um 09:58 >> geschrieben: >> >> To make it easier to support both MantisBT 1.2 and 1.3 in plugins we >> could 'provide' a dummy jQuery plugin with the MantisBT core. >> >> Thoughts? > > I prefer breaking things instead of some magic in the background that might > finally end in strange issues. I'm with Roland here. I believe the system I've put in place quite effectively deals with the problem by disabling the plugin; this should force the plugin authors to have a look at their code, and implement any necessary changes to ensure proper operations with 1.3 and release a specific version. I'm aware that this approach does put an additional burden on the plugin authors (to maintain a dedicated 1.3 branch), but in my opinion it is a better and safer alternative than the "dummy plugin" you suggest which would anyway only cover part of the 1.3 compatibility problem. In addition to jQuery support, authors also need to consider the revised CSS, deprecated functions, new syntax for DB queries, etc. |
|
From: Roland B. <ro...@at...> - 2015-08-02 08:45:23
|
Consider also https://www.mantisbt.org/bugs/view.php?id=17360 and https://github.com/mantisbt/mantisbt/pull/239 when thinking about it I prefer breaking things instead of some magic in the background that might finally end in strange issues. Of course, I am biased as I am quite often dealing with strange issues in our forum ;-) Roland > Robert Munteanu <rob...@gm...> hat am 30. Juli 2015 um 09:58 > geschrieben: > > > Hi, > > In MantisBT 1.2 jQuery was provided by a plugin. In MantisBT 1.3 it's > included in the core. However, there are still plugins which require > jQuery. > > To make it easier to support both MantisBT 1.2 and 1.3 in plugins we > could 'provide' a dummy jQuery plugin with the MantisBT core. > > Thoughts? > > Robert > > ------------------------------------------------------------------------------ > _______________________________________________ > mantisbt-dev mailing list > man...@li... > https://lists.sourceforge.net/lists/listinfo/mantisbt-dev |
|
From: Robert M. <rob...@gm...> - 2015-07-30 07:58:40
|
Hi, In MantisBT 1.2 jQuery was provided by a plugin. In MantisBT 1.3 it's included in the core. However, there are still plugins which require jQuery. To make it easier to support both MantisBT 1.2 and 1.3 in plugins we could 'provide' a dummy jQuery plugin with the MantisBT core. Thoughts? Robert |
|
From: Damien R. <dr...@ma...> - 2015-06-12 13:57:03
|
Chandan Pandey <chandanpandey1001@...> writes: > I would like to host a new plugin authored by me on Mantis Git repo for > public access. Plugin is not on GitHub as of now. Let me know what can I > do for it. Please see https://www.mantisbt.org/wiki/doku.php/mantisbt:mantis_plugins section "Hosting a new plugin" |
|
From: Chandan P. <cha...@gm...> - 2015-06-12 13:32:38
|
Hi, I would like to host a new plugin authored by me on Mantis Git repo for public access. Plugin is not on GitHub as of now. Let me know what can I do for it. Regards Chandan Pandey __________________________________ |
|
From: S. P. <spi...@gm...> - 2015-05-12 23:48:04
|
Hi, you are right in all aspects. It's just that I don't have a clue about mantis-bt APIs. Could you just mention a corresponding API method or class for each of your findings, please? I would be able to figure out how to continue from that. Thanks. Slawa Pidgorny. ____________________________________________ Time tracking and invoicing: http://rechnung-plus.de/ Need a new web-site? http://sigayeva.com/ Making appointments online: http://appointment.at/ On 11 May 2015 at 11:56, Alain D'EURVEILHER <ala...@gm...> wrote: > Hi, > I just had a look at your plugin on your repo (I am no admin, just a > MantisBT user), and I noticed several things which could be considered as > flaws against the mantis policies: > - The plugin does seem to take into account the visibility of he issue by > the connected user. You just make a select on all the bugs and display > them. Some issues can be set as hidden for some users or category of users > (public/private for instance...) > - Not all the users can modify the status of an issue, which your plugin > does not seem to take into account (meaning a viewer could possibly update > the status of an issue via the plugin) > - It also seems that you are bypassing the workflow defined by the mantis > manager/admin. One could define for its installation that a resolved ticket > cannot be opened again for example. > - Your plugin does not seem to work without an internet connection as you > link directly to JQuery online > (echo '<script src=" > https://ajax.googleapis.com/ajax/libs/jquery/2.1.3/jquery.min.js > "></script>';) > > I am assuming all that just by reading your files, I could be wrong on > some point. But I would like to alert you on some notes in case it is > rejected by the mantisBT core team. > > Regards, > AlainD. > > On Mon, May 11, 2015 at 11:32 AM, S. P. <spi...@gm...> wrote: > >> Hi, >> >> this is to announce a new plugin LikeTrello which allows to drag-n-drop >> issue cards between status columns in order to change their status. >> Inspired by https://trello.com/. >> >> See https://github.com/spidgorny/LikeTrello for animated GIF. >> >> Please add it to the list of plugins on wiki and >> https://github.com/mantisbt-plugins. >> >> https://www.mantisbt.org/bugs/view.php?id=19675 >> >> The *list of people* who should have *push access*: spidgorny >> >> Slawa Pidgorny. >> ____________________________________________ >> Time tracking and invoicing: >> http://rechnung-plus.de/ >> >> Need a new web-site? >> http://sigayeva.com/ >> >> Making appointments online: >> http://appointment.at/ >> >> >> ------------------------------------------------------------------------------ >> One dashboard for servers and applications across Physical-Virtual-Cloud >> Widest out-of-the-box monitoring support with 50+ applications >> Performance metrics, stats and reports that give you Actionable Insights >> Deep dive visibility with transaction tracing using APM Insight. >> http://ad.doubleclick.net/ddm/clk/290420510;117567292;y >> _______________________________________________ >> mantisbt-dev mailing list >> man...@li... >> https://lists.sourceforge.net/lists/listinfo/mantisbt-dev >> >> > > > -- > > AlainD. > > > ------------------------------------------------------------------------------ > One dashboard for servers and applications across Physical-Virtual-Cloud > Widest out-of-the-box monitoring support with 50+ applications > Performance metrics, stats and reports that give you Actionable Insights > Deep dive visibility with transaction tracing using APM Insight. > http://ad.doubleclick.net/ddm/clk/290420510;117567292;y > _______________________________________________ > mantisbt-dev mailing list > man...@li... > https://lists.sourceforge.net/lists/listinfo/mantisbt-dev > > |
|
From: Alain D'E. <ala...@gm...> - 2015-05-11 09:56:10
|
Hi, I just had a look at your plugin on your repo (I am no admin, just a MantisBT user), and I noticed several things which could be considered as flaws against the mantis policies: - The plugin does seem to take into account the visibility of he issue by the connected user. You just make a select on all the bugs and display them. Some issues can be set as hidden for some users or category of users (public/private for instance...) - Not all the users can modify the status of an issue, which your plugin does not seem to take into account (meaning a viewer could possibly update the status of an issue via the plugin) - It also seems that you are bypassing the workflow defined by the mantis manager/admin. One could define for its installation that a resolved ticket cannot be opened again for example. - Your plugin does not seem to work without an internet connection as you link directly to JQuery online (echo '<script src=" https://ajax.googleapis.com/ajax/libs/jquery/2.1.3/jquery.min.js "></script>';) I am assuming all that just by reading your files, I could be wrong on some point. But I would like to alert you on some notes in case it is rejected by the mantisBT core team. Regards, AlainD. On Mon, May 11, 2015 at 11:32 AM, S. P. <spi...@gm...> wrote: > Hi, > > this is to announce a new plugin LikeTrello which allows to drag-n-drop > issue cards between status columns in order to change their status. > Inspired by https://trello.com/. > > See https://github.com/spidgorny/LikeTrello for animated GIF. > > Please add it to the list of plugins on wiki and > https://github.com/mantisbt-plugins. > > https://www.mantisbt.org/bugs/view.php?id=19675 > > The *list of people* who should have *push access*: spidgorny > > Slawa Pidgorny. > ____________________________________________ > Time tracking and invoicing: > http://rechnung-plus.de/ > > Need a new web-site? > http://sigayeva.com/ > > Making appointments online: > http://appointment.at/ > > > ------------------------------------------------------------------------------ > One dashboard for servers and applications across Physical-Virtual-Cloud > Widest out-of-the-box monitoring support with 50+ applications > Performance metrics, stats and reports that give you Actionable Insights > Deep dive visibility with transaction tracing using APM Insight. > http://ad.doubleclick.net/ddm/clk/290420510;117567292;y > _______________________________________________ > mantisbt-dev mailing list > man...@li... > https://lists.sourceforge.net/lists/listinfo/mantisbt-dev > > -- AlainD. |
|
From: S. P. <spi...@gm...> - 2015-05-11 09:32:51
|
Hi, this is to announce a new plugin LikeTrello which allows to drag-n-drop issue cards between status columns in order to change their status. Inspired by https://trello.com/. See https://github.com/spidgorny/LikeTrello for animated GIF. Please add it to the list of plugins on wiki and https://github.com/mantisbt-plugins. https://www.mantisbt.org/bugs/view.php?id=19675 The *list of people* who should have *push access*: spidgorny Slawa Pidgorny. ____________________________________________ Time tracking and invoicing: http://rechnung-plus.de/ Need a new web-site? http://sigayeva.com/ Making appointments online: http://appointment.at/ |
|
From: Damien R. <dr...@ma...> - 2015-04-17 09:48:56
|
Roland Becker <roland@...> writes: > > I think we should disable the MantisBT GitHub Wiki It's done. The content is still available if necessary [1], I also saved a copy on our server (in /srv/backup) just in case. D [1] git clone https://github.com/mantisbt/mantisbt.wiki.git |
|
From: Roland B. <ro...@at...> - 2015-04-17 07:17:08
|
I think we should disable the MantisBT GitHub Wiki because - there is outdated and confusing information in it, see example below - we have our own Wiki on mantisbt.org Roland > ---------- Ursprüngliche Nachricht ---------- > Von: Frank Bültge <not...@gi...> > An: bueltge/MantisBT-Colorized <Man...@no...> > Datum: 16. April 2015 um 20:31 > Betreff: Re: [MantisBT-Colorized] Mantis 1.3.0 compatibility (#4) > > I found different hints for the 1.3 > > * https://github.com/mantisbt/mantisbt/wiki/Developer-changes-in-1.3.x > > > --- > Reply to this email directly or view it on GitHub: > https://github.com/bueltge/MantisBT-Colorized/issues/4#issuecomment-93809348 |
|
From: Damien R. <dr...@ma...> - 2015-03-27 08:44:34
|
Louis BAYLE <lbayle.work@...> writes: > I developped a plugin to do some actions when the bug status is > changed. I'm using EVENT_UPDATE_BUG. The job is done correctly when > status is changed from the view.php page, but nothing happens when I > change the status of a task (or a group of tasks) from the > view_all_bug_page.php. > > Could it be possible that the event is not called on group actions ? > Should I open a new bug or is it a normal behaviour ? Please have a look at https://www.mantisbt.org/bugs/view.php?id=14897. I believe you are facing the same issue. D |
|
From: Louis B. <lba...@gm...> - 2015-03-27 01:21:50
|
Hi, I developped a plugin to do some actions when the bug status is changed. I'm using EVENT_UPDATE_BUG. The job is done correctly when status is changed from the view.php page, but nothing happens when I change the status of a task (or a group of tasks) from the view_all_bug_page.php. Could it be possible that the event is not called on group actions ? Should I open a new bug or is it a normal behaviour ? I'm using Mantis 1.2.19 Best regards, Louis BAYLE http://codevtt.org |
|
From: Matej H. <mha...@re...> - 2015-02-10 09:25:40
|
>> we are working on integration of the ABRT reporter > > Pardon my ignorance, but I have absolutely no idea what "ABRT" is. I am sorry I forgot to attach a link to the ABRT documentation. ABRT is a set of tools to help users detect and report application crashes. For more information about the ABRT see http://abrt.readthedocs.org/en/latest/. >> We want to ask when are you planning to release a new version of >> the MantisBT (with the searching methods)? > > No commitment on date, sorry... I responded to this comment https://github.com/mantisbt/mantisbt/pull/560#issuecomment-71344146. >> would it possible to at least release a new beta version of the MantisBT >> which contains the searching methods by the end of the week? > > I think we should release 1.3.0-beta.2 soon, but this deadline is > completely unrealistic as far as I'm concerned. I've got other > priorities for this week. ok, I'll backport the patches from this pull request https://github.com/mantisbt/mantisbt/pull/560 to the MantisBT 1.2.x version which uses CentOS. Matej |
|
From: Damien R. <dr...@ma...> - 2015-02-09 20:51:39
|
On 2015-02-09 15:51, Matej Habrnal wrote: > we are working on integration of the ABRT reporter Pardon my ignorance, but I have absolutely no idea what "ABRT" is. > We want to ask when are you planning to release a new version of > the MantisBT (with the searching methods)? No commitment on date, sorry... > In case you plan to release an official version in a longer period of time > (more than a month), It is indeed likely to be more than a month IMO. > would it possible to at least release a new beta version of the MantisBT > which contains the searching methods by the end of the week? I think we should release 1.3.0-beta.2 soon, but this deadline is completely unrealistic as far as I'm concerned. I've got other priorities for this week. |
|
From: Matej H. <mha...@re...> - 2015-02-09 14:51:44
|
Hi, we are working on integration of the ABRT reporter with the MantisBT (actually CentOS Bug Tracker at the moment). We want to create a testing instance of the CentOS Bug Tracker and after that we want to start testing the ABRT MantisBT reporter on it. To test the full functionality of the reporter we need a latest version of MantisBT with new SOAP API searching methods (https://github.com/mantisbt/mantisbt/pull/560). We want to ask when are you planning to release a new version of the MantisBT (with the searching methods)? In case you plan to release an official version in a longer period of time (more than a month), would it possible to at least release a new beta version of the MantisBT which contains the searching methods by the end of the week? We realize this schedule is kind of tight, but we need to align it with the upcoming release of CentOS 7.1. Best regards Matej Habrnal ABRT team |
|
From: Roland B. <ro...@at...> - 2015-02-04 14:46:04
|
> Damien Regad <dr...@ma...> hat am 4. Februar 2015 um 01:12 > geschrieben: > > > On 2015-02-03 06:13, Victor Boctor wrote: > > I just merged the SOAP API pull request which ended up marking the issue as > > resolved by me. I thought it may be a good idea to mark issues that are > > fixed > > by the community differently from ones that are fixed by the core dev team. > > Hence, I created a “community” user with access level DEVELOPER and assigned > > the issue to that user. > > > > Thoughts? > > It doesn't really hurt I suppose, but I'm not really sure what you are > hoping to achieve by this. > > Consider that we sent emails to the community user and that we can't disable all of them by configuration [1]. You configured community@localhost for the user. I am not sure if there will be a problem sending email to this user. If so, we will generate entries in mantis_email_table that will never be cleared (and the cron job will try to sent them again and again) [1] https://mantisbt.org/bugs/view.php?id=12030 and related issues |
|
From: Damien R. <dr...@ma...> - 2015-02-04 00:12:18
|
On 2015-02-03 06:13, Victor Boctor wrote: > I just merged the SOAP API pull request which ended up marking the issue as > resolved by me. I thought it may be a good idea to mark issues that are fixed > by the community differently from ones that are fixed by the core dev team. > Hence, I created a “community” user with access level DEVELOPER and assigned > the issue to that user. > > Thoughts? It doesn't really hurt I suppose, but I'm not really sure what you are hoping to achieve by this. |
|
From: Victor B. <vb...@gm...> - 2015-02-03 05:14:06
|
Hi all, I just merged the SOAP API pull request which ended up marking the issue as resolved by me. I thought it may be a good idea to mark issues that are fixed by the community differently from ones that are fixed by the core dev team. Hence, I created a “community” user with access level DEVELOPER and assigned the issue to that user. Thoughts? -Victor |
|
From: Victor B. <vb...@gm...> - 2015-01-24 03:05:38
|
Sounds good to me. We should just make sure that the title for both bugs is readable not just a reference to the CVE #. > On Jan 23, 2015, at 12:35 PM, Roland Becker <ro...@at...> wrote: > > Seems this approach has been used in the past > > https://www.mantisbt.org/bugs/view.php?id=6724 > https://www.mantisbt.org/bugs/view.php?id=7743 > > https://www.mantisbt.org/bugs/view.php?id=8153 > https://www.mantisbt.org/bugs/view.php?id=8154 > >> Damien Regad <dr...@ma...> hat am 23. Januar 2015 um 17:13 >> geschrieben: >> >> >> Hello again, >> >> I'd like your input in terms of handling / tracking of important, publicly >> announced security issues (i.e having a CVE) that affect multiple versions. >> >> In the past, we only had a single issue in our tracker, with target/fixed in >> version set to the oldest version (i.e. 1.2.x), and it was implied that the >> fix was also implemented in later releases. >> >> This was not a problem before an "official" release for 1.3 was published, >> but now that we have the beta out, I'm wondering if we should not create >> "dummy" issues as clones/duplicates of the "main" ones for 1.2, but with >> target/fixed version set to 1.3.x. This way the CVE IDs would appear on the >> change log / roadmap. >> >> Thoughts ? >> >> >> >> >> ------------------------------------------------------------------------------ >> New Year. New Location. New Benefits. New Data Center in Ashburn, VA. >> GigeNET is offering a free month of service with a new server in Ashburn. >> Choose from 2 high performing configs, both with 100TB of bandwidth. >> Higher redundancy.Lower latency.Increased capacity.Completely compliant. >> http://p.sf.net/sfu/gigenet >> _______________________________________________ >> mantisbt-dev mailing list >> man...@li... >> https://lists.sourceforge.net/lists/listinfo/mantisbt-dev > > ------------------------------------------------------------------------------ > New Year. New Location. New Benefits. New Data Center in Ashburn, VA. > GigeNET is offering a free month of service with a new server in Ashburn. > Choose from 2 high performing configs, both with 100TB of bandwidth. > Higher redundancy.Lower latency.Increased capacity.Completely compliant. > http://p.sf.net/sfu/gigenet > _______________________________________________ > mantisbt-dev mailing list > man...@li... > https://lists.sourceforge.net/lists/listinfo/mantisbt-dev |
|
From: Victor B. <vb...@gm...> - 2015-01-24 03:00:10
|
I don’t see anything to block. Let’s do it. For 1.3.x, let’s publish the blog this time so we got more usage. I should be able to help Sunday, but if not early next week for sure. > On Jan 23, 2015, at 12:29 PM, Roland Becker <ro...@at...> wrote: > > I don't see anything that would block. > >> Damien Regad <dr...@ma...> hat am 23. Januar 2015 um 17:08 >> geschrieben: >> >> >> Hi team, >> >> After fixing several security issues in 1.2.18, I got confirmation from >> their respective reporters that the problems are indeed resolved, and the >> CVEs have been assigned as needed. >> >> Therefore, unless anyone objects/has pending work that must go in, I propose >> to cut 1.2.19 over the week-end (I just need to work on the release notes). >> >> Victor, do you think you'd be able to publish the release, maybe Sunday or >> early next week ? >> >> Also, since several of the above-mentioned security issues affect 1.3 as >> well, I would recommend that we also release 1.3.0-beta.2, either >> simultaneously or very soon afterwards. >> >> Let me know if you see anything that would block or delay either or both >> releases. >> >> D >> >> >> >> ------------------------------------------------------------------------------ >> New Year. New Location. New Benefits. New Data Center in Ashburn, VA. >> GigeNET is offering a free month of service with a new server in Ashburn. >> Choose from 2 high performing configs, both with 100TB of bandwidth. >> Higher redundancy.Lower latency.Increased capacity.Completely compliant. >> http://p.sf.net/sfu/gigenet >> _______________________________________________ >> mantisbt-dev mailing list >> man...@li... >> https://lists.sourceforge.net/lists/listinfo/mantisbt-dev > > ------------------------------------------------------------------------------ > New Year. New Location. New Benefits. New Data Center in Ashburn, VA. > GigeNET is offering a free month of service with a new server in Ashburn. > Choose from 2 high performing configs, both with 100TB of bandwidth. > Higher redundancy.Lower latency.Increased capacity.Completely compliant. > http://p.sf.net/sfu/gigenet > _______________________________________________ > mantisbt-dev mailing list > man...@li... > https://lists.sourceforge.net/lists/listinfo/mantisbt-dev |
|
From: Roland B. <ro...@at...> - 2015-01-23 20:48:43
|
Seems this approach has been used in the past https://www.mantisbt.org/bugs/view.php?id=6724 https://www.mantisbt.org/bugs/view.php?id=7743 https://www.mantisbt.org/bugs/view.php?id=8153 https://www.mantisbt.org/bugs/view.php?id=8154 > Damien Regad <dr...@ma...> hat am 23. Januar 2015 um 17:13 > geschrieben: > > > Hello again, > > I'd like your input in terms of handling / tracking of important, publicly > announced security issues (i.e having a CVE) that affect multiple versions. > > In the past, we only had a single issue in our tracker, with target/fixed in > version set to the oldest version (i.e. 1.2.x), and it was implied that the > fix was also implemented in later releases. > > This was not a problem before an "official" release for 1.3 was published, > but now that we have the beta out, I'm wondering if we should not create > "dummy" issues as clones/duplicates of the "main" ones for 1.2, but with > target/fixed version set to 1.3.x. This way the CVE IDs would appear on the > change log / roadmap. > > Thoughts ? > > > > > ------------------------------------------------------------------------------ > New Year. New Location. New Benefits. New Data Center in Ashburn, VA. > GigeNET is offering a free month of service with a new server in Ashburn. > Choose from 2 high performing configs, both with 100TB of bandwidth. > Higher redundancy.Lower latency.Increased capacity.Completely compliant. > http://p.sf.net/sfu/gigenet > _______________________________________________ > mantisbt-dev mailing list > man...@li... > https://lists.sourceforge.net/lists/listinfo/mantisbt-dev |
|
From: Roland B. <ro...@at...> - 2015-01-23 20:43:23
|
I don't see anything that would block. > Damien Regad <dr...@ma...> hat am 23. Januar 2015 um 17:08 > geschrieben: > > > Hi team, > > After fixing several security issues in 1.2.18, I got confirmation from > their respective reporters that the problems are indeed resolved, and the > CVEs have been assigned as needed. > > Therefore, unless anyone objects/has pending work that must go in, I propose > to cut 1.2.19 over the week-end (I just need to work on the release notes). > > Victor, do you think you'd be able to publish the release, maybe Sunday or > early next week ? > > Also, since several of the above-mentioned security issues affect 1.3 as > well, I would recommend that we also release 1.3.0-beta.2, either > simultaneously or very soon afterwards. > > Let me know if you see anything that would block or delay either or both > releases. > > D > > > > ------------------------------------------------------------------------------ > New Year. New Location. New Benefits. New Data Center in Ashburn, VA. > GigeNET is offering a free month of service with a new server in Ashburn. > Choose from 2 high performing configs, both with 100TB of bandwidth. > Higher redundancy.Lower latency.Increased capacity.Completely compliant. > http://p.sf.net/sfu/gigenet > _______________________________________________ > mantisbt-dev mailing list > man...@li... > https://lists.sourceforge.net/lists/listinfo/mantisbt-dev |
|
From: Damien R. <dr...@ma...> - 2015-01-23 16:14:05
|
Hello again, I'd like your input in terms of handling / tracking of important, publicly announced security issues (i.e having a CVE) that affect multiple versions. In the past, we only had a single issue in our tracker, with target/fixed in version set to the oldest version (i.e. 1.2.x), and it was implied that the fix was also implemented in later releases. This was not a problem before an "official" release for 1.3 was published, but now that we have the beta out, I'm wondering if we should not create "dummy" issues as clones/duplicates of the "main" ones for 1.2, but with target/fixed version set to 1.3.x. This way the CVE IDs would appear on the change log / roadmap. Thoughts ? |
|
From: Damien R. <dr...@ma...> - 2015-01-23 16:08:29
|
Hi team, After fixing several security issues in 1.2.18, I got confirmation from their respective reporters that the problems are indeed resolved, and the CVEs have been assigned as needed. Therefore, unless anyone objects/has pending work that must go in, I propose to cut 1.2.19 over the week-end (I just need to work on the release notes). Victor, do you think you'd be able to publish the release, maybe Sunday or early next week ? Also, since several of the above-mentioned security issues affect 1.3 as well, I would recommend that we also release 1.3.0-beta.2, either simultaneously or very soon afterwards. Let me know if you see anything that would block or delay either or both releases. D |
|
From: Thomas K. <th...@ko...> - 2015-01-23 08:43:03
|
On Friday, January 23, 2015 03:12:45 AM Elier Delgado wrote: > Hello Thomas, thanks for sharing. > > I have made public what I did so anyone can contribute. > What you did can be very useful. > > https://github.com/elier/mantis5 > > Thanks, Elier http://www.ben-morris.com/why-refactoring-code-is-almost-always-better-than-rewriting-it http://www.joelonsoftware.com/articles/fog0000000069.html Hi Elier, it's nice that you're interested in a symfony-based Mantis. So am I. However I'm afraid that developing a second Mantis in parallel will certainly not be succesful. (And I wouldn't do it in PHP, in that case...) But there would be a lot of potential in a gradual refactoring of Mantis towards a Symfony based architecture. This requires an agreement of all core devs. Developing in parallel means: - Confusion of users - additional effort to maintain two code bases - less users for the new system -> less bug reports / feedback - no continuous refactoring and compatibility testing of the many and useful mantis plugins and 3rd-party integrations (The biggest plus of Mantis nowadays is its maturity, plugins and integrations. - Not its clean code base...) Regards, Thomas Koch |
132 messages has been excluded from this view by a project administrator.