[06:35] MikeXIII (~Mike@bas8-montreal28-1176488080.dsl.bell.ca) left irc: [09:21] AlekSi (~AlekSi@star.mlzone.ru) joined #redmine-dev. [09:22] AlekSi (AlekSi@star.mlzone.ru) left #redmine-dev. [09:23] AlekSi (~AlekSi@star.mlzone.ru) joined #redmine-dev. [09:26] salvor (~salvor@ALyon-159-1-65-114.w90-57.abo.wanadoo.fr) joined #redmine-dev. [09:37] mosfet (~IceChat7@g229008135.adsl.alicedsl.de) joined #redmine-dev. [10:31] salvor (~salvor@ALyon-159-1-65-114.w90-57.abo.wanadoo.fr) left irc: Quit: /quat [11:53] Thegcat (59cc8961@gateway/web/freenode/ip.89.204.137.97) joined #redmine-dev. [11:54] Thegcat (59cc8961@gateway/web/freenode/ip.89.204.137.97) left irc: Client Quit [12:17] AlekSi (AlekSi@star.mlzone.ru) left #redmine-dev. [12:42] AlekSi (~AlekSi@star.mlzone.ru) joined #redmine-dev. [12:43] Shouldn't it be http://www.redmine.org/wiki/redmine/DevMeeting2 ? [12:48] yah [12:48] edavis10: oi [12:52] Khalsa: I don't have ops here anymore [12:57] I'm going to make some tea and then we can start. [12:59] May I propose a short discussion about gem bundler after the meeting, or it's better to use #redmine? [13:01] #redmine-dev: mode change '+o Khalsa' by ChanServ!ChanServ@services. [13:01] #redmine-dev: mode change '+o edavis10' by Khalsa!~Gursikh@tremulous/developer/Khalsa [13:05] AlekSi: after the meeting would be best. I just posted some comments to the issue about it. [13:05] I read them already, and have a response. :) ok, after the meeting. [13:09] Everyone ready to get this meeting started? [13:10] lol everyone [13:10] I'm working with what we have :) [13:10] im on my phone but ready [13:10] yep, ready [13:10] Khalsa: you able to moderate or do you want me too? [13:11] you please [13:12] Ok, lets start with a quick checkin by any team leaders that are present. We will go in order from the team lead list. It would be good to hear 1) any recent updates in your team 2) any ideas you have 3) any problems you need help resolving. [13:12] wiki:Teams [13:12] edavis10: wiki: wiki:Teams is http://www.redmine.org/projects/redmine/wiki/Teams "Redmine - Teams - Redmine" [13:13] I'll start with the Development team. [13:13] 1) We're slowly working towards the 1.0 release fixing bugs. 0.9.5 is past due and I'm wanting to try to get it ready to be released early next week. [13:14] is JPL AWOL entirely? [13:14] 2) I'd like to brainstorm some ideas about getting more people to help commit patches (Thegcat's idea) [13:15] 3) Two recent problems have been JPL has been inactive for almost a month now and I don't know why. And I've completely burned out on supporting users. [13:16] Khalsa: I've only seen him editing the Donation page ;) [13:16] Khalsa: you're next up with the Documentation team [13:17] Well [13:17] things have been slow as Ilve been working 65 hrs a week now [13:17] but Jon Hertzig has been working on his set and it looks good [13:18] we should have something good and useable with 6 more man hours of work [13:18] set of? [13:18] brand new docs [13:19] other than that not much else to report unfortunetly [13:20] Khalsa: thanks. Don't worry about it, we all get busy and are happy to have whatever help you can contribute. [13:20] Triage team next. [13:21] javajunky (~Adium@80.77.243.22) joined #redmine-dev. [13:21] nada, meinarde and felix has done som work but nothing to report afaik [13:22] ok, I did a bit of triage last night for the Bugmash. Nothing to report from that [13:22] Plugin team. [13:23] Not much here from me. I'm working on some tools/scripts for my own use to make creating plugins easier. The code is on Github and I'd like to release it post-1.0. [13:23] I'm also going to be trying to work on the plugin directory post 1.0 too. [13:23] Release team.... I'll fill in for JPL [13:24] 0.9.5 is a few weeks late already but I'd like to get it out this next week. It will (probably) be the last release for the 0.9.x series. [13:25] 1.0.0 will be the RC and it's on track for release in two weeks (as long as people stop adding last minute bugs to it ;) ). [13:25] After 1.0.0 we'll probably do 1.0.1, 1.0.2 soon afterwards for the official non-RC release [13:26] We could still use some Ruby 1.9 testing on the 1.0 code [13:26] Translations team, I don't think Azamat is here [13:26] nope [13:27] Community relations. (You are going to get sick of reading my typing soon) [13:28] Been quiet on the PR front. I did a short presentation on Redmine for Jumpbox eariler this month and have the slides posted online. I'd like to expand the slidedeck and release it so anyone can reuse and edit them. [13:28] Anyone here for the UX team? [13:30] i missed the last ux meeting [13:30] From what I've seen with the UX team, they are finding a lot of things to improve but need help coordinating them with everyone else (esp doc and dev teams). [13:30] User support team. [13:32] Guess Felix isn't here anymore. [13:32] Anyone have any comments before we move on to the first item? [13:32] neg [13:33] Going once.... [13:34] twice.... [13:34] moving on.... [13:34] Topic: the 0.9.5 release [13:34] JPL gave 0.9.5 a release date of 2010-06-01 but the work never happened on it. [13:35] I want to make the bugs scheduled for it a priority for the Bugmash so I can release it next week. [13:35] he has not replied to anybodys emails for about a month [13:36] Do you have new release date in mind? [13:36] Khalsa: yea, I'm hoping he's just taking a summer vacation and will be back soon. [13:37] AlekSi: 22nd would be great but it might be as late as the 26th. [13:37] lousy french with their month long vacations :p [13:38] A problem I have is that there is no documentation on how to "release" Redmine. I should have access to most of the things I need to release it, if I can figure out the process. [13:38] Other problem is that I don't have permissions to edit the release on Redmine.org. So I can't change the release date or close it out. [13:39] And you can't create a new milestone? [13:39] AlekSi: nope, I only have access to Issue Categories [13:40] May you create a new project Redmine-JPL-is-missing? :) [13:40] But there is nothing stopping us from fixing the bugs and pushing out a release. [13:40] AlekSi: nope, no permissions. [13:40] too bad [13:41] yea, but I'll work with what I have. [13:41] anyone have any other comments on 0.9.5? Anyone want to maintain the 0.9.x series longer? [13:42] honestly yes [13:42] I dont think we should RC untill the teams catchup [13:42] though I am not passonate about this view [13:42] As a side note: I think both bundler and support for SemVer (semver.org) would be great for 1.0 release. [13:43] catchup how? like update the docs? (etc) [13:43] yup [13:43] AlekSi: bundler is a no, it's still pre 1.0. We are already doing semver but since Redmine is pre 1.0 we can do whatever we want ;) [13:44] Ok, may I discuss bundler situation now, not waiting the end of the meeting? [13:44] Khalsa: I like that idea but realisticly with volunteer teams, someone will always be behind. [13:44] true [13:45] Khalsa: I think the RC would be good signal to say "this is the new version, lets get updated to it becasue we will be here for the next few months." [13:45] fair enough [13:45] THe 1.0 might also let us do more community outreach and get some more volunteers to help out. [13:46] so will we be on RC or 1.0.0 final for a few months? [13:46] I think at 1.0.1 (whatever the stable 1.0 is) we should talk to each team and make sure they are going to be ready or are ok being a bit behind. [13:46] ok [13:47] mosfet: 1.0.0 is in two weeks and will be the RC. 1.0.1, 1.0.2, 1.0.3 will be following it. One of them will be the "final, stable" release based on how the RC goes. [13:48] I see [13:48] Then I suspect we'll have monthly-ish patch releases (1.0.4, 1.0.5) until 1.1.0 is ready [13:48] Should we talk about Bundler next really quick? [13:49] I would like to. [13:49] Bundler 0.9 is actually stable. They are hacking 0.10 now. [13:49] #5638 [13:49] edavis10: #5638 is http://www.redmine.org/issues/show/5638 "Redmine - Patch #5638: Use Bundler (Gemfile) for gem management - Redmine" [13:49] And most importantly: we can stick bundler version in Gemfile itself. [13:50] I already use bundler with Gemfile for 2 month. [13:50] I added Gemfiles to few plugins I use. [13:50] No problems. [13:50] AlekSi: let me ask this, why is Bundler needed with Redmine? [13:51] From what I see in your issue, you are trying to use a newer i18n library. [13:52] Because I happened to have Rails 2.3.8 on this machine. [13:52] uh, no, I think it's because of Rails 3 [13:52] Which in turns depends on i18n 0.4 [13:53] Okay, so the problem is because you have installations of newer libraries in place that Redmine is loading on accident? [13:53] Locked bundler protects Redmine installation from unwanted gem updates. [13:53] Yes. [13:54] Also I believe it will make life simpler for plugin developers if their plugins depends on other gems. [13:55] As a developer, bundler seems nice. But 1) 1.0 is already feature frozen 2) I don't want to add a new dependency to 1.0 so late in the release 3) Bundler is still beta and is subject to breaking changes (some call it alpha) and 4) adding it to Rails 2.3.5 isn't easy [13:55] AlekSi: config.gem works inside a plugins' init.rb. I've used it many times already. [13:56] 1, 2) that is the biggest problem [13:56] 3) fixing bundler version inside Gemfile solves this problem [13:56] javajunky (~Adium@80.77.243.22) left irc: Read error: Connection reset by peer [13:56] Personally, I don't want bundler or Rails 3 in Redmine until they are both non-beta and after Redmine 1.0. [13:56] 4) it's not true [13:56] allesmueller (~allesmuel@unixboard/users/allesmueller) joined #redmine-dev. [13:57] It's impossible to add bundler after 1.0 if you really support SemVer. [13:57] AlekSi: bundler/rails 3 would go into trunk for 1.1.0 [13:58] javajunky (~Adium@80.77.243.22) joined #redmine-dev. [13:58] anyone else have any experience or comments about bundler? [13:58] Ok, I'm out of words (and I don't know English good enough to argument more :) ) [13:59] May be it's better to create a post in forum / blog to gather opinions. [13:59] ? [13:59] AlekSi: no problem. I like the idea of Bundler but I've seen and heard of it failing a lot still. I don't want to increase the support burden. [13:59] AlekSi: keep using #5638, it's already active. [13:59] edavis10: AlekSi: #5638 is http://www.redmine.org/issues/show/5638 "Redmine - Patch #5638: Use Bundler (Gemfile) for gem management - Redmine" [13:59] Shall we discuss the Bugmash 1.0 now? [13:59] Sure, this patch is in production for 2 months. :) [14:00] I agree. [14:00] AlekSi: good, another 10 months and I'll consider it stable :p [14:00] lol, ok [14:00] edavis10: actually, my company uses bundler in production for a year... but not with Redmine [14:01] AlekSi: (post 1.0 I'm going to branch Redmine to start on Rails3. You're welcome to put bundler into there) [14:01] ferggo (42a1f8ca@gateway/web/freenode/ip.66.161.248.202) joined #redmine-dev. [14:01] uh, one more quick question [14:01] Rails 2.3.8? [14:02] AlekSi: dunno about .8 yet. I need to review what was changed and if we need it. [14:02] So the Bugmash is going on this weekend. I've created a list of issues for people to start on the wiki. [14:02] I'm going to be around most of this weekend to help with questions, review patches, and commit. [14:02] First off, is anyone here going to participate? [14:03] good question ^^^ [14:03] Im planning to [14:03] Me too. [14:03] meineerde? [14:03] rchady (~rchady@flotsam.chady.org) joined #redmine-dev. [14:03] Khalsa: Out of bed again, so a definitive YES [14:03] Im installing Ubuntu server fresh in a VM right now so I can get started testing with the version I use at work. [14:03] rchady: you in for bug mash? [14:04] I wsih [14:04] I'm going to be doing extra work for work today, plus have a HONEY-DO list a mile long [14:04] For work I have deadlines of Monday morning right now, blah [14:05] I migrated Redmine to production yesterday at work, so now I'm committed. :) [14:05] rchady: my wife is out of the state so my HONEY-DO is taking a back seat to Redmine this weekend ;) [14:05] ok, so at least three, great better than the zero I was expecting. [14:05] ferggo: great, welcome [14:06] edavis10: are we going to use git for this mainly? [14:06] Khalsa: I don't count ;) [14:06] edavis10: ferggo, AlekSi, and meineerde [14:07] Khalsa: I'm an absolutely git newbie, so I'm more firm with patches. [14:07] Where is the bug list btw? [14:07] But I see, what I can make... [14:07] We will use whatever works to get me patches. I'd love to see them uploaded to redmine.org or at least a comment posted to redmine.org like "I've fixed this bug in this git commit [[url]]" [14:07] http://www.redmine.org/wiki/redmine/BugMash-10 [14:07] I'll be watching (and going through) my github pull requests [14:08] Great! [14:08] But if we can post to the issues trackers, that would be more visible and might help motivate more people to contribute. [14:08] May I propose #61? [14:08] AlekSi: #61 is http://www.redmine.org/issues/show/61 "Redmine - Defect #61: Broken character encoding in pdf export - Redmine" [14:08] AlekSi: you can work on any bug you want. I picked smaller ones and ones that would be good to fix in the release. [14:09] ic [14:09] What about the issues in the "These issues have a patch and need to be verified before committing" section. Do these need tests to be written or usage confirmation. [14:09] edavis10: Thanks for making a list. It helps me not freeze up trying to pick something. :) [14:09] mosfet: I'll add a description to those [14:09] If *anyone* needs a working dev installation to hack on I'm happy to provide [14:09] @Khalsa: as a VM? [14:10] no, as a semi-jailed user where you get shell/ftp/svn/git/etc and a public trunk redmine install [14:10] I wonder if there would be any value in having a ready-to-run copy of the code that could be pushed to heroku for testing? [14:11] mosfet: can you check the wiki page and see if the new comments make sense? [14:11] edavis10: ok [14:11] ferggo: yea, my goal with making a list was "here's a smaller set of issues to start with." [14:11] ferggo: re push to Heroku: For what? Testing a patch? [14:12] edavis10: much clearer now, thanks [14:12] Action: rchady has more dev instances of redmine floating around than he can shake a stick at. [14:12] rchady: get a bigger stick :p [14:12] no, a faster one! [14:12] edavis10: For new devs, so we can say "fork this from github and push it to heroku. Now you're ready to test and patch." [14:12] edavis10, yesterday I did an upgrade from r2828 to trunk ;) [14:12] rchady: edavis10: r2828 is http://www.redmine.org/repositories/revision/redmine/2828 "Revision 2828" [14:12] How is the state of the various populator plugins? [14:13] ferggo: oh, as part of the development process.... it might be useful but could be hard. [14:13] meineerde: my plugins.... poort. I might plan a plugin bugmash once the RC is out ;) [14:13] but I'll take patches to them this weekend too :) [14:13] edavis10: Just an idea. I think the effort overhead might quickly outweigh the benefit. [14:14] on that form, any way to get the subject for all the issues in there? [14:14] ferggo: yea, I've been thinking about a one-step installer for Redmine. It could be expanded to a one-step development installer. [14:14] rchady: have to hover on the link. Someone is welcome to edit the page to add titles [14:15] oooh, one of my bugs is on that list [14:15] If anyone is able to help support people in teh bugmash, that would rock. [14:16] ferggo: Who is heroku? [14:16] If the questions are too hard or you need my attention, message me in IRC and I'll try to check in as often as I can. [14:16] #5123 is going to be near impossible to track down, espec considering I don't see anyone else reporting it [14:16] rchady: #5123 is http://www.redmine.org/issues/show/5123 "Redmine - Defect #5123: NoMethodError (undefined method `[]' for nil:NilClass) - Redmine" [14:16] mostfet: heroku.com is awesome rack/rails hosting. They have a "git push" interface to deployment and a free plan that gets you started. [14:17] rchady: That's what I thought... [14:17] fergoo: hmmm, interesting [14:17] rchady: I'm going to throw several tests at it and see if I can reproduce it. If not, I'll close it. [14:17] rchady: looks like the browser somehoe forgets to send the form along [14:17] in theory, Redmine should never 500 error from missing POST data [14:17] I wonder if he has any plugins installed [14:18] I've seen this occur from a malfunctioning plugin (usually mine) [14:18] The other major thing for the bugmash: if someone is looking for what to start on, try to direct them to any open 0.9.5 bugs first. Those are my top priority this weekend. [14:19] What is the baseline for creating these patches? Should I clone the latest from git? [14:19] And we have two sets of CI servers running on Redmine. FinnLabs has their public one and I have a private one. [14:20] ferggo: you want to use the lastest trunk. So either svn's trunk or git's master branch. I can work with both (they are mirrors). [14:20] I also have a CI server running heh [14:20] Anyone else have any bugmash organization questions or comments? [14:20] (I'll help people get started in #redmine in a few hours) [14:21] While I might not be officially involved in this, I'll be monitoring and trying to help if I can [14:21] Is there publicly available CI server for Redmine? [14:21] rchady: thanks [14:21] javajunky (~Adium@80.77.243.22) left irc: Quit: Leaving. [14:21] rchady: Commited patches should are also be checked by http://ci.finn.de in a variety of ways. [14:21] Can I suggest handling all support questions for this in -dev instead? [14:21] http://ci.finn.de/ [14:21] rchady: no, we want to show activity in #redmine [14:21] OK [14:22] if AlexC comes around, can we please shoot him? :) [14:22] we can use -dev for organization questions if #redmine gets busy [14:22] Oh, one other question: [14:22] rchady: no, be nice ;) [14:22] I tend to get along with almost anyone, but certain personality types rub me wrong :P [14:22] Are we going to use Ruby 1.9.2 for development? [14:23] ferggo: Ruby 1.8.6 and 1.8.7 right now. I want to support 1.9.1/1.9.2 in 1.0 so you are welcome to use them if you want to fix compatibily issues. [14:23] (we would also like to support JRuby and rbx if people can help) [14:24] I don't have much experience working with different Ruby versions, but I'd like to learn. I hear great things about 1.9 [14:24] alright, we have 30 minutes left. Khalsa think we should discuss Bug triage? [14:24] edavis10, I think you should do a plugin BugMash too [14:24] not right now of course [14:24] yeah [14:25] ferggo: 1.8.7 is the best with Redmine right now (all tests pass). 1.9 needs some work. [14:25] Khalsa: you want to lead the discussion about Bug Triage? [14:26] Honestly the majority of issues are things JPL needs to answer from us [14:26] edavis10: If I want to pick up specific issue, should I assign it to myself to prevent others from working on it? [14:26] or maybe you can shed some light [14:27] The biggest problem we have is that we don't know *what* exactly to classify certain bugs as [14:27] let me paste the general questions we have here: [14:27] What to do with old bugs? Old support requests? Old but duplicated requests? When to consider stuff outdated? [14:27] How to decide what is in scope for Redmine? For official plugins? Third party plugins? [14:27] Khalsa: speaking frankly.... we need to function without JPL. If we make a decision he doesn't like, he can always reverse it. [14:28] AlekSi: post a comment to the issue saying you're working on this for the "Bugmash" and then in IRC say "I'm working on #xxx" (in #redmine) [14:28] edavis10: tnx [14:28] meineerde: you remember when we had our little bug triage? [14:28] Khalsa: Old bugs => are they still valid? can they be reproduced? [14:28] Khalsa: yes, but it was indeed very little :) [14:30] (sidebar: there is talk about Rubyforge migrating to Redmine ;) ) [14:30] hehe [14:30] hmm, I have a new plugin I'm releasing semi soonish I think too [14:30] edavis10: There are a nmber of huge projects moving to it. [14:31] edavis10: Any updates from Wikimedia? [14:31] meineerde: I know, my email is full of "Add me to UsingRedmine" [14:31] Might be faster for me to build an app to manage that list than to add everyone [14:31] or forward those emails to me or othter by rule and we can help [14:32] it is part of the wiki, no? [14:32] why can't they edit it [14:33] rchady: locked to prevent spamming [14:33] ahh [14:34] too bad those emails could not be converted to tickets assigned to a group of people that manage the wiki [14:34] automatically [14:35] Action: edavis10 gets back from #redmine [14:35] rchady: good idea... let me think about that [14:35] Khalsa: thoughts on my proposal about issue triage? [14:36] which proposal? [14:36] 07:27 <@edavis10> Khalsa: speaking frankly.... we need to function without JPL. If we make a decision he doesn't like, he can always reverse it. [14:36] ah, I'm down [14:36] I'm more than happy to give my opinion on issues, you know that :) [14:36] hehe [14:37] I also tend to :) [14:37] so I guess I'll just get with Felix and answer the questions ourselves + you and write our own guidelines [14:38] I'm planning to change my notification settings on Redmine.org to cut down on my email. What about if you assign the issue to me and ask the question about what to do then? I can review it and close/agree/discuss etc. [14:38] actually we were hoping you would finish redmine_tags to provide this functionality [14:38] I know the direction Redmine is heading towards and have a rough guideline of what's in/out of scope for it. [14:38] we even started pre-tagging stuff in preperation of it [14:39] Khalsa: tagging won't help if I can't get access to Redmine.org :) [14:39] well I know of at least one remote exploit ... [14:39] :p [14:39] fair enough [14:40] Khalsa: haha [14:40] Khalsa: if you have the time, could you create a wiki page with a simple process of how you're sending me issues that need reviewed? Then I can follow it and we can change it as we go. [14:42] anyone else have comments about bug triage and feature planning? [14:42] it is VERY time consuming [14:42] just fyi [14:42] only way to solve that is to improve our tools around reviewing or create better documentation [14:43] Khalsa: I think, we (maybe not neccessary you alone) have to do it some time. The backlog is starting to get even longer without it. [14:43] and for new issues, there could be a more enforced process in place. [14:43] meineerde: agreed, I'm trying to put in my time and resolve things as much as I can. [14:43] it's the only option I suppose [14:43] and I think, we need to have the cochones to just close/reject issues. [14:44] yeah we were quite apprehensive to do it last time [14:44] One big point: if anyone feels overwelmed with what they are working on, please let me know asap. I don't want anyone to burn out or have bad feelings towards Redmine. This is supposed to be fun. [14:44] meineerde: +1 [14:45] meineerde: like the logging issue this week, "Won't fix" [14:45] edavis10: logging issue? [14:46] meineerde: Alex [14:47] Should we try to cover "User Support: Redmine install guides (common platforms/env)"? I think that's your area again Khalsa. [14:48] try to cover where? [14:48] this is planned for docs in general already [14:48] I have some materials I've compiled while installing various versions of Redmine on various versions of Ubuntu and (I think) CentOS. [14:49] ferggo: welcome to the documentation team [14:49] Khalsa: I think, we should try to gather some of the stuff from the web and put it into a common location. [14:49] Once you have a natural place for things, it autmatically gets updated and extended [14:50] meineerde Khalsa: what do you think about a general page that links to a bunch of external resources? At least then we can point people there instead of Google? [14:50] edavis10: +1 That way, we can select good ones. [14:50] But I think, in the long run, they should be on r.o [14:51] I'll create a wiki page for it, we'll just need to update it as we go [14:51] I do think that the install doc(s) could be cleaned up some [14:51] Make it more user friendly, maybe even look a bit nicer [14:51] meineerde: ideally yes, but if people have already written good docs offsite we should take advantage of them if we can. [14:51] rchady: good suggestion [14:51] Which reminds me, do we have any good themers available? :) [14:51] Install docs are IN PROGRESS (like all other docs) [14:52] edavis10: what I meant was, that we can maybe convonce people to copy/move the stuff from their blogs to r.o or at least take responsibility to update it. [14:52] I think for Redmine-1.0 it would be nice to have a new and improved theme...(just a thought) [14:52] Btw, for the install document(s) [14:52] I think that instead of having a single document that tries to cover the differences between versions [14:52] There should be separate documents for versions [14:52] meineerde: ah yea. Might be good to reach out to the blogger and see if they would be willing to port their docs to the wiki. [14:52] rchady: +1 for wiki:ThemeSP [14:52] meineerde: rchady: wiki:ThemeSP is http://www.redmine.org/projects/redmine/wiki/ThemeSP "Redmine - ThemeSP - Redmine" [14:52] (but not for 1.0) [14:52] rchady: I think some kind of theming in 1.0 would be nice. [14:53] rchady: 1.0 themes are probably too late [14:53] rchady: But so would lots of other things... [14:53] ferggo: Redmine has themes already (since 0.8 I think) [14:53] edavis10: I know. I meant more out-of-the-box options. [14:53] rchady: so a "Install Redmine 0.9" "Install Redmine 1.0" pages? [14:53] Yes [14:54] Otherwise there is too much clutter for it to be clear [14:54] I've noticed that fairly frequently from questions in #redmine [14:54] ferggo: the UX team has talked about improving theme support a bit. It will be brought up for 1.1 features very soon. [14:54] Khalsa: thoughts on per version install docs (above ^^^) [14:54] I vote no [14:54] Way too much headache to maintain for multiple versions [14:55] doc team already decided to only support latest version, with newest docs centered around 1.0+ [14:55] Khalsa: what about for the current version and past version (so 0.9 and 0.8 right now. 1.0 and 0.9 soon) [14:55] I don't think, the version differ much. Only the required gem versions... [14:55] Khalsa: or wait.. [14:55] personally I would think it would be fairly easy to support [14:55] You write 1 good document for the current version [14:56] nevermind, I thought Mischa archived the old 0.8 install docs when 0.9 was released. [14:56] When a new version comes out with any changes, you move the old document to its version number, modify the new one as the current [14:56] So it's more of doing a final edit on the old install docs and then copying it to an archive? [14:57] Yeah [14:57] Would there ever be a reason to install an old version? [14:57] SAme goes for differences in databases, instead of inlining both parts in a single document, put in a link to the mysql info, sqlite info, postgres info, etc [14:57] I guess if you wanted to install a compatible version with an archived database or something... [14:57] It cleans things up a lot and allows useres to select only the pieces that matter to them [14:57] rather than trying to filter [14:58] ferggo: older docs would be helpful for older installs. Like if Debian only has 0.8 in it's packages and you need to setup 0.8 to test something. [14:59] brb [14:59] rchady: sounds like you need to be part of the Documentation team. These are good ideas. [14:59] edavis10: Ah, I didn't know redmine had packages. [14:59] rchady: what edavis10 said [14:59] edavis10, I have a lot of experience in customer experience(s) [14:59] ferggo: we're in Debian and I think in Ubuntu now. [14:59] ferggo: would like to get into others too [14:59] I know what works, I just hate actually DOING it :) [14:59] (side note: I've stopped supporting Debian repo/packages on all my other proejcts) [14:59] I have lots of ideas for improvements, just not the time to do them on my own [14:59] hmm, one could even use many imports and combine various parts into specific guides. [14:59] edavis10: So you just apt-get install redmine and, what, it unpacks into a directory that you point a web server at? [14:59] ok, brb [15:00] meineerde: good idea... [15:00] ferggo: dunno, Debian changed a bit in how Redmine works due to their Ruby/Rails versions. [15:00] We are about out of time now [15:00] ferggo: they backprted redmine to rails 2.2 and somehow added multi-site support [15:02] Thank you for coming everyone, it's been a great meeting. [15:02] meineerde: More power to them I guess, but that seems like more work than actually just installing it from source. [15:02] I'm adding some notes to the Wiki page, feel free to add your own wiki:TeamLeadMeeting2 [15:02] edavis10: wiki:TeamLeadMeeting2 is http://www.redmine.org/projects/redmine/wiki/TeamLeadMeeting2 "Redmine - TeamLeadMeeting2 - Redmine" [15:03] edavis10: Do you know, if it possible to run the redmine tests in parallel? [15:03] Action: meineerde got seven bored cores [15:04] meineerde: yes, parallel_tests works for me [15:04] Action: edavis10 has only 4 cores [15:05] I've tried to get hydra to work but it's failing. It lets you run workers over SSH.... e.g. distributed tests over internal network. [15:05] Action: edavis10 would love to spin up EC2 instances to run Redmine tests... [15:06] we have some unused servers in the office. wanted to turn them into test/ci slaves if I find some time. [15:06] exactly [15:07] Back to #redmine for me [15:30] rchady (rchady@flotsam.chady.org) left #redmine-dev. [15:59] allesmueller (allesmuel@unixboard/users/allesmueller) left #redmine-dev. [16:06] AlekSi (AlekSi@star.mlzone.ru) left #redmine-dev. [16:37] So when I'm ready to submit a patch, do I just make it with something like "svn/git diff > issueID.patch" ? [16:40] ferggo: yes. (best to ask in #redmine now though) [17:18] AlekSi (~AlekSi@star.mlzone.ru) joined #redmine-dev. [17:18] AlekSi (AlekSi@star.mlzone.ru) left #redmine-dev. [18:55] Topic changed on #redmine-dev by edavis10!edavis@theadmin.org: Information about dev meetings is at http://www.redmine.org/wiki/redmine/DevMeetings [19:51] ferggo (42a1f8ca@gateway/web/freenode/ip.66.161.248.202) left irc: Ping timeout: 252 seconds