| ../irclogs/#mantishelp.2009-06-23.log | ||
| --- scribe started --- | 00:00 | |
| AvengerX | Captcha is showing as a [x] instead of pic -- there is no 'no gd-lib support missing' warning on page | 00:54 |
|---|---|---|
| AvengerX | :/ | 00:54 |
| [KK]Kirill | AvengerX: yuo must enabled gd-lib support in php | 03:32 |
| mantisbot | New bug: Bug 10616 - sdurkin - open - new | 03:49 |
| mantisbot | New bug: Crash on attempt to attach file. - http://www.mantisbt.org/bugs/view.php?id=10616 | 03:49 |
| dhx_m | [KK]Kirill: I'll fix bug 10611 in a moment, thanks :) | 07:51 |
| mantisbot | Bug 10611 - Kirill - open - assigned | 07:51 |
| mantisbot | Attach not recognize correctly - http://www.mantisbt.org/bugs/view.php?id=10611 | 07:51 |
| [KK]Kirill | dhx_m: lo | 07:51 |
| [KK]Kirill | dhx_m: In git? | 07:52 |
| dhx_m | [KK]Kirill: hi | 07:52 |
| dhx_m | yep | 07:52 |
| [KK]Kirill | 5 minutes, I test | 07:52 |
| [KK]Kirill | dhx_m: sorry, I don't see changes | 08:02 |
| [KK]Kirill | where you push changes? | 08:02 |
| dhx_m | [KK]Kirill: sorry... I haven't done it yet :o | 08:02 |
| dhx_m | [KK]Kirill: when you said "in git" I thought you were talking about where I was going to make the changes | 08:03 |
| [KK]Kirill | I think you push changes in master or your own git repo | 08:04 |
| dhx_m | I haven't done either yet... will do it in a moment | 08:05 |
| giallu | hi guys | 08:11 |
| [KK]Kirill | giallu: lo | 08:14 |
| dhx_m | [KK]Kirill: I have a nicer fix to the problem coming up :) | 08:16 |
| [KK]Kirill | How? | 08:16 |
| dhx_m | I'll commit in a moment | 08:18 |
| [KK]Kirill | dhx_m: :( | 08:55 |
| dhx_m | [KK]Kirill: I realised my implementation of file_get_extension in 1 line wasn't quite up to par | 08:55 |
| dhx_m | [KK]Kirill: so I'm redoing it with UTF8 support as well | 08:55 |
| [KK]Kirill | :-\ | 08:56 |
| dhx_m | [KK]Kirill: surprise! ... in a moment | 09:41 |
| CIA-18 | Mantisbt: hickseydr * r735dbd5cbe8d /core/file_api.php: Fix #10611: file extension check fails with UTF-8 | 09:41 |
| [KK]Kirill | yeah | 09:43 |
| dhx_m | let me know how that works :) | 09:43 |
| dhx_m | I've tested the functions myself with and without UTF-8 and they seem OK | 09:43 |
| [KK]Kirill | :( not sync.. ok pull from mantisbt.org | 09:45 |
| dhx_m | have you tried it yet? | 10:14 |
| Bonaparte | Hi all | 10:33 |
| Bonaparte | Mantis doesn't send any e-mail notification at all. | 10:34 |
| Bonaparte | Can you suggest to where to look at to identify the problem? | 10:34 |
| Bonaparte | Can you suggest to where to look at to identify the cause problem?* | 10:34 |
| dhx_m | Bonaparte: which version of Mantis are you using? | 10:36 |
| Bonaparte | dhx_m, 1.1.7 | 10:37 |
| dhx_m | Bonaparte: try running admin/test_email.php | 10:37 |
| Bonaparte | dhx_m, there is no such script in admin | 10:38 |
| dhx_m | hmm must be a 1.2.x feature | 10:38 |
| dhx_m | are you getting any errors in your PHP error log, mail server log, etc? | 10:38 |
| Bonaparte | There is check.php though. I am trying it now | 10:39 |
| Bonaparte | dhx_m, nothing in the logs | 10:40 |
| dhx_m | Bonaparte: have you just installed 1.1.7? | 10:41 |
| Bonaparte | dhx_m, I am using it from about three months. Ever since I installed it, the email notification is not working at all | 10:41 |
| Bonaparte | Okay, I received the mail it sent from admin/check.php | 10:42 |
| Bonaparte | But I don't get any emails when events occur in the application such as create an issue or close an issue | 10:43 |
| Bonaparte | When I visit manage_config_email_page.php I see two messages | 10:43 |
| Bonaparte | 26 total queries executed. | 10:43 |
| Bonaparte | 19 unique queries executed. | 10:43 |
| Bonaparte | I don't understand what they mean | 10:44 |
| dhx_m | Bonaparte: open up config_defaults_inc.php and scroll down to # Mantis Email Settings | 10:44 |
| dhx_m | Bonaparte: then read those options, and make sure the relevant ones are placed in your config_inc.php file and are configured correctly | 10:44 |
| dhx_m | Bonaparte: you'll probably need to specify the from_email, etc correctly so your mail server doesn't bounce it | 10:44 |
| Bonaparte | dhx_m, I have properly set these http://fpaste.org/paste/16158 in my config | 10:46 |
| [KK]Kirill | dhx_m: sorry. Test. All work | 10:47 |
| dhx_m | Bonaparte: those aren't correct I'm afraid | 10:47 |
| Bonaparte | dhx_m? | 10:47 |
| dhx_m | Bonaparte: $g_phpMailer_method = 2 will send emails via an SMTP server, rather than the default (used in check.php) or using the php mail() function | 10:48 |
| Bonaparte | I removed the actual values in the pastebin | 10:48 |
| dhx_m | oh ok | 10:48 |
| Bonaparte | Yes, I want it to use SMTP | 10:48 |
| dhx_m | Bonaparte: try using php mail() instead if that works? | 10:48 |
| [KK]Kirill | dhx_m: thanks | 10:48 |
| dhx_m | [KK]Kirill: no problem, any more things I need to fix? :) | 10:48 |
| Bonaparte | dhx_m, isn't SMTP a better a choice? | 10:49 |
| dhx_m | Bonaparte: I haven't tried it before... but it isn't a better choice... it is another choice :) | 10:49 |
| [KK]Kirill | dhx_m: I think about that | 10:50 |
| dhx_m | Bonaparte: php mail() is easier because it uses the same settings you use for all PHP scripts (most likely sending via the SMTP client already on your server) | 10:50 |
| dhx_m | Bonaparte: whereas when you specify a custom SMTP server, you have to ensure you get the hostname, username, password etc correct | 10:51 |
| Bonaparte | dhx_m, I want to avoid using local sendmail. I am sure the hostname, username and password are correct | 10:51 |
| dhx_m | Bonaparte: does your SMTP host have any logs recording who connected? | 10:52 |
| Bonaparte | dhx_m, I will check now | 10:52 |
| dhx_m | Bonaparte: it could be your SMTP host settings which are causing the problem too | 10:52 |
| Bonaparte | dhx_m, I think the problem is I didn't specify $g_default_notify_flags | 10:53 |
| dhx_m | Bonaparte: the default settings should be OK for you... I'd recommend you check your user settings under "My Account" | 10:53 |
| dhx_m | Bonaparte: also set $g_email_receive_own = ON if you want to test more easily | 10:54 |
| Bonaparte | dhx_m, I just tested with $g_phpMailer_method = 2; I updated few issues statuses for testing. Nothing in the mail log | 11:04 |
| Bonaparte | The last item in the mail log was when I tested with admin/check.php | 11:05 |
| dhx_m | Bonaparte: are you able to upgrade to the latest git version (basically 1.2.0rc1 less a few fixes) | 11:05 |
| dhx_m | Bonaparte: there will be a new 1.2.0 release soon and that is where most of the development effort is placed at the moment | 11:06 |
| dhx_m | Bonaparte: the new version has a new copy of phpMailer, etc so may work a lot better :) | 11:06 |
| Bonaparte | I see. Is there any ETA of 1.2.0 release? | 11:06 |
| dhx_m | Bonaparte: no need to upgrade... you could also just try a side-by-side test copy of the newest Mantis | 11:07 |
| dhx_m | Bonaparte: there are a few minor things we're fixing at the moment, but what you get from git is essentially feature complete | 11:07 |
| dhx_m | Bonaparte: and it has a guaranteed upgrade path to whatever newer versions are released | 11:07 |
| Bonaparte | dhx_m, cool | 11:08 |
| dhx_m | Bonaparte: of course if you are upgrading, there is a bit of effort involved on your end with changing configuration (depending on how customised your installation is) | 11:08 |
| dhx_m | Bonaparte: and you'd need to create a database backup of course... as you would with any sort of upgrade to software that uses a database :) | 11:09 |
| Bonaparte | dhx_m, it's a very plain installation. My config has only the db and email settings in it | 11:09 |
| Bonaparte | dhx_m, is there a page where I can read about the new features being implemented in 1.2.0? | 11:10 |
| dhx_m | Bonaparte: sure... here: http://www.mantisbt.org/bugs/changelog_page.php | 11:11 |
| dhx_m | Bonaparte: check under each version 1.2.0a1 through 1.2.0a3 and then also 1.2.x | 11:11 |
| dhx_m | Bonaparte: a note however... you need PHp 5.1 for version 1.2.x | 11:12 |
| Bonaparte | dhx_m, that is no problem. I have php 5.2.9 | 11:13 |
| dhx_m | Bonaparte: good :) also a more condensed changelog is at http://git.mantisbt.org/?p=mantisbt.git;a=blob;f=doc/RELEASE;h=6380d60e6404868041e2dda425ee8f72427418cb;hb=30debf44a82eb60fc6d2c42f497641ce6dd9c2bd | 11:13 |
| dhx_m | Bonaparte: and it is very much condensed... there is a LOT that has been improved in 1.2.x :) | 11:13 |
| Bonaparte | Thanks. The previous one was a bit overwhelming | 11:13 |
| dhx_m | Bonaparte: to grab the latest version at any time, click the first 'snapshot' link @ http://git.mantisbt.org/?p=mantisbt.git;a=summary | 11:14 |
| dhx_m | Bonaparte: but please be warned this is under development continuously and things may be broken from time to time | 11:15 |
| dhx_m | Bonaparte: at the moment I can tell you that it is quite stable (I guess it is in an unofficial feature freeze) | 11:15 |
| Bonaparte | dhx_m, thanks for the help. But I think it is too much work for an end user to get the email notification to work. No offense meant :) | 11:15 |
| dhx_m | Bonaparte: you are doing something that most people don't... most just use the inbuilt PHP mail() function | 11:16 |
| mantisbot | New bug: Bug 10617 - lone - open - new | 11:17 |
| mantisbot | New bug: LDAP login not work on AD - http://www.mantisbt.org/bugs/view.php?id=10617 | 11:17 |
| * giallu is not using mail() | 11:17 | |
| Bonaparte | dhx_m, heh. I seriously recommend to NOT to use the php mail() function unless you have a properly configured mail server on the same machine | 11:18 |
| dhx_m | Bonaparte: well SMTP should also work... all I'm saying is that it takes a little bit more effort to setup | 11:19 |
| Bonaparte | I appreciate your kindness. I gotta run now. I will be back tomorrow :) | 11:20 |
| Bonaparte | Thanks again, dhx_m | 11:20 |
| dhx_m | Bonaparte: ok good luck :) | 11:20 |
| Bonaparte | dhx_m, just curious, are you a mantis committer? | 11:22 |
| dhx_m | Bonaparte: yep | 11:22 |
| Bonaparte | Great | 11:22 |
| dhx_m | Bonaparte: I mainly work on 1.2.0 so I don't have any interest in fixing bugs with 1.x.x at the moment unless they're security problems | 11:23 |
| Bonaparte | I see | 11:23 |
| dhx_m | Bonaparte: other developers may be more interested in 1.x.x though if they use that | 11:23 |
| Bonaparte | dhx_m, no luck with mail() | 11:24 |
| dhx_m | Bonaparte: interesting... that is what check.php uses | 11:24 |
| Bonaparte | I think I should look at it when I have more time | 11:24 |
| Bonaparte | Thanks for all the help | 11:25 |
| mantisbot | New bug: Bug 10618 - dhx - open - assigned | 11:57 |
| mantisbot | New bug: Add option to disable projection field - http://www.mantisbt.org/bugs/view.php?id=10618 | 11:57 |
| CIA-18 | Mantisbt: hickseydr * r73ab2ee2c135 / (3 files): Add option to hide projection field | 12:23 |
| nuclear_eclipse | dhx_m: | 13:13 |
| dhx_m | nuclear_eclipse: hey | 13:13 |
| nuclear_eclipse | why aren't we just using basename(), dirname(), etc? | 13:14 |
| nuclear_eclipse | or even better, pathinfo() ? | 13:14 |
| dhx_m | nuclear_eclipse: I was going to use pathinfo() however it is dumb and will return extensions with directory slashes | 13:14 |
| nuclear_eclipse | ? | 13:14 |
| dhx_m | nuclear_eclipse: pathinfo('somefile./ext', EXTENSION_BLAH) will return the string '/ext' | 13:15 |
| dhx_m | nuclear_eclipse: and additionally, it isn't UTF8 aware | 13:15 |
| dhx_m | afaik | 13:15 |
| nuclear_eclipse | ok | 13:16 |
| dhx_m | nuclear_eclipse: what I'm stuck on at the moment is what collation the database should be | 13:16 |
| dhx_m | nuclear_eclipse: at the moment we use utf8_general_ci which does case insensitive comparisons (a = A) | 13:16 |
| nuclear_eclipse | right | 13:16 |
| nuclear_eclipse | that's hte correct collation | 13:17 |
| dhx_m | nuclear_eclipse: there is utf8_unicode_ci which does more correct sorting in other languages | 13:17 |
| dhx_m | nuclear_eclipse: because utf8_general_ci simply removes accents, converts to uppercase, then compares | 13:17 |
| nuclear_eclipse | meh | 13:17 |
| * nuclear_eclipse still hates utf8 | 13:17 | |
| dhx_m | nuclear_eclipse: utf8_unicode_ci doesn't remove accents, it uses Unicode tables to compare... although a = A still | 13:17 |
| dhx_m | nuclear_eclipse: I was worried that this could cause some nasty security problems | 13:18 |
| nuclear_eclipse | I have a feeling that's probably a slower collation too | 13:18 |
| dhx_m | nuclear_eclipse: yeah it's meant to be a little slower (but more accurate) | 13:18 |
| nuclear_eclipse | I'm not sure what any security problem would be.... | 13:18 |
| nuclear_eclipse | we already enforce uniqueness of username based on database comparison, so regardless of the collation type, you couldn't get conflicts of username... | 13:19 |
| dhx_m | nuclear_eclipse: well yeah, I guess if we limit the character set to a-z it'd be ok | 13:20 |
| nuclear_eclipse | well, even if we didn't | 13:20 |
| nuclear_eclipse | assuming we let usernames be anything | 13:20 |
| dhx_m | nuclear_eclipse: my point is that with utf8_general_ci, böb = BOB | 13:21 |
| nuclear_eclipse | if user A wants username roger, and user B wants "roge`r", then user B will get denied because it's not unique | 13:21 |
| dhx_m | nuclear_eclipse: so accents are ignored completely, even though they're important | 13:21 |
| dhx_m | nuclear_eclipse: yep but only because we're filtering out certain characters | 13:21 |
| nuclear_eclipse | no | 13:21 |
| nuclear_eclipse | ignore our own filtering | 13:21 |
| nuclear_eclipse | we check uniqueness by doing "SELECT username WHERE username=?" -- if there's a "böb" already registered, and a new user requests "bob", the uniqueness query will return "böb", and mantis will deny "bob" from creating that username | 13:23 |
| dhx_m | yep | 13:23 |
| nuclear_eclipse | regardless of collation, the fact that we rely on the database consistently for comparisons means that there isn't a chance for exploit based on that issue | 13:24 |
| dhx_m | so what you're saying is that utf8_unicode_ci may be unsafe because böb wouldn't be returned? | 13:24 |
| nuclear_eclipse | no, utf8_unicode_ci would likewise be safe too | 13:24 |
| dhx_m | hmm ok | 13:24 |
| nuclear_eclipse | it's the consistency of comparison that matters here | 13:24 |
| dhx_m | I guess in this case we're counting rows | 13:24 |
| nuclear_eclipse | not how "accurate" it is or isn't | 13:24 |
| dhx_m | but if the comparison is done in PHP, böb != bob (whereas this is true in the database) | 13:25 |
| nuclear_eclipse | well, right | 13:25 |
| dhx_m | utf8_strstr() for instance | 13:25 |
| nuclear_eclipse | that's my point, we're not doing comparisons for that stuff in PHP, it's all happening in the db | 13:25 |
| dhx_m | ok | 13:25 |
| dhx_m | I'm thinking that we could do with a new install option to let the user choose their collation type? | 13:26 |
| dhx_m | or maybe a separate script in admin/ to change it for mysql? | 13:26 |
| nuclear_eclipse | perhaps, but I think that's generally going to be a moot point | 13:26 |
| dhx_m | I guess the main thing it'd affect is sort orders | 13:28 |
| dhx_m | but then again, I doubt you'd be mixing character sets on a Mantis installation anyway | 13:29 |
| nuclear_eclipse | which at that point, is it really an issues? | 13:29 |
| nuclear_eclipse | ie, in French, they still considered a e` to be the same character as e, so they would sort the same... ? | 13:29 |
| dhx_m | with utf8_general_ci yes, with utf8_unicode_ci no | 13:30 |
| dhx_m | I suppose it isn't a big deal ;) | 13:30 |
| nuclear_eclipse | well, my point being that all the variants of e come after d and before f, does it *really* matter that e comes before e` comes before e~ :P | 13:31 |
| nuclear_eclipse | and how does sort ordering work in pictogram languages? :P | 13:31 |
| dhx_m | not too sure... but from what I read utf8_general_ci doesn't play nicely with languages that use special Unicode control chars, etc | 13:33 |
| dhx_m | as it only compares one character at a time | 13:33 |
| dhx_m | I think the example they use is a weird looking B = s vs B = ss | 13:34 |
| dhx_m | depending on if you use general or unicode collations | 13:34 |
| nuclear_eclipse | ah, damn germans... | 13:34 |
| * nuclear_eclipse hides his all-german heritage. | 13:34 | |
| nuclear_eclipse | :P | 13:34 |
| dhx_m | lol | 13:34 |
| nuclear_eclipse | ironic, my families all came from germany, and I learn french in high school :) | 13:35 |
| dhx_m | haha | 13:35 |
| nuclear_eclipse | although tbh, if they had offered german as an option, I would have jumped on it in a heartbeat... | 13:35 |
| dhx_m | is: | 13:35 |
| dhx_m | $sqlarray = $dict->CreateDatabase( $f_database_name, Array( 'mysql' => 'DEFAULT CHARACTER SET utf8 DEFAULT COLLATE utf8_general_ci' ) ); | 13:35 |
| dhx_m | ok? | 13:35 |
| nuclear_eclipse | I think it is | 13:36 |
| dhx_m | currently we have: | 13:36 |
| dhx_m | $sqlarray = $dict->CreateDatabase( $f_database_name, Array( 'mysql' => 'DEFAULT CHARSET=utf8' ) ); | 13:36 |
| nuclear_eclipse | talk to paul_ | 13:36 |
| nuclear_eclipse | most of the way that adodb does things is beyond my ability to pay attention... | 13:36 |
| dhx_m | according to bug 9216, some installations have a different default collation than utf8_general_ci | 13:37 |
| mantisbot | Bug 9216 - kinguru - fixed - resolved | 13:37 |
| mantisbot | Problems with Russian language - http://www.mantisbt.org/bugs/view.php?id=9216 | 13:37 |
| dhx_m | yep | 13:37 |
| nuclear_eclipse | well, it all depends on how the database is created | 13:38 |
| nuclear_eclipse | I'd reckon that a good majority of users, including myself, create the database manually beforehand | 13:38 |
| dhx_m | true | 13:39 |
| nuclear_eclipse | eg, I always log into phpmyadmin, and set up a user for each app, generate a random password for the user, and automatically create a database for the user at the same time | 13:39 |
| nuclear_eclipse | so at that point, it's up to me to either choose the correct collation, or take responsibility for being an ignorant idiot :P | 13:40 |
| kenguest | nuclear_eclipse: how often do you take responsibility for the latter? ;-) | 13:40 |
| dhx_m | :) | 13:40 |
| nuclear_eclipse | never! | 13:40 |
| nuclear_eclipse | I know everything! | 13:41 |
| nuclear_eclipse | I am never wrong! | 13:41 |
| kenguest | not from Barcelona so | 13:41 |
| CIA-18 | Mantisbt: hickseydr * r65f51280e646 /admin/install.php: Fix #9216: Specify MySQL collation utf8_general_ci | 13:51 |
| paul_ | hmm | 14:01 |
| paul_ | dhx_m | 14:02 |
| nuclear_eclipse | dhx_m: will that break anything not mysql? | 14:02 |
| nuclear_eclipse | oh, nevermind | 14:02 |
| dhx_m | applies to MySQL only | 14:02 |
| paul_ | dhx_m: hmm | 14:02 |
| nuclear_eclipse | missed the `'mysql' => ..` part | 14:02 |
| dhx_m | paul_: not setting the collation will default to some sort of MySQL default that may vary system-to-system | 14:03 |
| dhx_m | paul_: I was thinking a better fix is to ask the user at install time what collation they want to use (but we'd need to list it from the output of "show collatation") | 14:03 |
| dhx_m | paul_: or add documentation to the install guide to let people specify the correct Unicode collation for their language | 14:03 |
| dhx_m | paul_: I guess this is limiting us to only really supporting one language per Mantis installation | 14:04 |
| paul_ | +---------+---------------+-------------------+--------+ | 14:04 |
| paul_ | | Charset | Description | Default collation | Maxlen | | 14:04 |
| paul_ | +---------+---------------+-------------------+--------+ | 14:04 |
| paul_ | | utf8 | UTF-8 Unicode | utf8_general_ci | 3 | | 14:04 |
| paul_ | +---------+---------------+-------------------+--------+ | 14:04 |
| paul_ | I thought | 14:04 |
| paul_ | charset utf8 set a default collation | 14:04 |
| paul_ | as part of the charset | 14:04 |
| dhx_m | same | 14:05 |
| dhx_m | doesn't hurt to specify it anyway I guess | 14:05 |
| nuclear_eclipse | paul_: did you ever look at the release notes like you wanted to? | 14:12 |
| dhx_m | paul_: http://dev.mysql.com/doc/refman/6.0/en/charset-server.html | 14:12 |
| dhx_m | is there much left to do before 1.2rc1? | 14:21 |
| dhx_m | is it ok to make a patch that allows the user to turn off the footer? | 14:23 |
| dhx_m | I ask... because there is a copyright statement and branding there | 14:27 |
| nuclear_eclipse | hmm? | 14:28 |
| dhx_m | well I was thinking of allowing the user to turn off the webmaster email, Mantis logo in the bottom-right, etc | 14:29 |
| nuclear_eclipse | I'd rather we not... | 14:29 |
| dhx_m | so the page ends at the horizontal line | 14:29 |
| nuclear_eclipse | that's the only mantis branding left... | 14:29 |
| dhx_m | even if it's off by default and not documented? :p | 14:29 |
| dhx_m | yep | 14:29 |
| nuclear_eclipse | I think we want to leave that... | 14:30 |
| dhx_m | I agree it'd be nice to have something left that search engines can notice | 14:30 |
| dhx_m | I suppose users can easily hack it out themselves if they want to | 14:31 |
| nuclear_eclipse | yep, I'd rather it be a forceful decision to remove the only branding left, rather than let an admin not even think about masking out anything that says where the application came from... | 14:32 |
| dhx_m | yep | 14:33 |
| nuclear_eclipse | afaik, the only thing holding up 1.2.0rc1 is paul; he said he wanted to look at release notes before it went out, and he hasn't said anything about them... | 14:35 |
| dhx_m | also for 1.3 I was thinking about the possibility of removing built-in support for fields like ETA and projection, and instead having them as custom fields? | 14:38 |
| dhx_m | I remember reading somewhere about wanting to remove other things like "Additional information" in default installs | 14:39 |
| nuclear_eclipse | hmm | 14:39 |
| nuclear_eclipse | that could be quite tricky/disastrous | 14:39 |
| dhx_m | IMO it'd be a lot cleaner to place the focus on having the user specify the fields they want to use | 14:39 |
| dhx_m | rather than force feed them some defaults they probably won't use | 14:39 |
| nuclear_eclipse | I think we would really need a way to assign custom fields globally before we even thought about doing something like that... | 14:40 |
| dhx_m | true | 14:40 |
| dhx_m | I was thinking long term | 14:40 |
| * nuclear_eclipse wants next major version to be 1.4, and 1.3.x be unstable releases, a la Gnome | 14:41 | |
| dhx_m | maybe it'd be better to work out some formal ontology | 14:41 |
| nuclear_eclipse | it makes the numbering *so* much easier | 14:41 |
| dhx_m | I don't mind the Linux kernel approach | 14:42 |
| nuclear_eclipse | ? | 14:42 |
| dhx_m | I recon we don't need interim releases with version numbers before stable versions are released | 14:42 |
| dhx_m | just tell people to download git snapshot 129379 | 14:43 |
| dhx_m | aka "the latest" | 14:43 |
| nuclear_eclipse | we don't have an active enough testing community to be able to do that | 14:43 |
| dhx_m | but if someone was to report a bug against 1.2.0a3 right now | 14:44 |
| dhx_m | we fix it | 14:44 |
| dhx_m | we've got to tell them to update to the latest git master to verify whether the fix worked | 14:45 |
| nuclear_eclipse | or we could just make our development releases happen more often... | 14:45 |
| dhx_m | that would help solve the problem a little | 14:45 |
| dhx_m | but I still think most users trying development versions would want to try the fix as soon as it is produced | 14:46 |
| nuclear_eclipse | we have the nightly builds, which could technically help serve that purpose | 14:46 |
| dhx_m | rather than wait a while | 14:46 |
| dhx_m | yep | 14:46 |
| dhx_m | why do we need builds though? | 14:46 |
| nuclear_eclipse | rather than having people manually pull snapshots, just have them test a nightly... | 14:46 |
| nuclear_eclipse | because a lot of users don't ever want to use source control | 14:47 |
| nuclear_eclipse | you tell them to use git and they freak out on you | 14:47 |
| dhx_m | no need for them to use git | 14:47 |
| dhx_m | just point to something like http://git.mantisbt.org/?p=mantisbt.git;a=snapshot;h=65f51280e646b3821ab6444689d8b0472ab23145;sf=tgz | 14:47 |
| dhx_m | where h= current head commit | 14:47 |
| dhx_m | to download a snapshot | 14:47 |
| nuclear_eclipse | or just point to www.mantisbt.org/builds so that it's not taxing the server to generate tarballs on the fly.... | 14:48 |
| dhx_m | I'm sure it'd be possible to create a git post-commit hook that builds a tarball with git archive master | gzip -9 > latest.tar.gz | 14:49 |
| dhx_m | ? | 14:49 |
| nuclear_eclipse | I think the nightly builds page could definitely use some better automation to have, eg, a symlink pointing at the latest build, etc | 14:49 |
| dhx_m | I just don't see any point in having only a nightly build | 14:49 |
| dhx_m | except for documentation or other things that actually need building | 14:49 |
| nuclear_eclipse | the only difference is that it gets kicked off at midnight rather than on post-commit... ? | 14:50 |
| nuclear_eclipse | and it stores five days of history, so that users can pull older builds if something's currently broken... | 14:50 |
| dhx_m | well you could easily add protection like "don't create more than one snapshot every 10 minutes" | 14:50 |
| dhx_m | hmm maybe that wouldn't work so well | 14:51 |
| nuclear_eclipse | that still seems like overkill... | 14:51 |
| dhx_m | well what I'm concerned about is if someone comes in here and we help them out with a problem, and apply a patch | 14:51 |
| dhx_m | and then they want to test it | 14:51 |
| nuclear_eclipse | but thanks, you've reminded me that I wanted to reduce the set of nightly builds | 14:51 |
| dhx_m | we'd probably want to tell them to try http://git.mantisbt.org/?p=mantisbt.git;a=snapshot;h=master;sf=tgz | 14:51 |
| dhx_m | do we currently build documentation? | 14:52 |
| nuclear_eclipse | we do for nightlies | 14:52 |
| nuclear_eclipse | snapshots from gitweb won't, ofc | 14:53 |
| dhx_m | yep | 14:53 |
| dhx_m | sounds good so far | 14:53 |
| dhx_m | but are you saying we still need alpha releases? | 14:53 |
| nuclear_eclipse | yes, but I'm thinking something like: | 14:55 |
| nuclear_eclipse | 1.3.x is an unstable development release -- 1.4.x is a stable release of the 1.3.x code base | 14:56 |
| nuclear_eclipse | eg, gnome does 2.27.1, 2.27.2, 2.27.3, then RC is 2.27.90, 2.27.91, then final release is 2.28.0, and maintenance releases are 2.28.1, etc | 14:57 |
| nuclear_eclipse | but that's just my opinion | 14:58 |
| dhx_m | that sounds OK | 14:58 |
| nuclear_eclipse | I just hate the fact that 1.2.0aX and 1.2.0rcX aren't very obvious that they come before a 1.2.0 | 14:59 |
| dhx_m | paul_ and myself the other day were talking about quarterly releases (I think)... what are your thoughts on when major releases should happen? | 14:59 |
| nuclear_eclipse | I generally like predictable releases, but I don't think we have the manpower for that with Mantis | 15:00 |
| angelete2 | hi | 15:55 |
| angelete2 | is there any mantis connector for thunderbird? | 15:55 |
| angelete2 | i want to link mantis tasks with thunderbird's | 15:56 |
| kenguest | angelete2: I think there will be - once you write one... | 15:59 |
| kenguest | correct me if I'm wrong ;-) | 15:59 |
| angelete2 | mmmmm, i'm thinking on it | 16:00 |
| angelete2 | now i have to learn to programm for thunderbird | 16:00 |
| angelete2 | then mantis.... | 16:00 |
| angelete2 | just, keep comfortable till i finish XD | 16:00 |
| paul_ | dhx_m: not quartely | 16:40 |
| paul_ | dhx_m: alpha one = october 09, release xmas 2011/12 | 16:40 |
| dhx_m | paul_: weekly? :p | 16:40 |
| dhx_m | yep | 16:40 |
| dhx_m | 2011-12 :o | 16:41 |
| dhx_m | that is a long time | 16:41 |
| shardy | is there a simple way to add new workflow states? | 16:41 |
| paul_ | statistically! | 16:41 |
| dhx_m | paul_: lol | 16:41 |
| shardy | i.e. has someone done it before and have instructions on how to do it? :) | 16:41 |
| dhx_m | paul_: what are you holding up 1.2.x with? :p | 16:42 |
| paul_ | dunno | 16:42 |
| dhx_m | shardy: it's all included in the documentation | 16:42 |
| paul_ | I said release notes miss stuff like graphs | 16:42 |
| paul_ | although | 16:42 |
| paul_ | that might be a good thing | 16:42 |
| shardy | hm, ok. i looked through but didn't see anything; will check again. | 16:42 |
| dhx_m | paul_: I recon we need to create a gnome-style release document | 16:43 |
| dhx_m | paul_: where you wow users with lots of pictures :p | 16:43 |
| paul_ | anyway in terms of builds for stuff | 16:43 |
| paul_ | we've got cc stuff running after every commit | 16:43 |
| dhx_m | shardy: it's under "customisation" | 16:43 |
| paul_ | so if we just keep files | 16:43 |
| paul_ | I need to decide whether to update my server | 16:43 |
| paul_ | for new hardware :9 | 16:43 |
| nuclear_eclipse | paul_: so are you wanting to add anything to release notes or not? | 16:44 |
| dhx_m | paul_: are you any good with SQL? I want a query that orders bugs firstly by whether they're resolved or not... then by their priority | 16:44 |
| dhx_m | paul_: not sure if that is possible :o | 16:44 |
| paul_ | nuclear_eclipse: well, I think the release doc file reflects the quality/length that we normally put into our release ntoes on the blog | 16:44 |
| nuclear_eclipse | order by XXX ASC, YYY DESC | 16:44 |
| paul_ | I dont think even | 16:44 |
| dhx_m | lol | 16:44 |
| paul_ | and | 16:45 |
| paul_ | it would be nice as a pdf | 16:45 |
| paul_ | with pictures | 16:45 |
| paul_ | as dhx says | 16:45 |
| dhx_m | nuclear_eclipse: nah, I only want to order by whether an issue is resolved or not... | 16:45 |
| dhx_m | nuclear_eclipse: rather than by the actual numerical status value | 16:45 |
| * nuclear_eclipse notes that he never saw any official release notes for 1.1, so knows not what paul is talking about... | 16:45 | |
| dhx_m | nah, not PDf... on the main website! :p | 16:45 |
| dhx_m | the users will think we're academics if we use PDF :p | 16:46 |
| nuclear_eclipse | the main site is not very easy to work with... | 16:46 |
| dhx_m | http://library.gnome.org/misc/release-notes/2.26/ | 16:46 |
| nuclear_eclipse | maybe if our main site was something like a CMS or wiki where it was easy to add new pages... | 16:46 |
| dhx_m | but I was thinking more of a before/after layout | 16:46 |
| dhx_m | hmm yeah | 16:47 |
| nuclear_eclipse | but tbh, our current main site is not very dev-friendly, or even user-friendly... | 16:48 |
| nuclear_eclipse | and I rather disagree with the layout of menu options on the main site too | 16:48 |
| paul_ | nuclear_eclipse: http://www.mantisbt.org/blog/?p=19 | 16:49 |
| paul_ | anyway | 16:49 |
| paul_ | I'm gonna try making a pdf I think | 16:49 |
| paul_ | pdf's are nice | 16:49 |
| nuclear_eclipse | arg | 16:49 |
| paul_ | did we agree on a new mantis logo | 16:49 |
| paul_ | for 1.2 yet | 16:49 |
| nuclear_eclipse | not to my knowledge | 16:49 |
| nuclear_eclipse | I don't like any of the suggested logos | 16:49 |
| paul_ | dhx_m: make a new logo | 16:50 |
| dhx_m | the current one looks good IMO | 16:50 |
| dhx_m | paul_: part of graphics for 1.3 | 16:50 |
| nuclear_eclipse | I think our current image is excellent, but without the source image to modify, we're screwed | 16:50 |
| paul_ | dhx_m: make a new logo for 1.2.0 | 16:50 |
| dhx_m | paul_: too late :p | 16:50 |
| paul_ | nuclear_eclipse: well there was reasons to change it iirc? | 16:50 |
| paul_ | ;p | 16:50 |
| dhx_m | paul_: I'll do it... for 1.3 :p | 16:50 |
| nuclear_eclipse | so paul_, you're complaint is more than I didn't explain enough about the individual features/changes? | 16:50 |
| dhx_m | as an SVG | 16:50 |
| paul_ | nuclear_eclipse: do you think we should mention or not mention the graph changes? | 16:51 |
| nuclear_eclipse | paul_: the only reason I know of to change the logo is to add "BT" to the end of the name... | 16:51 |
| nuclear_eclipse | I dunno | 16:51 |
| dhx_m | in fact, redoing Mantis with XHTML/CSS is high on the list of things I'd like to see :) | 16:51 |
| paul_ | nuclear_eclipse: pm | 16:51 |
| daryn | uh oh...dxh_m said the naughty word | 16:51 |
| paul_ | dhx_m: <video> | 16:52 |
| dhx_m | the text in the logo is ugly... the actual graphic of the Mantis head is cool though | 16:52 |
| paul_ | can we use <video>? | 16:52 |
| dhx_m | paul_: lol | 16:52 |
| nuclear_eclipse | no | 16:52 |
| paul_ | it would be cool | 16:52 |
| dhx_m | what is the naughty word lol? | 16:52 |
| dhx_m | XHTML or CSS? | 16:52 |
| daryn | xhtml | 16:52 |
| nuclear_eclipse | it is cool, but only beta browsers and Safari support it atm | 16:52 |
| daryn | nuclear_eclipse hates that word | 16:52 |
| paul_ | daryn: you got a working laptop yet? :P | 16:52 |
| daryn | sort of | 16:52 |
| paul_ | heh | 16:53 |
| paul_ | get to work :P | 16:53 |
| daryn | they gave me the original one back but it still has issues | 16:53 |
| dhx_m | oh I see HTML is basically a revision of XHTML | 16:53 |
| dhx_m | HTML5 | 16:53 |
| paul_ | bbiab | 16:53 |
| dhx_m | I'll hit anyone that adds <video> to Mantis :p | 16:54 |
| nuclear_eclipse | HTML5 is a compromise between HTML4 and XHTML, but with a lot of new features too, like <video> and <audio> | 16:54 |
| dhx_m | I was thinking of replacing priority icons with Unicode text because I hate having 100000 little images on a website | 16:54 |
| dhx_m | but then Unicode doesn't have enough arrows for us :( | 16:54 |
| dhx_m | TBH HTML5 is going to have so much crap in it | 16:54 |
| dhx_m | worker threads you'll hate | 16:54 |
| dhx_m | now websites can burn 100% of your CPU while they run bloated Javascript crap :p | 16:55 |
| nuclear_eclipse | well, you're not forced to use any of the new stuff, you know... | 16:55 |
| nuclear_eclipse | and tbh, websites could burn 100% of my CPU before too, it's called Flash video... | 16:55 |
| dhx_m | yeah but you can't control what other people do to their sites | 16:55 |
| dhx_m | NAUGHTY WORD! | 16:55 |
| * nuclear_eclipse stabs dhx_m | 16:56 | |
| kenguest | "people"? | 16:56 |
| dhx_m | hah | 16:56 |
| dhx_m | nuclear_eclipse: I take back XHTML... | 16:58 |
| dhx_m | nuclear_eclipse: after seeing xforms | 16:59 |
| nuclear_eclipse | lol | 16:59 |
| nuclear_eclipse | tbh, I really think that any form of *TML is a very poor way of creating web applications | 16:59 |
| dhx_m | their draft has a "select" control and wait for it... a "select1" control | 16:59 |
| dhx_m | and besides, I hate XML | 17:00 |
| nuclear_eclipse | I really think that todays html/css/javascript garbage is just a giant clusterfuck of poor implementations built on mountains of poorer implementations | 17:00 |
| dhx_m | I don't mind CSS too much... but HTML is another matter | 17:01 |
| nuclear_eclipse | if websites were designed and built using something similar to a native windowing system, with GUI toolkits designed from the ground up for presenting data and interaction controls to the user, then everything would be so much better and easier to design and implement | 17:02 |
| dhx_m | yep | 17:02 |
| dhx_m | do we have anything like that in existence though? | 17:02 |
| dhx_m | web browsers are a giant usability disaster IMO | 17:02 |
| nuclear_eclipse | yeah, Qt, Gtk, Cocoa, and *gasp* XUL | 17:03 |
| dhx_m | GTK? | 17:03 |
| dhx_m | IMO what you need to be able to do is tell the renderer that you've got "a list of options" | 17:04 |
| dhx_m | and it can do whatever it likes to display those to the user | 17:04 |
| nuclear_eclipse | well, that's the point of a toolkit | 17:04 |
| dhx_m | I guess as long as people separate data and UI, it isn't too much of an issue | 17:05 |
| dhx_m | and if you have good development tools to make UI writing easy, it becomes trivial to make UIs on different toolkits/platforms | 17:05 |
| nuclear_eclipse | you declare a list object, define a set of options for it, and place it in a container with a given layout method, and let the client render using local idioms or themes | 17:06 |
| dhx_m | yep | 17:06 |
| dhx_m | when am I meant to use db_param() as opposed to placing numbers straight into query strings? | 17:10 |
| dhx_m | ah I see... must be always | 17:10 |
| nuclear_eclipse | use db_param() whenever you're putting in something that could possibly come from user or data input | 17:11 |
| dhx_m | yep | 17:11 |
| nuclear_eclipse | eg, "WHERE xxx=1" is fine | 17:11 |
| nuclear_eclipse | but if it's anything dynamic, use db_param | 17:11 |
| dhx_m | ok :) | 17:12 |
| nuclear_eclipse | so paul_, your only complaint on the release notes is that I didn't explain enough about the individual features/changes? | 17:14 |
| dhx_m | I have a new feature :) | 17:19 |
| dhx_m | roadmap sorting by completion status, priority, status, last update time | 17:19 |
| nuclear_eclipse | uh oh | 17:19 |
| dhx_m | with priority icons used instead of the "-" when priority icons are on (but don't show priority text) | 17:20 |
| dhx_m | I'll get a screenshot | 17:20 |
| nuclear_eclipse | sounds messy... | 17:21 |
| shardy | dhx_m: thanks, was able to find the info on how to add it, all set now | 17:23 |
| shardy | (adding a new status state) | 17:23 |
| shardy | much appreciated! | 17:23 |
| dhx_m | :) | 17:23 |
| dhx_m | that is how I first did it too | 17:23 |
| dhx_m | documentation in that area is not too bad (I thought it'd be worse) | 17:23 |
| shardy | yeah, it's pretty straightforward once i was able to find it :) | 17:23 |
| dhx_m | nuclear_eclipse: http://www.mantisbt.org/bugs/file_download.php?file_id=2359&type=bug | 17:28 |
| dhx_m | nuclear_eclipse: I'm thinking that the priority shouldn't be shown for resolved issues though | 17:28 |
| nuclear_eclipse | that looks like information overload... | 17:29 |
| dhx_m | nuclear_eclipse: I agree it is a bit cluttered but I can see why people would want to sort by priority | 17:29 |
| nuclear_eclipse | right, but I think having the icons makes it less useful | 17:29 |
| dhx_m | ok | 17:30 |
| nuclear_eclipse | I mean, you can't tell at a glance where two and three arrows starts or ends | 17:30 |
| dhx_m | yep | 17:30 |
| nuclear_eclipse | and with a bunch of three arrows in a line, i just looks like noise | 17:30 |
| nuclear_eclipse | but tbh, I think the entire roadmap/changelog display needs to be overhauled | 17:31 |
| dhx_m | maybe in that case I can use priority_significance_threshold to change the "-" to "!" if it is high priority? | 17:31 |
| dhx_m | yeah I saw your comment to that effect on some bugs | 17:31 |
| dhx_m | personally I don't see the need for it | 17:31 |
| dhx_m | when you can just view issues for a target version | 17:31 |
| dhx_m | unless it is more of a Wiki page which has human-created ideas on what is planned | 17:32 |
| dhx_m | anyway, icons aside, what do you think of this sort order: | 17:32 |
| nuclear_eclipse | I somewhat like the way that Redmine handles it -- their roadmap is just a list of versions and overall status of the version, and then they offload viewing the related issues to the filters page | 17:33 |
| nuclear_eclipse | http://www.redmine.org/projects/redmine/roadmap | 17:33 |
| dhx_m | trac style | 17:33 |
| dhx_m | yep | 17:33 |
| nuclear_eclipse | I just think that a plaintext roadmap/changelog is over-simplifying the part of viewing the issues, and is visually distracting to boot | 17:34 |
| dhx_m | if resolved sort by priority, status, last update time | 17:34 |
| dhx_m | oops | 17:34 |
| dhx_m | if not resolved sort by priority, status, last update time | 17:34 |
| dhx_m | if resolved sort by last update time | 17:34 |
| dhx_m | yep | 17:35 |
| nuclear_eclipse | if we offload viewing the issues to the filters page, then it doesn't matter what our default sorting is; the filters page allows the user to change that | 17:35 |
| nuclear_eclipse | but either way, I think that's to be left for post-1.2 | 17:35 |
| nuclear_eclipse | atm, I just want to figure out what paul's doing, and what exactly he wants done with release notes | 17:36 |
| dhx_m | the filters page isn't smart enough (yet) to let you have complex ordering | 17:36 |
| nuclear_eclipse | I would argue that complex ordering is a) not really necessary, and b) unintuitive... | 17:37 |
| nuclear_eclipse | if the point of complex ordering is to segregate data, then filter out the unwanted data, and order by the next most important field... | 17:37 |
| dhx_m | true | 17:38 |
| nuclear_eclipse | eg, the redmine roadmap has two links, one for closed issues, one for open issues | 17:38 |
| nuclear_eclipse | so then you can set a default sort order on each of those links differently from the other | 17:39 |
| dhx_m | I'd argue "closed" is not really of interest in a roadmap | 17:39 |
| dhx_m | I'd prefer a roadmap to show something like a burndown chart or some other high-level management view over progress | 17:40 |
| nuclear_eclipse | well, yes/no -- redmine doesn't really have a "changelog" like mantis, so the roadmap in this case serves as the changelog as well | 17:40 |
| dhx_m | maybe I'm thinking of more of a "Summary" page though | 17:40 |
| dhx_m | ah ok | 17:40 |
| dhx_m | redmine's filter system is not too bad | 17:41 |
| dhx_m | except it needs Javascript | 17:41 |
| dhx_m | I still think I prefer Mantis' system for simplicity | 17:42 |
| nuclear_eclipse | redmine does use javascript... | 17:42 |
| paul_ | right and home | 17:43 |
| paul_ | apparently php6 windows snaps have now been fixed :P | 17:43 |
| nuclear_eclipse | so paul_, your only complaint on the release notes is that I didn't explain enough about the | 17:43 |
| nuclear_eclipse | individual features/changes? | 17:43 |
| paul_ | yep | 17:46 |
| paul_ | and that they aren't a pdf | 17:46 |
| paul_ | and that they dont cover graphs, but that might be a good thing | 17:46 |
| nuclear_eclipse | yth does it need to be a pdf? | 17:46 |
| paul_ | dhx_m's idea - prettier | 17:46 |
| paul_ | :) | 17:46 |
| nuclear_eclipse | prettier, but what's the point? | 17:47 |
| paul_ | it's prettier :) | 17:47 |
| nuclear_eclipse | it's a lot of effort for something that nobody's going to read... | 17:47 |
| dhx_m | yeah why not just use View Issues with a filter in place | 17:47 |
| dhx_m | in fact | 17:47 |
| dhx_m | why don't we just kill the "Roadmap" page and replace it with a dropdown box that is a shortcut to view issues with a filter? | 17:48 |
| nuclear_eclipse | lol | 17:48 |
| dhx_m | of course, it'd need a new menu system | 17:49 |
| dhx_m | but I think Mantis could do with one anyway | 17:49 |
| nuclear_eclipse | I think it's still useful to show more info about each release, completion graphics, etc | 17:49 |
| dhx_m | hmmm... sounds to me like that could be another option | 17:49 |
| dhx_m | if you want to view graphs and pretty pictures, you probably don't want to see a list of issues at the same time IMO | 17:50 |
| dhx_m | I can see a big need for a page that shows a burn down chart, progress updates, etc | 17:50 |
| dhx_m | that'd be very useful for managers/etc to determine progress towards the next release/milestone | 17:51 |
| dhx_m | or better still... a menu where the options are the version numbers themselves | 17:53 |
| paul_ | how can i git diff two branches? | 17:54 |
| dhx_m | if you click on the version number, it'll work out if you should see a roadmap/changelog depending on if the version is released | 17:54 |
| nuclear_eclipse | paul_: `git diff branch1..branch2` or `git diff branch1...branch2` to diff based on branching point | 17:55 |
| dhx_m | oh well... no point talking... I should do mockups | 17:55 |
| CIA-18 | Mantisbt: jreese * rb3c834c8ad62 /core/timeline_api.php: Remove stagnant/failed timeline api. | 17:57 |
| dhx_m | ah poor API | 17:58 |
| nuclear_eclipse | it was an initial attempt at extracting behavior out of the roadmap/changelog pages, but since then I've decided that I don't like those pages in the first place... | 17:59 |
| nuclear_eclipse | and some of the stuff that was added has just caused more headaches | 17:59 |
| dhx_m | yep | 18:00 |
| nuclear_eclipse | paul_: what do want to be said about graphs in release notes? | 18:01 |
| nuclear_eclipse | paul_: you also need to resolve the three issues assigned to you for 1.2.... | 18:01 |
| nuclear_eclipse | http://www.mantisbt.org/bugs/search.php?project_id=1&handler_id=2405&sticky_issues=off&target_version=1.2.x&sortby=last_updated&dir=DESC&hide_status_id=80 | 18:02 |
| dhx_m | Mantis #3 at Google for "bug tracker" :) | 18:14 |
| dhx_m | above JIRA :p | 18:14 |
| nuclear_eclipse | paul_: I'm just gonna roll an rc1 release as-is -- we can come up with a better set of release notes for a final release... | 18:17 |
| CIA-18 | Mantisbt: hickseydr live * r229a6848f6eb / (bug_stick.php core/html_api.php lang/strings_english.txt): Add Stick/Unstick button to html_buttons_view_bug_page | 18:18 |
| CIA-18 | Mantisbt: paul live * rea0a5bc93182 /lang/ (16 files): Language strings should be single-quoted. | 18:18 |
| CIA-18 | Mantisbt: paul live * ra3ba2c2f47dc /core/string_api.php: Fix: #0010088: Confirmation Link incorrect | 18:18 |
| CIA-18 | Mantisbt: paul live * rc8c95101b89e /core/adodb/ (113 files in 7 dirs): Update ADODB to 5.08 | 18:18 |
| CIA-18 | Mantisbt: paul live * r0c80b35fda6d /lang/ (6 files): Language strings should be single-quoted. | 18:18 |
| CIA-18 | Mantisbt: paul live * rad98e177cc53 /javascript/projax/ (7 files): Update projax to latest release | 18:18 |
| CIA-18 | Mantisbt: paul live * r33d73b38376e /core/access_api.php: Perf: We can shortcircuit out the loop as soon as we get the first true. | 18:18 |
| CIA-18 | Mantisbt: s.mazeland live * re593fed9cecc /lang/ (32 files): Remove obsolete and outdated non-UTF8 language files. All have a better maintained UFT8 equivalent. | 18:18 |
| CIA-18 | Mantisbt: hickseydr live * rd7d911b0a3af /bug_stick.php: Remove trailing white space | 18:18 |
| CIA-18 | Mantisbt: paul live * r0ad3b961ae66 /core/project_api.php: Add function to cache an array of project id's | 18:18 |
| CIA-18 | Mantisbt: paul live * re50944ce0288 /core/ (filter_api.php html_api.php print_api.php string_api.php): Perf: allow passing in charset to avoid calling lang/config_get in loops. | 18:18 |
| nuclear_eclipse | crap | 18:18 |
| CIA-18 | Mantisbt: paul live * rbdf219643277 /admin/install_functions.php: Fix: 0010329: Receive duplicate key on upgrade from 1.1.6 to 1.2.0a3 if existing categories exist with a leading or tailing space | 18:18 |
| CIA-18 | Mantisbt: giallu live * rf516488db540 /tests/ (4 files in 2 dirs): Create Mantis Test Suite configuration | 18:18 |
| CIA-18 | Mantisbt: jreese live * rbf6e5ef1cb08 / (config_defaults_inc.php core/print_api.php): Support attached text files with no file extension. | 18:19 |
| CIA-18 | Mantisbt: s.mazeland live * r023b3027d3d5 /lang/ (36 files): Localisation updates from http://translatewiki.net (2009-04-24 20:55 UTC) | 18:19 |
| nuclear_eclipse | bluh | 18:19 |
| CIA-18 | Mantisbt: jreese live * ra4eec2ffc34e /manage_tags_page.php: Fix #10446: PgSQL errors with manage_tags_page use of 'WHERE 1'. | 18:19 |
| CIA-18 | Mantisbt: hickseydr live * re55c7c8c0ddd / (512 files in 27 dirs): Merge branch 'master' into 10268 | 18:19 |
| CIA-18 | Mantisbt: s.mazeland live * r723db70d1f2c / (3 files in 2 dirs): Fix #0010445 for master branch. Update copyright year to 2009. | 18:19 |
| * nuclear_eclipse hides | 18:19 | |
| CIA-18 | Mantisbt: paul live * ree7508b5e6ea /core/print_api.php: Missing lang_get call. | 18:19 |
| CIA-18 | Mantisbt: paul live * r49ca189e400a /core/email_api.php: Remove calls to wordwrap() - Phpmailer already wraps text to 80 characters as we specify the width. All these calls to wordwrap do is wrap the text to 75 before we try to wrap to 80. | 18:19 |
| CIA-18 | Mantisbt: paul live * rcb56532e6433 / (4 files in 2 dirs): 1. html formatting | 18:19 |
| CIA-18 | Mantisbt: paul live * rdbe2163a135a /admin/check.php: add check for #0003484: check_mx_record fails on windows platforms | 18:19 |
| CIA-18 | Mantisbt: paul live * r685b9e0bfb91 /core/projax_api.php: html: only display the inline-stylesheet for projax once | 18:19 |
| CIA-18 | Mantisbt: paul live * r1a8caee1f89a /config_defaults_inc.php: mantis_database_table does not exist | 18:19 |
| CIA-18 | Mantisbt: paul live * rfc7a055fc2a8 /core/profile_api.php: Fix: #0010234: List of profiles not sorted alphabetically | 18:19 |
| CIA-18 | Mantisbt: paul live * r1b0a3663e2e9 /admin/schema.php: Fixes for #0009269 | 18:19 |
| CIA-18 | Mantisbt: paul live * ra9278935977a /core/database_api.php: Following siebrand's commit to remove all non-utf8 languages files, and the commit to use utf8 in install.php, we should always send the set names utf8 line to mysql. | 18:19 |
| CIA-18 | Mantisbt: paul live * r1bf8efa313be /admin/install.php: Fixes for #0009269 | 18:20 |
| CIA-18 | Mantisbt: paul live * rc729f169b656 /lang/strings_english.txt: test_langs: Language strings should be single quoted. | 18:20 |
| CIA-18 | Mantisbt: paul live * r734dc2c32707 / (4 files in 2 dirs): Remove microtime_float function. | 18:20 |
| CIA-18 | Mantisbt: s.mazeland live * r1096c049774b / (changelog_page.php roadmap_page.php): * remove some unneeded strtolower() | 18:20 |
| CIA-18 | Mantisbt: paul live * ra2146d2a8b13 / (core.php core/email_api.php): autload disposable + phpmailer classes | 18:20 |
| * nuclear_eclipse sets post-commit hook to only trigger ciabot on certain branches..... | 18:20 | |
| CIA-18 | Mantisbt: paul live * r49a5c45ac7f2 /core/ (database_api.php session_api.php): Session api requires gpc, database api does not require gpc. | 18:20 |
| CIA-18 | Mantisbt: s.mazeland live * rc81c3171c79f / (core.php core/email_api.php): Merge branch 'master' of git://mantisbt.org/mantisbt | 18:20 |
| CIA-18 | Mantisbt: s.mazeland live * rf2c854a349dd / (3 files in 3 dirs): Remove 'charset' message that is no longer used. Replaced by 'utf-8'. | 18:20 |
| CIA-18 | Mantisbt: jreese live * r4f83762b98c0 /bug_report_page.php: Fixed duplicate summary texts on the simple report page. | 18:20 |
| CIA-18 | Mantisbt: paul live * rcb8575faab46 /admin/check.php: Add checks to check.php to check that database is set up for utf8: | 18:20 |
| CIA-18 | Mantisbt: paul live * r165c12d191f3 /login_page.php: shorten upgrade check logic | 18:20 |
| CIA-18 | Mantisbt: jreese live * re21a1dfa72d0 /bugnote_view_inc.php: Fix inconsistencies with both the collapse area and execution of events for pages without bugnotes. | 18:20 |
| CIA-18 | Mantisbt: paul live * r965959b05a05 /core/print_api.php: Remove extra charset param | 18:20 |
| CIA-18 | Mantisbt: paul live * re5b0087dc808 /admin/check.php: Add check to display adodb version - currently just check >5 | 18:20 |
| CIA-18 | (64 lines omitted) | 18:21 |
| CIA-18 | Mantisbt: s.mazeland live * r2d8be0aa8ce5 /lang/strings_english.txt: Reduce shouting in messages. Only left in e-mail messages where we cannot use class styling if we really would want to shout at users. | 18:21 |
| CIA-18 | Mantisbt: paul live * re45b8f821a62 /api/soap/mantisconnect.php: library move broke soap api include | 18:21 |
| CIA-18 | Mantisbt: paul live * r92d11d9e5a29 /core/wiki_api.php: remove unused function: wiki_ensure_enabled | 18:21 |
| CIA-18 | Mantisbt: paul live * r47b1f127a92b / (12 files in 2 dirs): replace print_date with echo date -> calls to echo print_date are rather pointlesss. | 18:21 |
| CIA-18 | Mantisbt: s.mazeland live * re9cbf60f8c1b / (10 files in 5 dirs): Fix: #0007484: implement RTL css | 18:21 |
| CIA-18 | Mantisbt: paul live * ra3ba2c2f47dc /core/string_api.php: Fix: #0010088: Confirmation Link incorrect | 18:21 |
| CIA-18 | Mantisbt: paul live * r2f814980a775 /csv_export.php: Fixes for #0010420: Custom fields with newline break CSV export | 18:21 |
| CIA-18 | Mantisbt: paul live * rd2f77f2bd213 / (4 files in 2 dirs): Fix: 0010421: Default filename corrupted if project name contains special chars | 18:21 |
| CIA-18 | Mantisbt: paul live * rc36df5bbf23c / (185 files in 6 dirs): following giallu's change to use set_include_path to set first require directory as core dir, we no longer need to use core path in require_once | 18:21 |
| CIA-18 | Mantisbt: paul live * r994ce15eae22 /core/print_api.php: Fix: #0005196: core/print_api.php print_successful_redirect function calls html_api functions in wrong order | 18:21 |
| CIA-18 | Mantisbt: paul live * re50944ce0288 /core/ (filter_api.php html_api.php print_api.php string_api.php): Perf: allow passing in charset to avoid calling lang/config_get in loops. | 18:21 |
| CIA-18 | Mantisbt: s.mazeland live * re593fed9cecc /lang/ (32 files): Remove obsolete and outdated non-UTF8 language files. All have a better maintained UFT8 equivalent. | 18:21 |
| CIA-18 | Mantisbt: paul live * r59c531232d84 /lang/strings_english.txt: implement dhx_m suggestion (Time zone is two words) | 18:21 |
| CIA-18 | Mantisbt: paul live * rea0a5bc93182 /lang/ (16 files): Language strings should be single-quoted. | 18:22 |
| CIA-18 | Mantisbt: s.mazeland live * r023b3027d3d5 /lang/ (36 files): Localisation updates from http://translatewiki.net (2009-04-24 20:55 UTC) | 18:22 |
| CIA-18 | Mantisbt: jreese live * rbf6e5ef1cb08 / (config_defaults_inc.php core/print_api.php): Support attached text files with no file extension. | 18:22 |
| nuclear_eclipse | arg, it's still going? | 18:22 |
| CIA-18 | Mantisbt: jreese live * ra4eec2ffc34e /manage_tags_page.php: Fix #10446: PgSQL errors with manage_tags_page use of 'WHERE 1'. | 18:22 |
| CIA-18 | Mantisbt: jreese live * r6ab1b6defcbb / (core.php core/http_api.php): Extracted HTTP header routines into new API, allowing plugins to set caching headers for their own pages and content. | 18:22 |
| CIA-18 | Mantisbt: jreese live * r4f6b4662ca21 /core/config_api.php: Improve config evaluation routines; allow \% to escape and prevent processing. | 18:22 |
| CIA-18 | Mantisbt: giallu live * r1a91f7884f3a /tests/ (AllTests.php soap/AllTests.php): Add soap tests | 18:22 |
| CIA-18 | Mantisbt: jreese live * r209070a7ff3f /core/email_api.php: Remove old email_api functions that are no longer used. | 18:22 |
| dhx_m | oh dear :p | 18:22 |
| CIA-18 | Mantisbt: jreese live * r61096547d19a / (7 files in 3 dirs): Merge branches 'http', 'plugin-uses' and 'project-names' | 18:22 |
| CIA-18 | Mantisbt: s.mazeland live * r2b2ec01451c3 /lang/ (strings_catalan.txt strings_swissgerman.txt): Localisation updates from http://translatewiki.net (2009-06-03 11:38 UTC) | 18:22 |
| CIA-18 | Mantisbt: paul live * rbdf219643277 /admin/install_functions.php: Fix: 0010329: Receive duplicate key on upgrade from 1.1.6 to 1.2.0a3 if existing categories exist with a leading or tailing space | 18:22 |
| nuclear_eclipse | notes for a final release... | 18:22 |
| CIA-18 | Mantisbt: paul live * r648f388e1c07 /core.php: Reorganise core.php to allow setting of core_path following the previous include path changes. | 18:22 |
| CIA-18 | Mantisbt: paul live * r2912c78345c5 / (config_defaults_inc.php proj_doc_page.php): Fix: 0003436: cannot configure threshold for documentation edit access | 18:22 |
| CIA-18 | Mantisbt: paul live * r49ca189e400a /core/email_api.php: Remove calls to wordwrap() - Phpmailer already wraps text to 80 characters as we specify the width. All these calls to wordwrap do is wrap the text to 75 before we try to wrap to 80. | 18:23 |
| dhx_m | is this going to list every commit since 1.2.0a3? | 18:23 |
| CIA-18 | Mantisbt: paul live * r4f0fd58c900d /core/logging_api.php: Add support for logging to Firebug ( http://www.firephp.org/ ) as logging method. | 18:23 |
| CIA-18 | Mantisbt: paul live * rcbcefe330ccb /library/README.libs: Add upstream library details for disposable email checker | 18:23 |
| CIA-18 | (101 lines omitted) | 18:23 |
| CIA-18 | Mantisbt: paul live * r59c531232d84 /lang/strings_english.txt: implement dhx_m suggestion (Time zone is two words) | 18:23 |
| CIA-18 | Mantisbt: paul live * r2ef2f58e19be /core/ (constant_inc.php ldap_api.php logging_api.php): Add initial logging for ldap | 18:23 |
| CIA-18 | Mantisbt: paul live * r13fc9fb106a2 /core/database_api.php: We do not need to set $t_core_dir in database api | 18:23 |
| CIA-18 | Mantisbt: paul live * r77d6bf4ab711 /core.php: DIRECTORY_SEPARATOR should be used over / or \ | 18:23 |
| dhx_m | lol @ 101 lines omitted | 18:23 |
| CIA-18 | Mantisbt: paul live * r20ba0ea17877 / (335 files in 27 dirs): ADODB is 3rd party library. Added upstream details to README.libs | 18:23 |
| CIA-18 | Mantisbt: paul live * reba305694fcf /core/ (bugnote_api.php email_api.php relationship_api.php): Adjust how we cache loaded bugnotes | 18:23 |
| CIA-18 | Mantisbt: paul live * r3fbc4a38aba3 /core/filter_api.php: make date filters work. Note: we still need to deal with the offset between the stored data (gmt/utc) and the localtimezone for queries like this. | 18:23 |
| CIA-18 | Mantisbt: paul live * r97b67e4bbb2f / (23 files in 4 dirs): Changes to bug object | 18:23 |
| CIA-18 | Mantisbt: paul live * r40b52adf18c8 /admin/schema.php: Fix: Missing schema update in datetime->int conversion | 18:23 |
| CIA-18 | Mantisbt: hickseydr live * r313abf14e50c / (5 files in 3 dirs): Rename OPEN to $g_default_bug_resolution | 18:24 |
| CIA-18 | Mantisbt: jreese live * rc40a83d192c5 /core/plugin_api.php: Fixed bug with plugin initialization retries. | 18:24 |
| CIA-18 | Mantisbt: paul live * rb39854a24240 /core/classes/MantisEnum.class.php: is_blank() | 18:24 |
| CIA-18 | Mantisbt: paul live * rb47f9245291c / (9 files in 3 dirs): split->explode | 18:24 |
| CIA-18 | Mantisbt: paul live * r172c77f1de21 /core/ (16 files): Whitespace found at end of line | 18:24 |
| CIA-18 | Mantisbt: giallu live * rd3290c627293 /api/soap/mantisconnect.php: Fix nusoap inclusion method | 18:24 |
| CIA-18 | Mantisbt: giallu live * r10ffb96b7eb5 /tests/TestConfig.php: Fix warning | 18:24 |
| CIA-18 | Mantisbt: giallu live * r7066e6b44774 / (26 files in 2 dirs): Move nusoap to library/ | 18:24 |
| CIA-18 | Mantisbt: paul live * rb06b0108d7a3 /admin/ (install_functions.php schema.php): Reduce number of queries required for the data conversion | 18:24 |
| CIA-18 | Mantisbt: hickseydr live * rb51b4435dd7e / (bug_change_status_page.php manage_config_workflow_page.php): Replace REOPENED with $g_bug_reopen_resolution | 18:24 |
| CIA-18 | Mantisbt: vboctor live * r7106957595c3 /admin/install_functions.php: Fixed undefined variable warning in setup. | 18:24 |
| CIA-18 | Mantisbt: paul live * r745719001c89 / (admin/check.php core/constant_inc.php): Add WARN to constant_inc. | 18:24 |
| * nuclear_eclipse taps foot | 18:24 | |
| CIA-18 | Mantisbt: paul live * r0f47458541f7 /core/utility_api.php: Whitespace found at end of line | 18:24 |
| CIA-18 | Mantisbt: vboctor live * rac71e94db3a0 / (login.php login_page.php): Fixes #10505: On Login failure, keep user name populated and place the focus in the password field. | 18:24 |
| CIA-18 | Mantisbt: paul live * r632d590ea8df /core/string_api.php: Fix string_prepare_header | 18:25 |
| CIA-18 | Mantisbt: paul live * rb7b41015ca0f /core.php: Indentation within file inconsistent | 18:25 |
| CIA-18 | (118 lines omitted) | 18:25 |
| dhx_m | is this because you created a branch? | 18:25 |
| CIA-18 | Mantisbt: paul live * ra058e7596193 / (9 files in 4 dirs): Add initial timezone selection functionality | 18:25 |
| CIA-18 | Mantisbt: hickseydr live * rc7ecb89dacb0 /bug_change_status_page.php: Replace ASSIGNED with $g_bug_assigned_status | 18:25 |
| CIA-18 | Mantisbt: s.mazeland live * reb7eee06cfb4 /plugins/ (2 files in 2 dirs): Add Dutch translations for core plugins. | 18:25 |
| CIA-18 | Mantisbt: hickseydr live * ra0525539884f / (11 files in 2 dirs): Replace CLOSED with $g_bug_closed_status_threshold | 18:25 |
| dhx_m | :) | 18:25 |
| dhx_m | all of that because you created a new branch heh? | 18:25 |
| dhx_m | CIA is rather dumb | 18:25 |
| CIA-18 | Mantisbt: s.mazeland live * r51e4567d5da9 /plugins/ (2 files in 2 dirs): Fix: #0010579: add Russian to MantisBT Core Formating and XMLImportExport. Contributed by Kirill. | 18:25 |
| * nuclear_eclipse waits for cia to return and continue spmamming | 18:25 | |
| nuclear_eclipse | arg | 18:25 |
| CIA-18 | Mantisbt: hickseydr live * r7b940ad5f931 / (5 files in 2 dirs): Replace NEW_ with $g_bug_submit_status | 18:25 |
| dhx_m | it'll probably show the Mantis project as having 10000000000 commits today? :p | 18:25 |
| CIA-18 | Mantisbt: hickseydr live * r1a96b94b7d5d /bug_stick.php: No need to specify core path anymore | 18:26 |
| CIA-18 | Mantisbt: jreese live * r209070a7ff3f /core/email_api.php: Remove old email_api functions that are no longer used. | 18:26 |
| CIA-18 | Mantisbt: s.mazeland live * r2b2ec01451c3 /lang/ (strings_catalan.txt strings_swissgerman.txt): Localisation updates from http://translatewiki.net (2009-06-03 11:38 UTC) | 18:26 |
| dhx_m | lol @ http://cia.vc/ | 18:26 |
| CIA-18 | Mantisbt: paul live * raa618485eaa3 /core/email_api.php: PHPmailer should throw exceptions + catch exception adding email addresses. | 18:26 |
| CIA-18 | Mantisbt: jreese live * rb128f30f666e /core/category_api.php: Only display category's project name if different from current. | 18:26 |
| dhx_m | Paul with 270 commits and growing | 18:26 |
| CIA-18 | Mantisbt: vboctor live * rbabd70fe9ae8 /core/columns_api.php: Fixes #10568: Reproducibility column is shown as numbers in issue list. | 18:26 |
| CIA-18 | Mantisbt: paul live * r25595427939c /library/README.libs: update readme.libs | 18:26 |
| nuclear_eclipse | ... | 18:26 |
| CIA-18 | Mantisbt: paul live * rae74f935e669 /core/ (5 files): Remove db_prepare_strings before db_query_bound calls | 18:26 |
| CIA-18 | Mantisbt: paul live * r55e2ec2f28e6 / (core/string_api.php tests/Mantis/StringTest.php): collapse empty ?'s in string_sanitise_url | 18:26 |
| CIA-18 | Mantisbt: jreese live * ra583c8a1d534 / (5 files in 2 dirs): Add events for including/excluding users from notification lists. | 18:26 |
| CIA-18 | Mantisbt: s.mazeland live * r1bd263e74bd0 /core/html_api.php: Add a space after the semi-colon in '<meta http-equiv='Content-type' content='text/html; charset=utf-8' />' | 18:26 |
| CIA-18 | Mantisbt: hickseydr live * r1317d03ba014 /core/project_api.php: Make project upload path non-optional again | 18:26 |
| CIA-18 | Mantisbt: vboctor live * r87866cd52c83 /print_bug_page.php: Fixes #10562: Printing Bug does not work with configuration = SIMPLE_ONLY; | 18:26 |
| CIA-18 | (97 lines omitted) | 18:26 |
| CIA-18 | Mantisbt: paul live * r226eb0fe7c0b /core/classes/MantisEnum.class.php: actually go back to not using is_blank -> this change broke my phpunit test setup. | 18:27 |
| CIA-18 | Mantisbt: paul live * rdb4c72a09ef1 / (core.php core/html_api.php core/wiki_api.php): Only load wiki support if wiki is enabled | 18:27 |
| nuclear_eclipse | ... | 18:27 |
| dhx_m | lol @ being first place on cia.vc | 18:27 |
| nuclear_eclipse | all I did was freaking reset live branch to master... | 18:27 |
| dhx_m | haha | 18:28 |
| dhx_m | maybe you should of deleted the live branch | 18:28 |
| dhx_m | and then recreated? | 18:28 |
| nuclear_eclipse | perhaps -- I didn't realize it was going to result such spammage.... | 18:28 |
| dhx_m | nah I wouldn't either | 18:28 |
| dhx_m | cia.vc is broken because it thinks these commits happened 10min ago | 18:29 |
| nuclear_eclipse | well, it thinks that because our repo's update hook sent cia all that data ten minutes ago -- it doesn't actually look at our real repo | 18:29 |
| dhx_m | oh ;) | 18:30 |
| nuclear_eclipse | cia is just a "dumb" repeater service | 18:30 |
| paul_ | nice one | 18:30 |
| paul_ | :) | 18:30 |
| dhx_m | yep | 18:30 |
| dhx_m | Paul: you're number #2 | 18:30 |
| nuclear_eclipse | you just send it some specially-constructed XML, and it announces on the channel you specifiy | 18:30 |
| dhx_m | get nuclear_eclipse to do it again and you'll be #1 :p | 18:30 |
| dhx_m | ah I see | 18:31 |
| nuclear_eclipse | ok, I just reset the update hook to only send cia data if something happens to master... | 18:31 |
| dhx_m | so technically it'd be our fault then :p | 18:31 |
| paul_ | nuclear_eclipse: dont modify cia hooks pls | 18:31 |
| nuclear_eclipse | I'm not | 18:32 |
| nuclear_eclipse | I'm modifying our own hook that calls the ciabot.pl script | 18:32 |
| paul_ | could you do that spam again | 18:32 |
| paul_ | when you make master-1.2.x branch | 18:32 |
| nuclear_eclipse | no | 18:32 |
| paul_ | so I get top place :P | 18:32 |
| dhx_m | lol | 18:32 |
| paul_ | dhx_m: quickly, how do i make a branch | 18:32 |
| dhx_m | haha | 18:32 |
| dhx_m | git branch newbranch | 18:33 |
| dhx_m | but that didn't do it :p | 18:33 |
| paul_ | what about if we replayed all the changesets | 18:33 |
| paul_ | i'm sure we can make a way to do it | 18:33 |
| * nuclear_eclipse stabs paul_ | 18:33 | |
| paul_ | . | 18:33 |
| paul_ | git diff two branch again? | 18:34 |
| nuclear_eclipse | `git diff branch1..branch2` or `git diff branch1...branch2` | 18:34 |
| nuclear_eclipse | the first includes *all* diffs, the second only diffs from the branching point | 18:34 |
| paul_ | can i tell it to exlucde new files? | 18:35 |
| nuclear_eclipse | I dunno | 18:35 |
| nuclear_eclipse | `git help diff` | 18:35 |
| dhx_m | nuclear_eclipse: did that hook happen to also send emails to the git commit mailing list? :p | 18:36 |
| paul_ | hopefully | 18:36 |
| paul_ | :) | 18:36 |
| nuclear_eclipse | a different hook would have, but it seems to have failed... | 18:36 |
| dhx_m | hah | 18:36 |
| nuclear_eclipse | probably from such a gigantic amount of content | 18:36 |
| dhx_m | so what exactly is the "live" branch anyway? | 18:37 |
| nuclear_eclipse | that's what the live site uses these days | 18:37 |
| nuclear_eclipse | eg, allows me/giallu/vboctor to keep up with what revision the site is on, cherry-pick commits, etc | 18:37 |
| dhx_m | ah gotcha | 18:38 |
| nuclear_eclipse | paul_: I'm just gonna roll an rc1 release as-is -- we can come up with a better set of release notes for a final release... | 18:38 |
| dhx_m | sounds good | 18:38 |
| nuclear_eclipse | hi glenn | 18:48 |
| mantisbot | New bug: Bug 10619 - berdam - open - new | 19:04 |
| mantisbot | New bug: User with permission to write but not see other issues - http://www.mantisbt.org/bugs/view.php?id=10619 | 19:04 |
| nuclear_eclipse | rc1 is officially released :P | 19:19 |
| paul_ | omg | 19:25 |
| paul_ | no ;/ | 19:25 |
| paul_ | so trunk is breakable again? | 19:30 |
| nuclear_eclipse | yes | 19:30 |
| forgiven | When creating a new project, what is the difference between the public/private status? | 20:56 |
| forgiven | oh hah I found it in the docs. | 20:57 |
| paul_ | nuclear_eclipse: for fucks sake | 21:26 |
| nuclear_eclipse | excuse me? | 21:37 |
| nuclear_eclipse | something I did, or are you just expressing anger hoping I'll respond? :P | 21:38 |
| paul_ | see dev list ;/ | 21:43 |
| kenguest | so. what does the mantis development team use for tracking issues? | 21:43 |
| kenguest | bugzilla? | 21:43 |
| kenguest | :D | 21:44 |
| nuclear_eclipse | irc :P | 21:44 |
| kenguest | heheh | 21:44 |
| nuclear_eclipse | paul_: what specifically on the dev list are you cursing about? | 21:44 |
| paul_ | nuclear_eclipse: SOAPI API | 21:50 |
| paul_ | I swear i've modified that call already | 21:50 |
| paul_ | I just got a reply from giallu to list???? | 21:51 |
| nuclear_eclipse | yeah, I just saw that; rather late for that reply... :P | 21:54 |
| paul_ | why can't users reopen issues???? | 22:01 |
| nuclear_eclipse | because of readonly_threshold? | 22:04 |
| Steve_ | hi | 22:12 |
| Steve_ | i've been running mantis 1.x for a long time and recently setup a server to test 1.2. I'm trying to get dokuwiki working with it and it looks like the old method to set it up doesn't work any longer. Is there a way to get dokuwiki to work with mantis 1.2 or do we wait for a plugin to be released? | 22:15 |
| nuclear_eclipse | Steve_: it should still work (the integration is still there on the mantisbt side) -- you probably need to update your dokuwik to work with the new enum api | 22:17 |
| paul_ | nuclear_eclipse: php6 is going to be fun in a few years | 22:56 |
Generated by irclog2html.py