| ../irclogs/#mantishelp.2009-07-04.log | ||
| --- scribe started --- | 00:00 | |
| CIA-17 | Mantisbt: vboctor * r6c8c7bed92a6 /core/bugnote_api.php: Fixes #10655: Private notes cause the view page to stop rendering. | 06:56 |
|---|---|---|
| CIA-17 | Mantisbt: vboctor master-1.2.x * r57dbc614fe73 /core/bugnote_api.php: Fixed #10655: Private notes cause the view page to stop rendering. | 07:00 |
| CIA-17 | Mantisbt: vboctor master-1.2.x * r4e031b699f28 /config_defaults_inc.php: Fixes #5012: Comments relating to . | 07:01 |
| vb123 | nuclear_eclipse: are you there? | 16:23 |
| nuclear_eclipse | howdy | 16:25 |
| nuclear_eclipse | I just pulled the latest master-1.2.x into the live install | 16:26 |
| nuclear_eclipse | and I just killed all the pegged apache processes | 16:26 |
| nuclear_eclipse | so we'll see how it goes | 16:26 |
| vb123 | great, thanks. | 16:29 |
| vb123 | I sent an email with some comments on the source plugin. | 16:29 |
| nuclear_eclipse | ok | 16:30 |
| nuclear_eclipse | vb123: while I've got you to talk about that subject... | 16:31 |
| vb123 | what subject? | 16:32 |
| nuclear_eclipse | I've made quite a lot of upgrades to the source-integration framework beyond what's currently installed on mantisbt.org | 16:32 |
| vb123 | like? | 16:32 |
| nuclear_eclipse | specifically, the differentation between "linking" issues with changesets, and changesets that actually "fix" an issue in the tracker | 16:33 |
| vb123 | you mean support for partial fixes? | 16:33 |
| vb123 | partial vs auto-resolve? | 16:33 |
| nuclear_eclipse | this then allows for things like a) automatically setting the fixed-in version, b) automatically attaching a note to the issue, and c) automatically resolving the issue, all of which are configurable for the site | 16:34 |
| vb123 | the fixed-in-version depends on the branch? | 16:34 |
| nuclear_eclipse | right | 16:34 |
| nuclear_eclipse | I have it all set up on my own tracker at http://leetcode.net/mantis | 16:34 |
| vb123 | why add a note? | 16:35 |
| vb123 | to show up in the email? | 16:35 |
| nuclear_eclipse | right, adding the note triggers an email notification | 16:35 |
| vb123 | do changesets show in email notifications? | 16:35 |
| nuclear_eclipse | only that a changeset was attached | 16:36 |
| vb123 | through the history? | 16:36 |
| nuclear_eclipse | right | 16:36 |
| nuclear_eclipse | anything beyond that would be better left for when I get around to reworking the way notifications work altogether | 16:36 |
| vb123 | yep, go ahead install your update and email us with how to work with the new system. | 16:38 |
| vb123 | I mean mantisbt-dev | 16:38 |
| nuclear_eclipse | I'm just thinking that even if we only turned on the option to automatically set the fixed-in verison, it would be a big help | 16:38 |
| vb123 | fixed-in-version and resolve | 16:38 |
| vb123 | does it set the "assigned to" as well? | 16:39 |
| nuclear_eclipse | yep | 16:39 |
| vb123 | i.e. if the issue was not assigned or assigned to another person? | 16:39 |
| nuclear_eclipse | well, only if it's not already set | 16:39 |
| vb123 | ok | 16:39 |
| nuclear_eclipse | and it only sets the fixed-in version if it's not already set, etc | 16:39 |
| vb123 | how do you indicate that a fix is partial and it shouldn't resolve? | 16:39 |
| vb123 | different keywords? | 16:39 |
| nuclear_eclipse | it's a difference of "issue #XX" versus "fixes #XX" | 16:40 |
| vb123 | so you have another regular expression, right? | 16:40 |
| nuclear_eclipse | eg, two sets of regexes | 16:40 |
| vb123 | why don't you always overwrite the fixed in version? | 16:40 |
| nuclear_eclipse | because of the situation of committing to two different branches | 16:41 |
| nuclear_eclipse | eg, commit to master-1.2.x, and then cherry-picking to master, or vice versa | 16:41 |
| nuclear_eclipse | you'd get a situation where it would be setting the fixed-in version twice | 16:41 |
| vb123 | It seems to me that certain branches should have a higher priority than others. | 16:42 |
| vb123 | For fixed_in_version of 1.2.x would always take precedence over 1.3.x independent of the order of checkins. | 16:42 |
| nuclear_eclipse | well now you're just making it difficult :P | 16:42 |
| vb123 | if you want to automate, then do it right ;) | 16:43 |
| * nuclear_eclipse cries | 16:43 | |
| vb123 | otherwise we have to fiddle with the resolved issues causing unnecessary email notifications. | 16:43 |
| vb123 | The other option is to revert back to using the Port #123 option. | 16:43 |
| vb123 | Or maybe you create a port issue. | 16:44 |
| vb123 | If the issue is already resolved with a fixed_in_version of another branch, you create a port issue, link it as a child, and resolve it. | 16:44 |
| nuclear_eclipse | the real reason I don't do that is because it processes things individually -- eg, it doesn't have the ability (yet) to realize "issue X was fixed in branch Y and branch Z" | 16:44 |
| vb123 | (optional behavior) | 16:44 |
| vb123 | I understand, but the suggestions above don't assume this knowledge. | 16:45 |
| nuclear_eclipse | it says "issue X was fixed in branch Y", does its thing, and then later sees "issue X was fixed in branch Z" | 16:45 |
| vb123 | yes, but when you process the second one, you will notice the information about branch Y from the fixed_in_version. | 16:46 |
| nuclear_eclipse | right, and at that point it will just skip that issue | 16:46 |
| vb123 | that's the current behavior. but we need to think about how the porting scenario works for us. | 16:46 |
| nuclear_eclipse | although now that I think about it, we do have a branch "priority" as it is: the branch listing for the repository | 16:46 |
| vb123 | :) | 16:47 |
| nuclear_eclipse | the order they are listed will determine the order the changesets get imported | 16:47 |
| vb123 | just make it clear in the interface (e.g. a comment or something) that explains how the order affects the priority. | 16:48 |
| nuclear_eclipse | so if we change it to be "master-1.1.x, master-1.2.x, master", then 1.1 and 1.2 would get "priority" over master branch | 16:48 |
| nuclear_eclipse | anywho, I gotta run | 16:48 |
| vb123 | ok, thanks. | 16:48 |
| nuclear_eclipse | cheers, and happy 4th | 16:48 |
| vb123 | same to you. | 16:48 |
| CIA-17 | Mantisbt: vboctor * r03f6cb7d1029 /file_download.php: Fixes #10135: Downloading large attachments results in Internal Server Error - 500. | 17:39 |
| CIA-17 | Mantisbt: vboctor master-1.2.x * rbc945ed9eb4c /file_download.php: Fixes #10135: Downloading large attachments results in Internal Server Error - 500. | 17:40 |
| * paul_ sighs | 23:32 | |
Generated by irclog2html.py