| ../irclogs/#mantishelp.2009-06-30.log | ||
| --- scribe started --- | 00:00 | |
| mantisbot | New bug: Bug 10651 - EricSWB - open - new | 03:28 |
|---|---|---|
| mantisbot | New bug: Twitter Integration not Working. - http://www.mantisbt.org/bugs/view.php?id=10651 | 03:28 |
| mantisbot | New bug: Bug 10652 - andy_mbt - open - new | 05:04 |
| mantisbot | New bug: Clean install returns errors if Mantis installed in root - http://www.mantisbt.org/bugs/view.php?id=10652 | 05:04 |
| Ruslan_Zasukhin | Hi everybody | 07:45 |
| Ruslan_Zasukhin | I'd like catch somebody from GURUs | 07:45 |
| Ruslan_Zasukhin | and discuss sub-project | 07:45 |
| Ruslan_Zasukhin | nobody here? :) | 07:47 |
| Ruslan_Zasukhin | ok I will keep window to wait | 07:47 |
| Ruslan_Zasukhin | once again I'd like talk to the main developer(s) of mantis | 07:47 |
| Ruslan_Zasukhin | about Sub-Projects | 07:47 |
| Ruslan_Zasukhin | I see logical mistake in its implemeation | 07:48 |
| Ruslan_Zasukhin | - | 07:48 |
| dhx_m | you have to wait more than 2 minutes :p | 07:48 |
| Ruslan_Zasukhin | also I feel gret need in improvement of work wih VERSIONs | 07:48 |
| Ruslan_Zasukhin | ok :) | 07:48 |
| dhx_m | have you been able to find your ideas listed at http://www.mantisbt.org/bugs/view_all_bug_page.php | 07:48 |
| dhx_m | in case someone has already reported the problems? | 07:48 |
| dhx_m | if not, that is the place to put your ideas/requests/bug reports | 07:49 |
| giallu | Ruslan_Zasukhin, go ahead with the logical mistake description, I'm curious | 07:49 |
| Ruslan_Zasukhin | I think I have self report some things in the past | 07:49 |
| dhx_m | unless you wanted to discuss things more logically | 07:49 |
| Ruslan_Zasukhin | yes I ant DISCUSS | 07:49 |
| Ruslan_Zasukhin | not jut to report :) | 07:49 |
| dhx_m | ok | 07:49 |
| dhx_m | :) | 07:49 |
| Ruslan_Zasukhin | ok I will stat description of expecttion | 07:49 |
| giallu | hey David | 07:49 |
| Ruslan_Zasukhin | first of all | 07:49 |
| dhx_m | giallu: hi :) | 07:49 |
| Ruslan_Zasukhin | we use Mantis few years | 07:49 |
| giallu | I think I did not welcomed you properly in the dev team :) WELCOME! | 07:50 |
| Ruslan_Zasukhin | for our Valentina database projecs | 07:50 |
| Ruslan_Zasukhin | http://valentina-db.com/ | 07:50 |
| Ruslan_Zasukhin | thank you | 07:50 |
| mantisbot | New bug: Bug 10653 - kraades - open - new | 07:50 |
| mantisbot | New bug: MantisBT Formatting 1.0a gives File Not Found - http://www.mantisbt.org/bugs/view.php?id=10653 | 07:50 |
| Ruslan_Zasukhin | may be bette for me go and really make REPORT ISSUE ? | 07:51 |
| Ruslan_Zasukhin | ok I will try describe more hee | 07:51 |
| Ruslan_Zasukhin | here | 07:51 |
| Ruslan_Zasukhin | in short | 07:51 |
| Ruslan_Zasukhin | RULE: SUB-PROJECT IMO is PART of big project | 07:52 |
| Ruslan_Zasukhin | this means tha if I am a project manger | 07:52 |
| Ruslan_Zasukhin | I make in mantis PROJECT A | 07:52 |
| Ruslan_Zasukhin | then I start think -- this project has 2-3-4 parts | 07:52 |
| Ruslan_Zasukhin | so I making 2-3-4 sub-projects | 07:52 |
| Ruslan_Zasukhin | PROJECT 1, PROJECT 2, .. | 07:53 |
| giallu | Ruslan_Zasukhin, FWIW, I completely agree on that | 07:53 |
| Ruslan_Zasukhin | then I adding categories to EACH sb-project | 07:53 |
| Ruslan_Zasukhin | say 10 to each | 07:53 |
| Ruslan_Zasukhin | and now | 07:53 |
| Ruslan_Zasukhin | my expactations ARE that if I watch main PROJECT | 07:53 |
| Ruslan_Zasukhin | I will see 10 + 10 + 10 +10 = 40 categories | 07:54 |
| giallu | in fact, I tried using subprojects once, then I stopped because of that | 07:54 |
| Ruslan_Zasukhin | from its sub-projects | 07:54 |
| Ruslan_Zasukhin | YES | 07:54 |
| Ruslan_Zasukhin | MISTAKE is made HERE | 07:54 |
| Ruslan_Zasukhin | in Categories !!! | 07:54 |
| Ruslan_Zasukhin | in fact Mantis do all REVERSE !?? | 07:54 |
| Ruslan_Zasukhin | i.e. I see that PROJECT 1 | 07:55 |
| Ruslan_Zasukhin | has own 10 categories | 07:55 |
| Ruslan_Zasukhin | and INHERITED 10 categories from PARENT main project | 07:55 |
| Ruslan_Zasukhin | this is WRONG! | 07:55 |
| Ruslan_Zasukhin | --- | 07:55 |
| Ruslan_Zasukhin | what is CORRECT | 07:55 |
| Ruslan_Zasukhin | is work with Issues | 07:55 |
| Ruslan_Zasukhin | here all right | 07:55 |
| Ruslan_Zasukhin | if project 1 and project 2 have EACH say 15 issues | 07:55 |
| Ruslan_Zasukhin | then when I watch issues for mai PROJECT | 07:56 |
| Ruslan_Zasukhin | for main prject | 07:56 |
| Ruslan_Zasukhin | I see all right | 07:56 |
| Ruslan_Zasukhin | I see in LIST OF ISUES | 07:56 |
| Ruslan_Zasukhin | 15 + 15 + may be issues of ain project | 07:56 |
| Ruslan_Zasukhin | i.e. I see AGREGATION of PARTS | 07:56 |
| Ruslan_Zasukhin | ---- | 07:56 |
| Ruslan_Zasukhin | It seems to me | 07:56 |
| Ruslan_Zasukhin | somebody from Mantis develpers have made logical mistake | 07:56 |
| Ruslan_Zasukhin | with categories | 07:57 |
| Ruslan_Zasukhin | and I think it should be very easy to fix | 07:57 |
| Ruslan_Zasukhin | just change diection | 07:57 |
| Ruslan_Zasukhin | in which categories are added | 07:57 |
| Ruslan_Zasukhin | NOT from PARENT to sub-pojec | 07:57 |
| Ruslan_Zasukhin | but from sub-project to PARENT - MAIN | 07:57 |
| Ruslan_Zasukhin | -- | 07:57 |
| Ruslan_Zasukhin | FINISH :) | 07:57 |
| dhx_m | giallu: thanks :) | 07:57 |
| dhx_m | brb (cooking)... will read this in a moment :) | 07:58 |
| Ruslan_Zasukhin | I think FIX wil be as easy as ONE line corrections in code :) | 07:58 |
| Ruslan_Zasukhin | --- | 08:00 |
| Ruslan_Zasukhin | let me add | 08:00 |
| Ruslan_Zasukhin | I have try workaround this probem with categories | 08:00 |
| Ruslan_Zasukhin | making REVERSE order of sub-projets | 08:00 |
| Ruslan_Zasukhin | but this is bad way because then issues looks strange | 08:01 |
| Ruslan_Zasukhin | -- | 08:01 |
| giallu | Ruslan_Zasukhin, TBH, I think you're under-estimating the effort needed to fix the issue. However, no one prevents you from trying, I'm surely supportive of changing the semantic of subprojects. | 08:16 |
| giallu | But please note the technical issue is just part of the problem. Even if you came up with a proper patch, then we need a plan for the transition, e.g. how to prepare the users already using the current subproject implementation. | 08:18 |
| Ruslan_Zasukhin | yes may be not single line | 08:19 |
| Ruslan_Zasukhin | on te othr hand | 08:19 |
| Ruslan_Zasukhin | copy of categories happens I think ONCE | 08:19 |
| Ruslan_Zasukhin | so it needs just choose correct DIRECTION | 08:19 |
| Ruslan_Zasukhin | rest code is valid. You see? | 08:20 |
| Ruslan_Zasukhin | - | 08:20 |
| Ruslan_Zasukhin | 2) sorry, I am not great PHP deveopers:) | 08:20 |
| Ruslan_Zasukhin | I am c++ | 08:20 |
| Ruslan_Zasukhin | about EXISTED users | 08:21 |
| Ruslan_Zasukhin | the most simple and flexible way is | 08:21 |
| Ruslan_Zasukhin | Version say 1.2 claims | 08:21 |
| Ruslan_Zasukhin | CHANGE : sub-projects now copy categories from PARENT to SUB-project on default | 08:21 |
| Ruslan_Zasukhin | IF you want use old behavior correct in the INI file | 08:22 |
| Ruslan_Zasukhin | opion SUBPROJECTS_COPY_CATEGORY_OLD_STYLE = TRUE | 08:22 |
| Ruslan_Zasukhin | - | 08:22 |
| Ruslan_Zasukhin | solved ? :) | 08:22 |
| Ruslan_Zasukhin | ANYWAY | 08:22 |
| Ruslan_Zasukhin | current implemetation is WRONG | 08:23 |
| Ruslan_Zasukhin | and I just wat be here in chat | 08:23 |
| Ruslan_Zasukhin | as long as neede | 08:23 |
| Ruslan_Zasukhin | to PROVE this to MAJOR mantis developers | 08:23 |
| Ruslan_Zasukhin | because it is very bad idea leave for long ime LOGICAL mistaks in the product | 08:23 |
| Ruslan_Zasukhin | this is not just a bug | 08:23 |
| Ruslan_Zasukhin | this is big logical mistake | 08:23 |
| Ruslan_Zasukhin | which is show stopper for us | 08:24 |
| Ruslan_Zasukhin | I think MANY matis users will confirm -- that sub-projects feature now is ODD and not usable | 08:24 |
| Ruslan_Zasukhin | especially if try to us it for COMPLEX hierarchy | 08:24 |
| Ruslan_Zasukhin | of projects - subprojects | 08:24 |
| Ruslan_Zasukhin | even PROJECT with TWO parts already dead way currently | 08:25 |
| Ruslan_Zasukhin | --- | 08:25 |
| Ruslan_Zasukhin | in fact | 08:25 |
| Ruslan_Zasukhin | yes I CAN try to fix this | 08:25 |
| Ruslan_Zasukhin | especaily if somebody will at least point me file/ethod | 08:26 |
| Ruslan_Zasukhin | where this logic present | 08:26 |
| Ruslan_Zasukhin | I am too busy to learn all sources of mantis | 08:26 |
| Ruslan_Zasukhin | -- | 08:26 |
| dhx_m | ok I'm starting to read now :) | 08:56 |
| dhx_m | you raise an interesting point | 08:59 |
| dhx_m | personally I don't see why you'd want to inherit categories from parent or share categories to a child | 09:00 |
| dhx_m | in most cases it doesn't make sense | 09:00 |
| Ruslan_Zasukhin | yes | 09:01 |
| Ruslan_Zasukhin | PARENT project has PARTS | 09:01 |
| Ruslan_Zasukhin | so later it should AGREGATE parts items | 09:01 |
| Ruslan_Zasukhin | items are - categories, issues, ... | 09:01 |
| Ruslan_Zasukhin | --- | 09:01 |
| Ruslan_Zasukhin | this issue is main our trouble for now with Mantis | 09:02 |
| Ruslan_Zasukhin | -- | 09:02 |
| Ruslan_Zasukhin | SECOND ISSUE I cry few months already is | 09:02 |
| Ruslan_Zasukhin | work with VERSIONs | 09:03 |
| Ruslan_Zasukhin | -- | 09:03 |
| Ruslan_Zasukhin | it is not so fatal | 09:03 |
| Ruslan_Zasukhin | it is more issue of comfortable work | 09:03 |
| Ruslan_Zasukhin | -- | 09:03 |
| Ruslan_Zasukhin | I have report ISSUE into YOUR mantis bug tracker | 09:03 |
| dhx_m | I'm not sure I understand part one first... | 09:03 |
| Ruslan_Zasukhin | as new feature : PRODUCT LINE | 09:03 |
| Ruslan_Zasukhin | -- | 09:03 |
| dhx_m | do you want categories/etc to be inherited by child projects? | 09:03 |
| dhx_m | vice versa? | 09:03 |
| dhx_m | adjustable per-category? | 09:04 |
| Ruslan_Zasukhin | mmmm | 09:04 |
| Ruslan_Zasukhin | 1) | 09:04 |
| Ruslan_Zasukhin | it needs remove word INHERIT categories ! | 09:04 |
| dhx_m | how do we display where within the hierarchy a category is? | 09:04 |
| Ruslan_Zasukhin | display as now | 09:04 |
| Ruslan_Zasukhin | PROJECT_MAIN | 09:05 |
| dhx_m | so categories shouldn't be inherited from the parent... or shared with a child? | 09:05 |
| Ruslan_Zasukhin | CAtegory_1 | 09:05 |
| Ruslan_Zasukhin | Category_2 | 09:05 |
| Ruslan_Zasukhin | [subProject_1] Catgory_1 | 09:05 |
| Ruslan_Zasukhin | -- | 09:05 |
| Ruslan_Zasukhin | no | 09:05 |
| Ruslan_Zasukhin | RIGHT NOW sub-project really INHERIT categries from PARENT | 09:06 |
| Ruslan_Zasukhin | but should be VISA VERSA | 09:06 |
| dhx_m | so if browsing a tier 1 project, you should also be able to file tickets against categories in sub projects? | 09:06 |
| Ruslan_Zasukhin | if SUB-project have { cateory_a, caegory_b } | 09:06 |
| Ruslan_Zasukhin | then PARENT project should have | 09:06 |
| Ruslan_Zasukhin | [sub_preoject_1] category_1 | 09:07 |
| Ruslan_Zasukhin | [sub_preoject_1] category_2 | 09:07 |
| Ruslan_Zasukhin | and own categories | 09:07 |
| Ruslan_Zasukhin | --- | 09:07 |
| dhx_m | I think I understand... but I'm not sure why you'd want to do that? | 09:07 |
| dhx_m | (or vice-versa for that matter) | 09:07 |
| Ruslan_Zasukhin | because sub-project is PART of main project !!! | 09:07 |
| Ruslan_Zasukhin | not visa versa | 09:07 |
| Ruslan_Zasukhin | I have Valentina Stuio PRO | 09:07 |
| dhx_m | yes... but wouldn't you want to file the bug report in the sub project, if it affects a category from the sub project? | 09:07 |
| Ruslan_Zasukhin | it MUST have | 09:07 |
| Ruslan_Zasukhin | RIGHT | 09:08 |
| Ruslan_Zasukhin | I will report issue into sub-rject | 09:08 |
| Ruslan_Zasukhin | sorry, wht is your name ? | 09:08 |
| Ruslan_Zasukhin | Mantis CORRECTLY works with ISSUES !!! | 09:09 |
| Ruslan_Zasukhin | I report issue into SUBproject 1 | 09:09 |
| Ruslan_Zasukhin | and then I see it as par of PROJECT_MAIN | 09:09 |
| Ruslan_Zasukhin | all right with issues | 09:09 |
| Ruslan_Zasukhin | AGREATION works here in Mantis | 09:09 |
| Ruslan_Zasukhin | - | 09:09 |
| Ruslan_Zasukhin | but with CATEGORIES all works visa versa!! | 09:09 |
| Ruslan_Zasukhin | ISSUES: CHILD to PARENT | 09:09 |
| Ruslan_Zasukhin | CATEGORIES: PARENT to CHILD << WRONG !! | 09:09 |
| Ruslan_Zasukhin | -- | 09:09 |
| Ruslan_Zasukhin | check this | 09:10 |
| Ruslan_Zasukhin | and you will see | 09:10 |
| Ruslan_Zasukhin | it needs FIX only categoriesbehavior | 09:10 |
| Ruslan_Zasukhin | issues already works correctly :) | 09:10 |
| Ruslan_Zasukhin | - | 09:10 |
| dhx_m | ok I understand the need now | 09:14 |
| dhx_m | but I think there may be problems when you have overlapping categories | 09:15 |
| Ruslan_Zasukhin | no problems | 09:16 |
| Ruslan_Zasukhin | mantis aleady fine solve this | 09:16 |
| Ruslan_Zasukhin | it show | 09:16 |
| dhx_m | let's say you have a "security" category as part of your sub-projects that track security bugs in your sub projects | 09:16 |
| Ruslan_Zasukhin | [project1] Category1 | 09:16 |
| Ruslan_Zasukhin | [project2] Category1 | 09:16 |
| Ruslan_Zasukhin | Category1 | 09:16 |
| Ruslan_Zasukhin | - | 09:16 |
| Ruslan_Zasukhin | so everyhting is clear and right | 09:16 |
| dhx_m | I guess what you're really asking for is a generic bug report page that can be used to file bugs in any project/sub-project? | 09:17 |
| Ruslan_Zasukhin | noooo | 09:17 |
| Ruslan_Zasukhin | I talk not about ISSUES | 09:17 |
| Ruslan_Zasukhin | I talk about CATEGORIES | 09:17 |
| Ruslan_Zasukhin | when I go to MANAGE | 09:17 |
| Ruslan_Zasukhin | MANGE PROJECTs | 09:17 |
| Ruslan_Zasukhin | CATEGORIES | 09:17 |
| Ruslan_Zasukhin | - | 09:17 |
| Ruslan_Zasukhin | ISSUES - work correctly for subprojects | 09:18 |
| dhx_m | let's say you have: | 09:19 |
| dhx_m | Project 1 | 09:19 |
| dhx_m | Subproject 1.1 | 09:19 |
| dhx_m | Subproject 1.2 | 09:19 |
| dhx_m | Project 2 | 09:19 |
| dhx_m | if you file a bug under project 1, it should show categories from subprojects 1.1 and 1.2? | 09:20 |
| giallu | Ruslan_Zasukhin, the point is, this is not really a bug, but rather a design decision. I current subproject concept implements a "inheritance" concept, while you would see a more natural fit in a "composition" concept. | 09:21 |
| Ruslan_Zasukhin | YES | 09:21 |
| Ruslan_Zasukhin | exactly | 09:22 |
| Ruslan_Zasukhin | but problem i | 09:22 |
| Ruslan_Zasukhin | is | 09:22 |
| Ruslan_Zasukhin | that CATEGORIES use INHERTANCE | 09:22 |
| Ruslan_Zasukhin | but ISSUES use COMPOSTION | 09:22 |
| Ruslan_Zasukhin | conflict !! | 09:22 |
| Ruslan_Zasukhin | must be in both cases OR inheritance only | 09:22 |
| Ruslan_Zasukhin | OR composition ony | 09:23 |
| Ruslan_Zasukhin | this is where problem is | 09:23 |
| Ruslan_Zasukhin | -- | 09:23 |
| Ruslan_Zasukhin | and ABOVE I have start story | 09:23 |
| Ruslan_Zasukhin | that PROJECT MANAGER thinks | 09:23 |
| Ruslan_Zasukhin | that sub-projects are PARTs of project | 09:23 |
| giallu | I got fooled as well | 09:24 |
| Ruslan_Zasukhin | sub-project1 has categories {a1, a2, a3, a4, a5} and issues {#1, #2, #3} | 09:24 |
| Ruslan_Zasukhin | sub-project2 has categories {b1, b2, b3, b4} and issues {#101, #102, #103} | 09:24 |
| Ruslan_Zasukhin | now PROJECT_MAIN has two subprojects | 09:24 |
| Ruslan_Zasukhin | and PROJECT_MAIN has categories {c1, c2,c3} and own issues {#51, 52, 53 54} | 09:25 |
| Ruslan_Zasukhin | -- | 09:25 |
| Ruslan_Zasukhin | now I choose in menu Projects PROJECT_MAIN | 09:25 |
| Ruslan_Zasukhin | choose LIST ISSUES | 09:25 |
| Ruslan_Zasukhin | what issues should I see? | 09:25 |
| Ruslan_Zasukhin | right! I should see issues of MAIN project itself and it sub-parts | 09:26 |
| Ruslan_Zasukhin | LIST ISSUES | 09:26 |
| Ruslan_Zasukhin | 51 | 09:26 |
| Ruslan_Zasukhin | 52 | 09:26 |
| Ruslan_Zasukhin | 53 | 09:26 |
| Ruslan_Zasukhin | 54 | 09:26 |
| Ruslan_Zasukhin | 55 | 09:26 |
| Ruslan_Zasukhin | [subproject1] 1 | 09:26 |
| Ruslan_Zasukhin | [subproject1] 2 | 09:26 |
| Ruslan_Zasukhin | [subproject1] 3 | 09:27 |
| Ruslan_Zasukhin | [subproject2] 101 | 09:27 |
| Ruslan_Zasukhin | [subproject2] 101 | 09:27 |
| Ruslan_Zasukhin | [subproject2] 103 | 09:27 |
| Ruslan_Zasukhin | -- | 09:27 |
| Ruslan_Zasukhin | EVERYBODY AGREE to this? | 09:27 |
| dhx_m | I just did some testing myself... is the main problem that manage_proj_edit_page.php doesn't create a composition of child categories (as well as inheriting parent categories)>? | 09:27 |
| Ruslan_Zasukhin | and this i how mantis works now -- ALL RIGHT HERE !! :) | 09:27 |
| dhx_m | that sounds OK to me | 09:27 |
| Ruslan_Zasukhin | YES | 09:27 |
| Ruslan_Zasukhin | and when you REPORT ISSUE | 09:27 |
| Ruslan_Zasukhin | you see WRONG list of categories in the MENU | 09:28 |
| Ruslan_Zasukhin | you see? | 09:28 |
| Ruslan_Zasukhin | -- | 09:28 |
| dhx_m | yeah I can see now | 09:28 |
| Ruslan_Zasukhin | GREAT :) | 09:28 |
| Ruslan_Zasukhin | I am happy | 09:28 |
| dhx_m | so it is a global problem | 09:28 |
| dhx_m | not just the manage page | 09:28 |
| Ruslan_Zasukhin | yes it is BIG GLOBAL problem | 09:28 |
| dhx_m | although I don't like categories inheriting/compositing without my permission :) | 09:28 |
| Ruslan_Zasukhin | with CATEGORIES and only with categories | 09:29 |
| Ruslan_Zasukhin | yes, now present checkbox | 09:29 |
| dhx_m | well we did have plans somewhere to do a similar thing with resolutions, etc | 09:29 |
| Ruslan_Zasukhin | INHERIT parent categories | 09:29 |
| Ruslan_Zasukhin | may be enough just add secnd ehavior -- AGREGATE CHILD categories ? | 09:29 |
| Ruslan_Zasukhin | - | 09:29 |
| dhx_m | yep | 09:29 |
| dhx_m | I'd be happy with that | 09:30 |
| dhx_m | I guess | 09:30 |
| dhx_m | not sure if there are any problems with sub-sub-projects though | 09:30 |
| Ruslan_Zasukhin | but note | 09:31 |
| Ruslan_Zasukhin | IMHO should be only composite | 09:31 |
| Ruslan_Zasukhin | becase I do not see sense for [x] inherit parent categories option at ll | 09:32 |
| Ruslan_Zasukhin | try to find real life example of such ? | 09:32 |
| dhx_m | I don't see a need for either actually | 09:32 |
| dhx_m | let's say I have a top level "Superproject" project | 09:33 |
| Ruslan_Zasukhin | stop | 09:33 |
| dhx_m | ok | 09:33 |
| Ruslan_Zasukhin | TOP LEVEL is MAINproject | 09:33 |
| Ruslan_Zasukhin | sub-projects are leafs | 09:33 |
| Ruslan_Zasukhin | right? | 09:33 |
| dhx_m | ok | 09:33 |
| dhx_m | but you can have sub-sub-projects | 09:33 |
| Ruslan_Zasukhin | of course | 09:33 |
| Ruslan_Zasukhin | ths is how esolve task | 09:33 |
| Ruslan_Zasukhin | complex task is splited | 09:33 |
| Ruslan_Zasukhin | - | 09:34 |
| Ruslan_Zasukhin | with coposition no problems IMHO | 09:34 |
| Ruslan_Zasukhin | Project | 09:34 |
| Ruslan_Zasukhin | ... subproject1 | 09:34 |
| dhx_m | ok I think I see what you mean... if you're filing a bug in main project | 09:34 |
| Ruslan_Zasukhin | ....... subproject 1_1 | 09:34 |
| dhx_m | you'll see categories from subproject 1_1 as well | 09:34 |
| Ruslan_Zasukhin | of couse | 09:34 |
| Ruslan_Zasukhin | right | 09:35 |
| dhx_m | and if you select one of those, the bug will be filed under subproject 1_1 instead of mainproject? | 09:35 |
| Ruslan_Zasukhin | ahaaaa | 09:35 |
| Ruslan_Zasukhin | hmm | 09:35 |
| dhx_m | it seems wrong to me that you'd file a bug in mainproject (a generic high-level project) and use a specific category from a child project | 09:36 |
| dhx_m | why aren't you filing the bug in subproject 1_1 to start with? | 09:36 |
| Ruslan_Zasukhin | yes I also do not like "smart" work in background | 09:36 |
| Ruslan_Zasukhin | then it sounds | 09:36 |
| Ruslan_Zasukhin | that all I need | 09:36 |
| Ruslan_Zasukhin | is just disable checkbox inheritance | 09:37 |
| Ruslan_Zasukhin | andbe happy ... | 09:37 |
| Ruslan_Zasukhin | and then | 09:37 |
| Ruslan_Zasukhin | its USER obligation choose correct project / sub-project | 09:37 |
| Ruslan_Zasukhin | in the menu | 09:37 |
| Ruslan_Zasukhin | to report issue into ... | 09:37 |
| Ruslan_Zasukhin | - | 09:37 |
| Ruslan_Zasukhin | and then I will get advantege from sub-projects hierarchy | 09:38 |
| Ruslan_Zasukhin | only in the LIST ISSUES | 09:38 |
| Ruslan_Zasukhin | right ? | 09:38 |
| Ruslan_Zasukhin | I will try tune in this way our mantis | 09:38 |
| Ruslan_Zasukhin | and inform you later | 09:38 |
| dhx_m | I'd argue that if an issue can be filed in a more specific project/category, that is where it belongs | 09:39 |
| Ruslan_Zasukhin | thank you for this insigt :) | 09:39 |
| Ruslan_Zasukhin | why argue? | 09:39 |
| dhx_m | filing issues in a generic/high-level category seems wrong to me when those issues can be filed in more specific categories? | 09:39 |
| Ruslan_Zasukhin | so if wehve sub-projct "REPORTS" | 09:40 |
| Ruslan_Zasukhin | user must come to mantis and choose not main project | 09:40 |
| Ruslan_Zasukhin | but this one sub-proect | 09:40 |
| Ruslan_Zasukhin | to be able see categories for REPORTs | 09:40 |
| Ruslan_Zasukhin | on the other hand this can be panful for user ... | 09:41 |
| Ruslan_Zasukhin | if MAIN project has 4 sub-projects | 09:41 |
| Ruslan_Zasukhin | then [NEW] user need spend time to find correct sub-project | 09:41 |
| Ruslan_Zasukhin | you see? | 09:41 |
| Ruslan_Zasukhin | on the other hand ...if sub-projects have correct name | 09:41 |
| Ruslan_Zasukhin | anyway let me try setup mantis here | 09:42 |
| dhx_m | ok, as long a the user knows that their issue is being filed in subproject 1_1 instead of mainproject | 09:42 |
| Ruslan_Zasukhin | in this new way | 09:42 |
| dhx_m | I agree that is a better idea | 09:42 |
| Ruslan_Zasukhin | well not sot easy | 09:53 |
| Ruslan_Zasukhin | http://www.valentina-db.com/bt/bug_report_advanced_page.php | 09:53 |
| Ruslan_Zasukhin | I have | 09:54 |
| Ruslan_Zasukhin | a) Valentina Studio PRO | 09:54 |
| Ruslan_Zasukhin | b) .... Valentina Studio | 09:54 |
| Ruslan_Zasukhin | - | 09:54 |
| Ruslan_Zasukhin | PRO is somehing more | 09:54 |
| Ruslan_Zasukhin | this is obviouse | 09:55 |
| dhx_m | wouldn't you normally have "base version" broken down into the different versions of your software? | 09:55 |
| dhx_m | where the base version is for tickets affecting all versions | 09:55 |
| Ruslan_Zasukhin | so in VStudio I have many general caegories { Dialogs, Menu, EXport/Import} | 09:56 |
| dhx_m | and then you split it into issues affecting the Pro edition and Normal edition | 09:56 |
| Ruslan_Zasukhin | yes I want split :) | 09:56 |
| dhx_m | because I assume everything in the Normal edition is part of the Pro edition... your base version is essentially then the "Normal" version | 09:56 |
| Ruslan_Zasukhin | right | 09:56 |
| Ruslan_Zasukhin | so PRO version has sub-project Normal | 09:57 |
| dhx_m | so shouldn't the heirachy be "Visual Studio -> Pro" | 09:57 |
| Ruslan_Zasukhin | I think no | 09:57 |
| Ruslan_Zasukhin | bcause look | 09:57 |
| dhx_m | I can see what you're trying to do | 09:57 |
| Ruslan_Zasukhin | we have told that BIGGER task | 09:57 |
| Ruslan_Zasukhin | must be splited to FEW smaller tasks | 09:57 |
| dhx_m | but it doesn't seem like the logical way to sort things :) | 09:57 |
| Ruslan_Zasukhin | really? | 09:57 |
| Ruslan_Zasukhin | then what if PRO | 09:58 |
| dhx_m | well it does... | 09:58 |
| Ruslan_Zasukhin | have 4 sub-projects | 09:58 |
| Ruslan_Zasukhin | you can ave 4 parents | 09:58 |
| Ruslan_Zasukhin | ops | 09:58 |
| Ruslan_Zasukhin | you cannot have 4 parents | 09:58 |
| dhx_m | but generally I think you'd say you have a "base version" which has been extended to form the "pro version" | 09:58 |
| Ruslan_Zasukhin | this is one way to think | 09:58 |
| Ruslan_Zasukhin | and this way not works for FEW parts | 09:58 |
| dhx_m | how does your model work if the software was Windows? | 09:58 |
| Ruslan_Zasukhin | Windows have only HOME and PRO ? | 09:59 |
| dhx_m | you don't really have a clean hierarchy | 09:59 |
| dhx_m | nah they have all sorts of versions now... business, ultimate, etc | 09:59 |
| dhx_m | home premium, etc | 09:59 |
| Ruslan_Zasukhin | yes | 09:59 |
| dhx_m | so the ultimate version might contain everything | 09:59 |
| dhx_m | but the business and home premium versions contain bits and pieces of ultimate, but not all | 10:00 |
| dhx_m | in other words, they do not nest | 10:00 |
| Ruslan_Zasukhin | wait | 10:00 |
| Ruslan_Zasukhin | okay let me return back | 10:00 |
| dhx_m | so where do you put home basic in this model? | 10:00 |
| Ruslan_Zasukhin | VStudio | 10:00 |
| Ruslan_Zasukhin | ... VStudio PRO | 10:00 |
| Ruslan_Zasukhin | it was in such way or coule of weeks | 10:00 |
| Ruslan_Zasukhin | 2 min please | 10:00 |
| dhx_m | yep ok | 10:00 |
| Ruslan_Zasukhin | done | 10:02 |
| Ruslan_Zasukhin | look now please here | 10:03 |
| Ruslan_Zasukhin | http://www.valentina-db.com/bt/bug_report_advanced_page.php | 10:03 |
| Ruslan_Zasukhin | and try switch menu project | 10:03 |
| Ruslan_Zasukhin | betwen VStudio and VStudio PRO | 10:03 |
| Ruslan_Zasukhin | now all looks right in caegries | 10:03 |
| Ruslan_Zasukhin | looks ... | 10:03 |
| Ruslan_Zasukhin | but now looks wrong ISSUEs | 10:03 |
| Ruslan_Zasukhin | -- | 10:04 |
| Ruslan_Zasukhin | http://www.valentina-db.com/bt/view_all_bug_page.php | 10:04 |
| Ruslan_Zasukhin | go to this URL | 10:04 |
| dhx_m | (anonymous users can't report :p) | 10:04 |
| Ruslan_Zasukhin | okay | 10:04 |
| Ruslan_Zasukhin | lets see issues only | 10:04 |
| dhx_m | ok | 10:04 |
| Ruslan_Zasukhin | choose VStudio project | 10:04 |
| Ruslan_Zasukhin | it is no PARENT of Studio PR | 10:04 |
| dhx_m | yep | 10:04 |
| Ruslan_Zasukhin | something wrong with my keyboard | 10:04 |
| Ruslan_Zasukhin | and what you see in list? | 10:05 |
| Ruslan_Zasukhin | you see issues of PRO version ... | 10:05 |
| Ruslan_Zasukhin | IMHO this is wrong | 10:05 |
| Ruslan_Zasukhin | user which have pay 100$ | 10:05 |
| Ruslan_Zasukhin | for VStudio | 10:05 |
| Ruslan_Zasukhin | do not hve PRO version for say500 | 10:05 |
| Ruslan_Zasukhin | so why he should see PRO issues ??? | 10:05 |
| Ruslan_Zasukhin | you see my trouble? | 10:05 |
| dhx_m | fair call | 10:05 |
| Ruslan_Zasukhin | in one way -- categories looks wrong | 10:06 |
| dhx_m | but I think the current model of "generic -> specific -> more specific" is right | 10:06 |
| Ruslan_Zasukhin | in othe way isues are wrong | 10:06 |
| Ruslan_Zasukhin | I think no :) | 10:06 |
| Ruslan_Zasukhin | I also have seat and think | 10:06 |
| dhx_m | what you're after seems to be an option like "show this project as a sub-project of X for users above access level: ______" | 10:06 |
| Ruslan_Zasukhin | before this discussion | 10:06 |
| Ruslan_Zasukhin | what ismore right INHERITANCE or COMPOSITION ? | 10:07 |
| Ruslan_Zasukhin | ************ | 10:07 |
| Ruslan_Zasukhin | then let again come to beginning of today talk | 10:07 |
| Ruslan_Zasukhin | how work PROJECT MANAGER? | 10:07 |
| Ruslan_Zasukhin | I have VSTudio PRO | 10:07 |
| Ruslan_Zasukhin | then I think | 10:07 |
| Ruslan_Zasukhin | it includes VStudio | 10:07 |
| Ruslan_Zasukhin | and may be else... | 10:08 |
| Ruslan_Zasukhin | - | 10:08 |
| Ruslan_Zasukhin | although from your point of view | 10:08 |
| Ruslan_Zasukhin | you have BASIC project | 10:08 |
| Ruslan_Zasukhin | and then PRO version ... | 10:08 |
| Ruslan_Zasukhin | what you're after seems to be an option like "show this project as a sub-project of X for users above access level: ______" | 10:08 |
| Ruslan_Zasukhin | then what will be adventage at all fromsub-projects ??? | 10:09 |
| Ruslan_Zasukhin | if I will not use categories | 10:09 |
| Ruslan_Zasukhin | if I will not combine issues | 10:09 |
| Ruslan_Zasukhin | ? | 10:09 |
| Ruslan_Zasukhin | then what sense n this feature? :-) | 10:09 |
| dhx_m | is your problem that you don't want non-pro users viewing bugs from the normal version? | 10:09 |
| dhx_m | you could also set project-specific thresholds | 10:09 |
| dhx_m | as to who can view issues | 10:10 |
| Ruslan_Zasukhin | yes IF to choose hierarchy as VStudio -> VStudio PRO | 10:10 |
| Ruslan_Zasukhin | but if to chose reverse hierarchy VStudioPRO -> VStudio | 10:10 |
| Ruslan_Zasukhin | then problem comes to categories | 10:10 |
| Ruslan_Zasukhin | -- | 10:10 |
| Ruslan_Zasukhin | and if to look very careful on our POJECTs | 10:11 |
| Ruslan_Zasukhin | then VStudio is combination of { VKERNEL, VCLIENT } | 10:11 |
| Ruslan_Zasukhin | VStudio PRO is combination of { VStudio, { VKERNEL, VCLIENT } } | 10:12 |
| Ruslan_Zasukhin | -- | 10:12 |
| Ruslan_Zasukhin | this is why I think inheriance is wrong way | 10:12 |
| Ruslan_Zasukhin | should be used composition way | 10:12 |
| Ruslan_Zasukhin | issue reported to KERNEL affects VStudio and VSTudio PRO | 10:13 |
| dhx_m | I agree that categories should be derived from child projects rather than parent projects | 10:13 |
| Ruslan_Zasukhin | but issues als | 10:13 |
| Ruslan_Zasukhin | also | 10:13 |
| dhx_m | yes | 10:13 |
| dhx_m | but I'm confused as to why you have set out your projects as "most specific project -> least specific project" | 10:14 |
| dhx_m | well actually | 10:14 |
| dhx_m | I think I see now | 10:14 |
| Ruslan_Zasukhin | let me try here to draw hierrchy | 10:14 |
| Ruslan_Zasukhin | ---------------- | 10:14 |
| Ruslan_Zasukhin | VKERNEL | 10:14 |
| Ruslan_Zasukhin | VCLIENT | 10:14 |
| Ruslan_Zasukhin | VREPORT | 10:14 |
| Ruslan_Zasukhin | ------------- | 10:14 |
| Ruslan_Zasukhin | VStudo conains { VKERNEL, VCLINT, VREPORT } | 10:15 |
| Ruslan_Zasukhin | VStudo PRO conains { VStudio, { VKERNEL, VCLINT, VREPORT }} | 10:15 |
| Ruslan_Zasukhin | -- | 10:15 |
| Ruslan_Zasukhin | and what we have ... | 10:15 |
| Ruslan_Zasukhin | hard pictue | 10:16 |
| Ruslan_Zasukhin | may be we have very complex schema of projects | 10:16 |
| Ruslan_Zasukhin | may be other products are much simpler | 10:16 |
| dhx_m | I understand your layout now | 10:16 |
| dhx_m | my point is that if you select VStudio, you should also see issues from VStudio Pro | 10:16 |
| Ruslan_Zasukhin | I cnnot say | 10:16 |
| Ruslan_Zasukhin | that I want that VStudio -> List Issue have show also KERNEL issues ... I cannot say this ... | 10:17 |
| dhx_m | but I can see how your method works too | 10:17 |
| Ruslan_Zasukhin | -- | 10:17 |
| Ruslan_Zasukhin | dhx_mmy point is that if you select VStudio, you should also see issues from VStudio Pro | 10:17 |
| Ruslan_Zasukhin | - | 10:17 |
| Ruslan_Zasukhin | why ?? | 10:17 |
| Ruslan_Zasukhin | I thik REVERSE | 10:17 |
| Ruslan_Zasukhin | PRO list should include basic issues | 10:18 |
| Ruslan_Zasukhin | but not visa versa | 10:18 |
| Ruslan_Zasukhin | - | 10:18 |
| dhx_m | because if you have an issue in VStudio, it'll also affect VStudio Pro | 10:18 |
| Ruslan_Zasukhin | right? | 10:18 |
| Ruslan_Zasukhin | but above you give reverse rule | 10:18 |
| Ruslan_Zasukhin | read carfefully | 10:18 |
| dhx_m | I'm all for getting rid of all sense of hierarchy in favour of something else :) | 10:19 |
| dhx_m | yep | 10:19 |
| Ruslan_Zasukhin | list of PRO should show issues of BASIC version | 10:19 |
| Ruslan_Zasukhin | PRO contains basic | 10:19 |
| dhx_m | but when you're filing a bug against VStudio Pro... there aren't going to be any VStudio categories to use anyway | 10:19 |
| dhx_m | because VStudio Pro contains them all | 10:20 |
| Ruslan_Zasukhin | may be really best way -- do atomatic placement of issue | 10:20 |
| Ruslan_Zasukhin | into project of choosed category? | 10:20 |
| Ruslan_Zasukhin | in this way we get strict normalisation | 10:21 |
| Ruslan_Zasukhin | - | 10:21 |
| Ruslan_Zasukhin | even future idea | 10:21 |
| Ruslan_Zasukhin | I Can have PROJECT_MAIN | 10:21 |
| Ruslan_Zasukhin | in mantis splited to 4 sub-projects | 10:21 |
| Ruslan_Zasukhin | but I mark 4 sub projects as "hidden" | 10:21 |
| dhx_m | maybe we need a heterarchial model (http://en.wikipedia.org/wiki/Heterarchy) | 10:22 |
| Ruslan_Zasukhin | and then USER in the menu seeonly SINGLE option | 10:22 |
| Ruslan_Zasukhin | I think this is to complex | 10:23 |
| Ruslan_Zasukhin | can you try accept next TWO points | 10:23 |
| Ruslan_Zasukhin | a) FORGET about word and behavior INHERITANCE | 10:23 |
| Ruslan_Zasukhin | b)try to think and resolve all taks with COMPOSITION | 10:23 |
| Ruslan_Zasukhin | -- | 10:23 |
| Ruslan_Zasukhin | and then see how picture becomes looks | 10:24 |
| Ruslan_Zasukhin | we can think yes | 10:24 |
| Ruslan_Zasukhin | that each sub-project | 10:24 |
| Ruslan_Zasukhin | is managed by separate team of developers | 10:24 |
| Ruslan_Zasukhin | right? | 10:24 |
| Ruslan_Zasukhin | so user come to VStudio PRO | 10:24 |
| Ruslan_Zasukhin | he see list of COBINATION of all categories from 5 sub-projects | 10:25 |
| Ruslan_Zasukhin | [VREPORT] xxx | 10:25 |
| dhx_m | yep | 10:25 |
| Ruslan_Zasukhin | [VCLIENT] yyy | 10:25 |
| Ruslan_Zasukhin | [VStudio] dddd | 10:25 |
| Ruslan_Zasukhin | he choose category as he think | 10:25 |
| Ruslan_Zasukhin | report issue | 10:25 |
| dhx_m | but why would you have categories within your VStudio project? | 10:25 |
| Ruslan_Zasukhin | and issue REALLY go to corresponded project | 10:25 |
| dhx_m | they'd all be contained within VStudio Pro | 10:25 |
| Ruslan_Zasukhin | because VStudio have e.g. Menus | 10:26 |
| Ruslan_Zasukhin | dialogs | 10:26 |
| Ruslan_Zasukhin | import export | 10:26 |
| Ruslan_Zasukhin | KERNEL do not have any GUI things | 10:26 |
| dhx_m | I don't think this can be solved with a hierarchy, but I could be wrong | 10:26 |
| Ruslan_Zasukhin | VS PRO later added VREPORT plus PROJECT window | 10:26 |
| Ruslan_Zasukhin | 3 min br | 10:26 |
| dhx_m | vreport/vclient are children of VStudio *and* VStudio Pro | 10:26 |
| dhx_m | in a hierarchy you can't have multiple parents... each node is a subordinate of a single other node | 10:27 |
| Ruslan_Zasukhin | back | 10:34 |
| Ruslan_Zasukhin | I keep thinking and talk | 10:34 |
| Ruslan_Zasukhin | -- | 10:34 |
| Ruslan_Zasukhin | CHILD project!! right! | 10:35 |
| Ruslan_Zasukhin | you self havesay this word now | 10:35 |
| Ruslan_Zasukhin | current sub-projects in fact are made as CHILD-projects | 10:35 |
| Ruslan_Zasukhin | PARENT-child, inheritance | 10:35 |
| Ruslan_Zasukhin | -- | 10:35 |
| Ruslan_Zasukhin | so I vote to RENAME sub-projects in child-rojects | 10:35 |
| Ruslan_Zasukhin | in the current bavior | 10:35 |
| Ruslan_Zasukhin | - | 10:35 |
| Ruslan_Zasukhin | no you have ways | 10:36 |
| Ruslan_Zasukhin | add also real sub-projects | 10:36 |
| Ruslan_Zasukhin | whih behave as PARTs of main | 10:36 |
| Ruslan_Zasukhin | and main use agregation | 10:36 |
| Ruslan_Zasukhin | - | 10:36 |
| Ruslan_Zasukhin | may be this is the only way | 10:36 |
| Ruslan_Zasukhin | so WE users of mantis can choose way which is better for us | 10:36 |
| Ruslan_Zasukhin | at last of end OOP have both these ways | 10:37 |
| Ruslan_Zasukhin | :) | 10:37 |
| Ruslan_Zasukhin | ------------ | 10:37 |
| Ruslan_Zasukhin | next point | 10:37 |
| Ruslan_Zasukhin | yes no way to have multiple parents | 10:37 |
| Ruslan_Zasukhin | and no need | 10:37 |
| Ruslan_Zasukhin | for me | 10:37 |
| Ruslan_Zasukhin | I need only multiple parts | 10:37 |
| Ruslan_Zasukhin | ad GUI of mantis right now allow this with button ADD SUB-project | 10:38 |
| Ruslan_Zasukhin | - | 10:38 |
| Ruslan_Zasukhin | N-dimension | 10:38 |
| Ruslan_Zasukhin | keep in mind this word | 10:38 |
| Ruslan_Zasukhin | N-dimenssion | 10:38 |
| Ruslan_Zasukhin | -- | 10:38 |
| Ruslan_Zasukhin | we slit TASK/PROJECT into few dimensions | 10:38 |
| Ruslan_Zasukhin | * Projects | 10:38 |
| Ruslan_Zasukhin | * versions | 10:39 |
| Ruslan_Zasukhin | * issues | 10:39 |
| Ruslan_Zasukhin | *users | 10:39 |
| Ruslan_Zasukhin | and we must be able comine easy | 10:39 |
| Ruslan_Zasukhin | into ay combination of dimensios | 10:39 |
| Ruslan_Zasukhin | and make easy any CUT of this N-space :) | 10:39 |
| Ruslan_Zasukhin | -- | 10:39 |
| Ruslan_Zasukhin | this is I have smoke here a little :) | 10:40 |
| Ruslan_Zasukhin | -- | 10:40 |
| dhx_m | I agree that your model has benefits | 10:41 |
| dhx_m | but IMO it really needs to be changed to a heterarchy model | 10:44 |
| dhx_m | in your case you should really have vkernel, vreport, etc as child projects of vstudio *and* vstudio pro | 10:46 |
| dhx_m | not just as a child of vstudio pro | 10:46 |
| [KK]Kirill | dhx_m: hi | 10:46 |
| dhx_m | [KK]Kirill: hi | 10:46 |
| [KK]Kirill | Ruslan_Zasukhin: ðÒÉ×ÅÔ | 10:46 |
| dhx_m | [KK]Kirill: does your IRC client support UTF-8... I don't see Russian :) | 10:47 |
| [KK]Kirill | Dav, Yes | 10:47 |
| dhx_m | æäºžéžä¸‰å¤§æ´² | 10:48 |
| dhx_m | does that show up as Chinese for you? | 10:48 |
| [KK]Kirill | not | 10:48 |
| dhx_m | and does this show as Russian: ðÒÉ×ÅÔ | 10:48 |
| dhx_m | ok | 10:48 |
| [KK]Kirill | yes | 10:48 |
| dhx_m | I'm using X-Chat | 10:48 |
| [KK]Kirill | Miranda forever :) | 10:49 |
| Ruslan_Zasukhin | --------------- | 10:49 |
| dhx_m | ðÒÉ×ÅÔ shows as random characters (to me it looks like what could possibly be a Russian codepage... not UTF-8 though) | 10:49 |
| Ruslan_Zasukhin | --- | 10:49 |
| Ruslan_Zasukhin | hx_min your case you should really have vkernel, vreport, etc as child projects of vstudio *and* vstudio pro | 10:49 |
| Ruslan_Zasukhin | -- | 10:49 |
| Ruslan_Zasukhin | NO NO and again no | 10:49 |
| Ruslan_Zasukhin | because even historically | 10:49 |
| Ruslan_Zasukhin | at first we did have VKERNEL | 10:49 |
| Ruslan_Zasukhin | then was boned VCLIENT | 10:49 |
| Ruslan_Zasukhin | they was used in such products without GUI as Valentina for COM | 10:50 |
| Ruslan_Zasukhin | then was borned Valentina Server | 10:50 |
| Ruslan_Zasukhin | and then was borned Valentina Studio | 10:50 |
| Ruslan_Zasukhin | you see? | 10:50 |
| Ruslan_Zasukhin | so EXACTLY will be not correct | 10:50 |
| Ruslan_Zasukhin | consider VKENREL as child project of VStudio | 10:50 |
| Ruslan_Zasukhin | NEVER | 10:50 |
| Ruslan_Zasukhin | :) | 10:50 |
| Ruslan_Zasukhin | --- | 10:50 |
| dhx_m | Ruslan_Zasukhin: I don't know anything about your software... but I thought you said VStudio consists of vreport, etc | 10:50 |
| Ruslan_Zasukhin | right | 10:51 |
| Ruslan_Zasukhin | VStudio when was born | 10:51 |
| Ruslan_Zasukhin | USES | 10:51 |
| Ruslan_Zasukhin | INCLUDES | 10:51 |
| Ruslan_Zasukhin | already exised | 10:51 |
| Ruslan_Zasukhin | VKERNEL.dll -- which is db engine | 10:51 |
| dhx_m | ok how about we talk about something we both know :p | 10:51 |
| Ruslan_Zasukhin | VCLIENT.dLL which is socket library to talk to remote VSERVER | 10:51 |
| Ruslan_Zasukhin | - | 10:51 |
| Ruslan_Zasukhin | yes :) | 10:51 |
| dhx_m | let's say you have Windows Home and Windows Pro as projects | 10:52 |
| dhx_m | and you have a subproject "Notepad" | 10:52 |
| Ruslan_Zasukhin | so againINHERITANCE do not works here | 10:52 |
| Ruslan_Zasukhin | subproject "Notepad" | 10:52 |
| Ruslan_Zasukhin | I think it is not subproject | 10:52 |
| Ruslan_Zasukhin | is STANDALONE | 10:52 |
| dhx_m | where does Notepad fit into the scheme of things? | 10:52 |
| Ruslan_Zasukhin | independent project | 10:52 |
| dhx_m | well I'd do that too | 10:52 |
| dhx_m | maybe not the best example then | 10:53 |
| dhx_m | ok | 10:53 |
| dhx_m | we can make that work... | 10:53 |
| dhx_m | you have a Windows project | 10:53 |
| dhx_m | which consists of sub projects... "Notepad", "Windows Home" and "Windows Pro"? | 10:53 |
| dhx_m | if you tried to model Mantis for use across all of Microsoft | 10:54 |
| dhx_m | top level projects might be "Office", "Windows", etc | 10:54 |
| dhx_m | but you'd have different development teams for different versions (Windows 7 team vs Windows Vista team) | 10:54 |
| dhx_m | and of course a lot of overlap | 10:54 |
| Ruslan_Zasukhin | but try to think about COMPOSE way | 10:55 |
| dhx_m | more likely there is a "Shell" and "Kernel" division at Microsoft that are "hired" by the Windows 7 or Windows Vista teams to fix a bug or add a feature | 10:55 |
| Ruslan_Zasukhin | yes | 10:55 |
| dhx_m | so Windows 7 is a project... as is Windows Vista | 10:56 |
| dhx_m | they all have releases, etc | 10:56 |
| Ruslan_Zasukhin | I'd say PUBLIC projects | 10:56 |
| dhx_m | now something like IE8 is also a project | 10:56 |
| Ruslan_Zasukhin | and behind of wall can be PARTS of that | 10:56 |
| dhx_m | but it is intended to be part of the Windows 7 project... and *also* operate on Vista | 10:56 |
| Ruslan_Zasukhin | yes I see complexi what you want o show :) | 10:57 |
| dhx_m | to make matters worse, Office depends upon IE8 too :p | 10:57 |
| [KK]Kirill | dhx_m: did you siebrand today? | 10:58 |
| dhx_m | [KK]Kirill: nope | 10:58 |
| Ruslan_Zasukhin | but I can argue | 10:58 |
| Ruslan_Zasukhin | Win7 inncludes IE8 only as bindle part | 10:58 |
| Ruslan_Zasukhin | marketing bundle | 10:59 |
| Ruslan_Zasukhin | IE8 team have own PROJECT | 10:59 |
| Ruslan_Zasukhin | and list of TODO tasks | 10:59 |
| Ruslan_Zasukhin | if they find bug in Win7 they repot to other team | 10:59 |
| Ruslan_Zasukhin | we now should think about developer teams I think | 10:59 |
| Ruslan_Zasukhin | nt about MARKETING bundles | 10:59 |
| Ruslan_Zasukhin | - | 10:59 |
| dhx_m | well this is heading towards the direction I apply in practice... don't use sub projects :p | 11:00 |
| Ruslan_Zasukhin | back to my task | 11:01 |
| Ruslan_Zasukhin | I have again made VStudio PRO >> VSTudio | 11:01 |
| dhx_m | the relationship between projects is just too complex to model (while retaining any usefulness) IMO | 11:01 |
| Ruslan_Zasukhin | so now issues show correct from my point o view LIST OF PRO shows VStudio | 11:01 |
| Ruslan_Zasukhin | I hae dsable inheritance of categories | 11:02 |
| Ruslan_Zasukhin | and NOW I see | 11:02 |
| dhx_m | I agree that what you're seeing now is correct | 11:02 |
| Ruslan_Zasukhin | that I ca reach my goal in MANUAL way | 11:02 |
| Ruslan_Zasukhin | I can just COPY all categories from VStudio to VStudio PRO | 11:02 |
| Ruslan_Zasukhin | but this wil be painful future | 11:02 |
| Ruslan_Zasukhin | it will be not easy REMOVE them :) | 11:02 |
| Ruslan_Zasukhin | if Iwill need that | 11:03 |
| dhx_m | yep | 11:03 |
| Ruslan_Zasukhin | [x] Inherit Cateories -- is more comfotable mechanism here | 11:03 |
| Ruslan_Zasukhin | - | 11:03 |
| Ruslan_Zasukhin | so my dream so far | 11:03 |
| Ruslan_Zasukhin | could be jus tohave option | 11:03 |
| Ruslan_Zasukhin | [] inherit from CHILD-project | 11:04 |
| Ruslan_Zasukhin | - | 11:04 |
| aptituz | hi | 11:05 |
| aptituz | paul_, nuclear_eclipse: do you remember the state of affairs with respect to adodb in mantis? do you still have modifications around for it that are not applied upstream? | 11:07 |
| dhx_m | Ruslan_Zasukhin: the best place to record this is in a new ticket at mantisbt.org assuming one doesn't already exist | 11:08 |
| dhx_m | Ruslan_Zasukhin: that way all developers will see it | 11:09 |
| Ruslan_Zasukhin | question is | 11:10 |
| Ruslan_Zasukhin | what we have aree on ? | 11:10 |
| Ruslan_Zasukhin | so far I am not sure :) | 11:10 |
| Ruslan_Zasukhin | 1) rename sub-projects to child-projects ? | 11:10 |
| Ruslan_Zasukhin | yes no ? | 11:10 |
| Ruslan_Zasukhin | -- | 11:10 |
| Ruslan_Zasukhin | 2) you agree that now prsent conflict in the implementation | 11:10 |
| Ruslan_Zasukhin | categories go from PARENT to CHILD | 11:11 |
| Ruslan_Zasukhin | issues go from CHILD to PARENT | 11:11 |
| Ruslan_Zasukhin | should be the same in both case-sensitive | 11:11 |
| Ruslan_Zasukhin | yes no ? | 11:11 |
| Ruslan_Zasukhin | --- | 11:11 |
| Ruslan_Zasukhin | 3) ADD NEW FEATURE --- inherit categoies from child-proect | 11:11 |
| Ruslan_Zasukhin | -- | 11:11 |
| Ruslan_Zasukhin | 4) else ? | 11:12 |
| dhx_m | yep I think so | 11:12 |
| Ruslan_Zasukhin | - | 11:12 |
| giallu | aptituz, see README file in library/ | 11:13 |
| dhx_m | giallu: it may be out of date? | 11:13 |
| dhx_m | giallu: oh ok seems right to me | 11:13 |
| dhx_m | giallu: except ezc is a trunk version not 2008.2.3 (I think) | 11:14 |
| aptituz | giallu: in tgit | 11:14 |
| aptituz | in git? i meant | 11:14 |
| aptituz | should not try to touch type when one of my hands is busy with holding an ice | 11:15 |
| dhx_m | paul_: why does setting fixed_in_version on a bug object require handle_bug_threshold? | 11:15 |
| dhx_m | paul_: I guess it might just be misunderstanding/lack of proper use of this variable... because bug_report_advanced_page requires handle_bug_threshold to set the priority | 11:20 |
| dhx_m | paul_: bug_update_advanced_page will happily let "anyone" update the priority | 11:20 |
| nuclear_eclipse | aptituz: I'm not sure about 1.1, but in 1.2, all libraries are now documented as to what patches they have applied (if any) | 11:46 |
| nuclear_eclipse | Ruslan_Zasukhin likes to hear himself type, I think :P | 11:47 |
| nuclear_eclipse | that is one *helluva* long backlog... | 11:47 |
| dhx_m | haha | 11:47 |
| dhx_m | nuclear_eclipse: want the summary? | 11:47 |
| nuclear_eclipse | yes please | 11:47 |
| dhx_m | nuclear_eclipse: when viewing a project, you also view the issues from the child sub projects | 11:48 |
| dhx_m | when reporting an issue to a project, you don't also see the categories from the sub projects | 11:48 |
| dhx_m | then I argued that the project/subproject system shouldn't be a hierarchy but instead should be a heterarchy (http://en.wikipedia.org/wiki/Heterarchy) | 11:49 |
| dhx_m | basically his point was that you should always see an aggregation of child projects, rather than an inheritance of parent projects | 11:50 |
| dhx_m | with respect to issues, categories, whatever else | 11:51 |
| nuclear_eclipse | that sounds insane to manage/deal with.. | 11:51 |
| nuclear_eclipse | eg, you have 10 subprojects, and instantly your main project becomes completely overwhelmed with options/data.... | 11:52 |
| dhx_m | yep that's why I also said that we should just do away with subprojects because the complexity overwhelms the benefits | 11:52 |
| nuclear_eclipse | well, I would disagree with that... | 11:52 |
| dhx_m | the only reason the current system sort of works is because it is mostly just a cosmetic thing | 11:53 |
| nuclear_eclipse | subprojects can be very useful as they currently are, without getting overly complex... | 11:53 |
| dhx_m | with exception of categories | 11:53 |
| dhx_m | or for projects which work nicely under a hierarchial structure | 11:54 |
| dhx_m | I was basically raising points like "why can't a project have multiple parents", etc | 11:54 |
| dhx_m | the example I gave was Microsoft Windows/Office/IE8 | 11:55 |
| nuclear_eclipse | actually, a project *can* have multiple parents... | 11:56 |
| dhx_m | just not via the UI? | 11:57 |
| nuclear_eclipse | no, you can do it in the ui | 11:57 |
| Ruslan_Zasukhin | guys wait few hours please | 11:57 |
| dhx_m | ah ok in that case it already is a heterarchy :) | 11:57 |
| Ruslan_Zasukhin | I try now make in Photoshop | 11:57 |
| Ruslan_Zasukhin | ew pitures how CAN looks a dream | 11:57 |
| Ruslan_Zasukhin | this may help to all | 11:57 |
| Ruslan_Zasukhin | better see picture | 11:58 |
| dhx_m | yep :) | 11:58 |
| nuclear_eclipse | dhx_m: just go to the second parent, select the subproject from the list, and click Add as Subproject -- bam, multi-parented subproject :) | 11:58 |
| dhx_m | nuclear_eclipse: great :) | 11:59 |
| nuclear_eclipse | anywho, time to go to work | 11:59 |
| nuclear_eclipse | bbiab | 11:59 |
| dhx_m | nuclear_eclipse: any idea on what handle_bug_threshold is meant to be? | 11:59 |
| dhx_m | nuclear_eclipse: when you get back... :) | 11:59 |
| nuclear_eclipse | who can be assigned to a bug | 11:59 |
| dhx_m | well I was wondering why it has other uses throughout the code | 11:59 |
| dhx_m | bug_report_advanced_page won't show the priority if the user is below that threshold | 12:00 |
| nuclear_eclipse | can't answer that without seeing | 12:00 |
| nuclear_eclipse | afk | 12:00 |
| dhx_m | bug_api won't let you update fixed_in_version unless you're above that threshold, etc | 12:00 |
| dhx_m | ok | 12:00 |
| Ruslan_Zasukhin | okay guys | 12:08 |
| Ruslan_Zasukhin | I give up :( | 12:08 |
| Ruslan_Zasukhin | I will just remove sub-projects relations from our mantis | 12:09 |
| Ruslan_Zasukhin | because it becomes crasy | 12:09 |
| Ruslan_Zasukhin | - | 12:09 |
| dhx_m | ? | 12:23 |
| nuclear_eclipse | back | 12:41 |
| nuclear_eclipse | I have a good feeling that paul_ completely broke everything with his changes to bug_api :P | 12:41 |
| dhx_m | actually I like where bug_api could go | 12:46 |
| dhx_m | for instance... putting a lot of the access checks in bug_api instead of scattered throughout the code | 12:46 |
| nuclear_eclipse | oh right, I agree | 12:46 |
| dhx_m | and renaming them to be consistent | 12:46 |
| dhx_m | like priority_change_threshold | 12:47 |
| dhx_m | severity_change_threshold | 12:47 |
| dhx_m | whatever else | 12:47 |
| dhx_m | instead of using handle_bug_threshold to mean 100 different things in different parts of the code | 12:47 |
| nuclear_eclipse | well, I think update_bug_threshold should be used in place of handle_bug_threshold... | 12:48 |
| nuclear_eclipse | I'd rather *not* see a new threshold for everything single field.... | 12:48 |
| dhx_m | I think it'd be useful | 12:52 |
| dhx_m | seems to be requested a lot | 12:53 |
| nuclear_eclipse | more thresholds = more complication.... | 12:53 |
| dhx_m | I was thinking it should behave more like the custom field options | 12:53 |
| dhx_m | true | 12:53 |
| dhx_m | but most wouldn't need to modify it | 12:53 |
| dhx_m | I was partly thinking of having some sort of "configuration template" thing | 12:54 |
| dhx_m | where we provide a number of different config_default's for different setups | 12:54 |
| dhx_m | a lot of people seem to be using their own 'tester' threshold for instance | 12:54 |
| nuclear_eclipse | don't make me stab you again.... | 12:54 |
| dhx_m | well there are different development styles :p | 12:54 |
| nuclear_eclipse | afk, meeting | 12:55 |
| dhx_m | all we need is a read/write threshold for each built in field IMO | 12:55 |
| dhx_m | that way it is consistent with custom fields too, making it much easier for users to understand | 12:56 |
| dhx_m | rather than have lots of separate settings thrown all over the place like update_bug_threshold, handle_bug_threshold, etc | 12:56 |
| dhx_m | ok | 12:56 |
| escamoteur | I just installed mantis. When selecting "Manage Configuration" I get an Application error #700 | 15:11 |
| escamoteur | Can anybody help with my problem? | 15:23 |
| nuclear_eclipse | escamoteur: what version of mantis? | 15:25 |
| escamoteur | 1.1.1 | 15:26 |
| nuclear_eclipse | you should upgrade | 15:26 |
| nuclear_eclipse | the latest version is 1.1.8 | 15:26 |
| escamoteur | The problem is, that this is a prepared package of my web hoster | 15:26 |
| nuclear_eclipse | then I'm afraid we can't help you | 15:27 |
| escamoteur | Can I install mantis from scratch without direct access to the server? | 15:27 |
| nuclear_eclipse | there have been a large number of bug and security fixes since 1.1.1, and your web host should be updating their packages for the safety of their customers | 15:27 |
| escamoteur | I sure will tell them. | 15:28 |
| escamoteur | What about 1.2? | 15:28 |
| nuclear_eclipse | 1.2 is in release candidate phase | 15:28 |
| escamoteur | aahh | 15:28 |
| escamoteur | Ok, so I will dive into manualy install mantis | 15:29 |
| nuclear_eclipse | 1.1 will still receive security fixes for a while though, so having your web host upgrade to 1.1.8 is the best course of action | 15:29 |
| escamoteur | No I think I will install 1.1.8 on my own. After all it's just a PHP-Application so this should be possible | 15:31 |
| Chillax_ | is there a reason that my email settings on the bug tracker are suddenly being ignored? | 16:25 |
| ruslan_zasukhin1 | hi all again | 16:42 |
| ruslan_zasukhin1 | I have report few issues | 16:42 |
| ruslan_zasukhin1 | about sub-projects | 16:43 |
| ruslan_zasukhin1 | from 10658 to 10662 | 16:43 |
| ruslan_zasukhin1 | -- | 16:43 |
| paul_ | wtf | 17:06 |
| paul_ | that was long | 17:06 |
| * paul_ got bored reading | 17:06 | |
| paul_ | dhx: that's what it used to require | 17:07 |
| dhx_m | Chillax: I can confirm that issue | 17:09 |
| Chillax | dhx_m: good, glad it wasn't just me | 17:09 |
| dhx_m | paul_: did something change recently (phpmailer upgrade?) which may have caused email to stop working correctly? | 17:09 |
| dhx_m | paul_: btw thanks for the heads up, I think I'll remove that check | 17:09 |
| Chillax | i think its more about the emails not obeying user settings for when they do and do not want to receive emails | 17:10 |
| dhx_m | Chillax: do you get any emails? | 17:10 |
| Chillax | for example, i have my notify of new turned off and yet still get emails every time a bug is filed | 17:10 |
| dhx_m | oh | 17:10 |
| dhx_m | I'm having a different problem :p | 17:10 |
| Chillax | heh | 17:10 |
| Chillax | are you not getting any emails dhx_m ? | 17:10 |
| dhx_m | Chillax: might be my fault, I'm checking now :) | 17:11 |
| Chillax | also is there a reason i only have the option for America/New York as my timezone? | 17:12 |
| dhx_m | Chillax: you need PHP 5.2 I think | 17:12 |
| Chillax | dhx_m: im talking about bugs.mantisbt.org | 17:12 |
| nuclear_eclipse | Chillax: PHP 5.1 does not have a native implementation for listing all available timezones, so for the time being, users with PHP 5.1 will only see the server's current timezone | 17:13 |
| dhx_m | Chillax: that runs on PHP 5.1 I believe :) | 17:13 |
| nuclear_eclipse | and yes, our server only runs PHP 5.1 atm | 17:13 |
| paul_ | dhx_m: mm? | 17:13 |
| paul_ | nuclear_eclipse: 5.1 does have | 17:13 |
| dhx_m | paul_: error_log for apache tells me sendmail fails to connect to "mail" on port 25 | 17:13 |
| paul_ | nuclear_eclipse: some distributions choose to patch stuff out of php | 17:13 |
| dhx_m | paul_: I'm using PHPMAILER_METHOD_MAIL | 17:14 |
| paul_ | dhx_m: hmm, unknown | 17:14 |
| dhx_m | paul_: and php.ini hasn't overridden anything | 17:14 |
| dhx_m | paul_: ok | 17:14 |
| paul_ | dhx_m: but that check for bug update or whatever you refer to | 17:14 |
| paul_ | has always been there | 17:14 |
| dhx_m | yep | 17:14 |
| dhx_m | was wondering what it was doing there :p | 17:14 |
| Chillax | how long has 1.2rc2 been running on bugs.mantis? anyone know? | 17:14 |
| dhx_m | rc1 ;) | 17:14 |
| dhx_m | since it was released | 17:14 |
| paul_ | nuclear_eclipse: imo, it's a distribution problem | 17:15 |
| dhx_m | and before that it was running a git version | 17:15 |
| paul_ | nuclear_eclipse: if they choose not to use the php bundled timezones | 17:15 |
| paul_ | nuclear_eclipse: but patch it out to use system timezone db | 17:15 |
| paul_ | nuclear_eclipse: then they should patch commands to work too | 17:15 |
| Chillax | rc1, right... ok so is there some bug with it that makes it ignore user email settings or has nobody else experienced this? | 17:15 |
| paul_ | nuclear_eclipse: (or just not patch it out in the first place) | 17:15 |
| dhx_m | Chillax: any email setting in particular... or all of them? | 17:15 |
| dhx_m | Chillax: also are the emails you receive for actions you perform yourself? | 17:16 |
| Chillax | well specifically, i get new bugs when i have email on new unchecked | 17:16 |
| Chillax | negative | 17:16 |
| dhx_m | I think I noticed that too... would have to test again | 17:16 |
| dhx_m | stupid email validation doesn't like username@localhost :p | 17:17 |
| nuclear_eclipse | paul_: it's not a matter of them patching it out -- it's a matter of it only being available in PHP 5.1 as an external/extra library -- it was only included in core as of PHP 5.2 | 17:18 |
| paul_ | nuclear_eclipse: http://derickrethans.nl/distributions_please_dont_cripple_php_or_red_hat_stop_fucking_around.php | 17:18 |
| nuclear_eclipse | or at least that's what I gleaned from reading about it | 17:18 |
| nuclear_eclipse | anywho, I gotta head out -- gots to do alot of paperwork for buying a home | 17:19 |
| paul_ | you might be right actually | 17:19 |
| nuclear_eclipse | cheers all | 17:19 |
| paul_ | either way it's partly a distribution problem | 17:19 |
| dhx_m | lol paul_ : nice ticket :p | 17:19 |
| paul_ | ? | 17:19 |
| Chillax | dhx_m: how about if you uncheck all your email boxes in preferences on bugs.mantis and i will submit a ticket, then let me know if you get it sent to you | 17:20 |
| paul_ | "In the near future, when PHP 5.3 comes out, the timezone database that is bundled with PHP will no longer be compatible with the system version of the timezone database. I've mentioned that this could happen before. This change is made to provide extra functionality, and as a side effect breaks those stupid crippling patches that RedHat thought was a good idea" | 17:20 |
| Chillax | btw near future = now. | 17:20 |
| paul_ | Chillax: i've been running 5.3 for last 2-3 days | 17:21 |
| paul_ | erm 5.3.0 | 17:21 |
| dhx_m | Chillax: would prefer not to test on the proper bug tracker :) | 17:22 |
| dhx_m | Chillax: I'm running some tests locally at the moment | 17:22 |
| paul_ | dhx_m: when aptituz gets back | 17:22 |
| paul_ | i can speak to him about adodb | 17:23 |
| paul_ | and what we bundle | 17:23 |
| paul_ | in fact, can probably do it across all libs | 17:23 |
| dhx_m | Chillax: actually you're right... I do get emails on new issues from mantisbt.org even though "E-mail on New" was unchecked | 17:23 |
| dhx_m | paul_: PHP 5.3 doesn't use the system timezone data anymore? :o | 17:24 |
| paul_ | 5.2 didn' | 17:24 |
| paul_ | RH patched php not to | 17:24 |
| paul_ | some distributions copied | 17:24 |
| paul_ | get impression php guys not impressed | 17:25 |
| dhx_m | paul_: that's odd... what is wrong with pulling it from /usr/share/zoneinfo | 17:25 |
| dhx_m | paul_: probably Windoze? :p | 17:25 |
| paul_ | PHP wanted a) consistent behaviour for web apps across platforms | 17:25 |
| paul_ | b) have introduced new timezone functions | 17:25 |
| paul_ | c) would need to bundle for windows | 17:26 |
| paul_ | from reading derick's blog (and he codes the timezone stuff) | 17:26 |
| paul_ | it suggests they've now added more timezone functionality that's not in the common system stuff | 17:26 |
| dhx_m | I can see the argument | 17:26 |
| dhx_m | but it won't fly with the RH/Debian crowd | 17:27 |
| paul_ | http://wordpress.org/support/topic/278495 | 17:27 |
| paul_ | erm wrong post | 17:27 |
| dhx_m | who like to pick a version and backport patches to it for years | 17:27 |
| dhx_m | rather than increment the version number from upstream | 17:27 |
| paul_ | http://www.2s2d.net/2009/06/17/wordpress-2-8-timezone-bug-fix/ | 17:28 |
| paul_ | wordpress2.8 breaks for this reason | 17:28 |
| dhx_m | heh | 17:28 |
| paul_ | I dont really get it tbh | 17:29 |
| paul_ | RH must get constant grief in both directions | 17:30 |
| paul_ | we need neweset php for our webapps | 17:30 |
| paul_ | we dont want to update all the time in case it breaks | 17:30 |
| dhx_m | Chillax: I might have identified the problem... I don't think we do any check for e-mail on new anymore (?) | 17:30 |
| Chillax | heh "oops" | 17:30 |
| dhx_m | IMO they need to provide both... but they do that already don't they (Debian unstable)? | 17:31 |
| paul_ | unknown | 17:31 |
| paul_ | I think my view would have to be | 17:31 |
| paul_ | if mantis works on latest php without a problem | 17:31 |
| paul_ | and a user is having a problem on some old/custom(e.g. with suhosin) php | 17:32 |
| paul_ | then it's up to the user to fix | 17:32 |
| paul_ | we can obviously help | 17:32 |
| paul_ | if we hit some crash bug in latest php, i'd try cvs head, and tbh try and work out why it's crashing | 17:33 |
| dhx_m | well as developers it makes a lot of sense to be testing with upcoming PHP versions | 17:33 |
| paul_ | as if redhatphp5.1 != unbuntuphp5.1 != gentoophp5.1 | 17:33 |
| paul_ | all we can do is say 'stock php5.1' | 17:33 |
| dhx_m | so you can be sure when the newest PHP is released, Mantis works | 17:33 |
| paul_ | that's without suhosin | 17:33 |
| paul_ | without timezone patches etc | 17:33 |
| dhx_m | I think we really need to fix this email stuff ASAP | 17:34 |
| paul_ | harsh but :) | 17:34 |
| dhx_m | it seems quite a few people are reporting problems with it | 17:34 |
| dhx_m | lol | 17:34 |
| paul_ | I can probably look at email with you tonight if you want | 17:34 |
| paul_ | i.e. in 30-40 mins | 17:35 |
| paul_ | it's probably something i've broken anyway | 17:35 |
| dhx_m | I am fairly certain we're not checking the e-mail on new user preference | 17:35 |
| dhx_m | from what I can see | 17:35 |
| paul_ | I want to rewrite email api anyway | 17:35 |
| paul_ | :P | 17:35 |
| dhx_m | and for some reason a few people are saying that emails won't send at all | 17:35 |
| paul_ | similarly with library versions | 17:36 |
| paul_ | I tend to do a weekly check for libary updates | 17:36 |
| dhx_m | I've noticed that too now... my Apache error_log reports failure for sendmail to connect to mail on port 25 | 17:36 |
| paul_ | your doing it wrong | 17:36 |
| dhx_m | I haven't changed anything on my system relating to sendmail/etc | 17:36 |
| paul_ | :) | 17:36 |
| dhx_m | maybe it is a newer version of PHP causing the trouble... dunno | 17:37 |
| paul_ | unlikely :P | 17:37 |
| paul_ | anyway | 17:37 |
| paul_ | q: | 17:37 |
| paul_ | are there 2 issues then? | 17:37 |
| dhx_m | email was working fine for me during 1.2.0a3 => 1.2.0r1 | 17:37 |
| paul_ | a) mails dont send ever/fullstop | 17:37 |
| dhx_m | from what I can see, yeah | 17:37 |
| paul_ | b) mails always send? | 17:37 |
| dhx_m | and when they do send... e-mail on new is ignored | 17:37 |
| dhx_m | just e-mail on new I think | 17:37 |
| dhx_m | bug 10650 | 17:37 |
| dhx_m | mantisbot died hours ago heh | 17:38 |
| dhx_m | paul_: I have some more fixes in the pipeline for other problems that have been reported... mostly just some bugobjects fixes | 17:40 |
| dhx_m | paul_: just minor stuff that you'd only notice if you had very particular settings | 17:41 |
| dhx_m | paul_: my changes to remove hardcoded enum levels has also exposed a lot of bugs | 17:41 |
| dhx_m | paul_: so it seems | 17:42 |
| dhx_m | paul_: but I do like bugobjects... it's just a big job going through fixing the rest of the code to work with it nicely :) | 17:42 |
| Reapazor | q: right now notifications from mantis go out as "Mantis Bug Tracker" (email), i looked in man.... any way to change that variable wise? | 17:43 |
| dhx_m | paul_: for instance, there are a lot of uses of bug_get_field to replace with bugobject equivalent code :) | 17:43 |
| dhx_m | paul_: but once it is done, the code will be MUCH better... especially when access checks are moved into bug_api's __get and __set methods | 17:44 |
| dhx_m | paul_: then we only have one place to worry about access levels... not 1000 :) | 17:44 |
| dhx_m | Reapazor: yes, check config_defaults_inc.php | 17:45 |
| dhx_m | Reapazor: $g_from_name | 17:45 |
| Reapazor | hmf ;/ | 17:47 |
| Reapazor | thnx | 17:47 |
| Reapazor | wtf... im stupid | 17:48 |
| Reapazor | i have that in my own config already | 17:48 |
| Reapazor | and its set to manti | 17:48 |
| Reapazor | s | 17:48 |
| Reapazor | *Sigh* is it friday yet? | 17:48 |
| dhx_m | lol | 17:49 |
| dhx_m | Chillax: are you a developer? | 17:52 |
| Chillax | dhx_m: aye | 17:52 |
| Chillax | been too busy to do much in AGES though :-/ | 17:52 |
| dhx_m | Chillax: thought so, just noticed when I went to the forums :) | 17:52 |
| dhx_m | ah :) | 17:53 |
| Chillax | yeah i used to keep spammers at bay back in the day too | 17:53 |
| dhx_m | yep | 17:55 |
| dhx_m | I'm just reading through some of the plugin code @ http://deboutv.free.fr/mantis/ | 17:57 |
| dhx_m | there is some seriously nasty stuff there... a reminder_get_bugs function that creates and drops tables | 17:58 |
| dhx_m | and the function is 450 lines of code (no blank lines) | 17:59 |
| dhx_m | anyhow, I'm outta here, will be back later with some fixes | 18:01 |
| * siebrand mulbles something about the fracking repo. | 20:14 | |
| paul_ | ? | 20:25 |
Generated by irclog2html.py