PMC QA Meeting 20100317
Date: 2010-03-17
Time: 8AM GMT
Venue: irc #adempiere-team
Support Spreadsheet: Adempiere PMC QA
Chat times in GMT-5
(03:14:22) interopen: Hi Carlos, hi Heng sin and Trifon
(03:14:29) CarlosRuiz: Hi Ivan
(03:15:02) hengsin: Hi Ivan
(03:15:56) interopen: Here is an agenda we can follow:
(03:16:11) interopen: 1. CI server questions
(03:16:31) interopen: 2. bugs testing organization
(03:16:53) interopen: 3. Review and progress on task list
(03:17:42) CarlosRuiz: ok
(03:17:43) interopen: i have been working on clarify the design of the CI server this week and have some issues want to see
(03:18:54) interopen: during the CI process, we have created several scripts to automate it
(03:19:16) interopen: one of them is related to database migration, and here we have two working ways
(03:19:30) interopen: or update the last migration scripts in SVN
(03:20:00) interopen: or update all revision versions of this migration scripts in SVN
(03:20:54) interopen: as we are not clear how you manage the migration scripts update in the case one developer is not using the last revision
(03:21:04) trifon: interopen: what is the problem?
(03:21:25) trifon: sorry it is not clear what problem you faced?
(03:21:35) interopen: ok, let me try to clarify it
(03:22:42) CarlosRuiz: Iván - just sent you an e-mail that maybe can help you - where it's described how testadempiere is set up
(03:23:16) CarlosRuiz: in testadempiere hengsin did a mechanism to run all the migration scripts from an ant build.xml file
(03:23:45) interopen: all migration scripts in all SNV revisions?
(03:24:31) CarlosRuiz: nope - you take the latest seed from data/seed directory
(03:24:31) CarlosRuiz: and apply the migration scripts from [version]-trunk directory
(03:25:10) interopen: i mean if one developer use revision 1260 to create his migration script and another use 1261 when the second updates the svn will delete second developer migration
(03:25:59) CarlosRuiz: migration scripts are numbered - you need to apply all of them on the specified order
(03:26:39) CarlosRuiz: so, in revision 1260 a developer will contribute for example the script 657_BLABLABLA.sql
(03:26:39) CarlosRuiz: with revision 1261 another developer will contribute the script 658_BLABLA.sql
(03:26:45) interopen: ok, so is the same aproach we are using in the script we created
(03:27:37) interopen: ok, clear then
(03:27:58) interopen: that is what we didn't have clear, and that is how you solve this issue
(03:28:12) interopen: so there is no need to update all revisions with CI
(03:29:05) CarlosRuiz: I think I'm not understanding your problem
(03:30:14) interopen: every developer create a numbered script as you explain this way there is no conflict between script commits
(03:30:39) interopen: i had not clear this way you arrange to do it
(03:31:05) CarlosRuiz: ok
(03:31:06) interopen: so that is why we update the database on all migration script revisions
(03:32:19) interopen: Carlos: thanks for the email, we review it and compare it with our scripts
(03:32:20) CarlosRuiz: ah, I see, it would be needed just those revisions that write on [version]-trunk folder
(03:33:26) interopen: that was related to my second question, as we have already the POC for the CI we wanted to contribute the scripts
(03:33:37) interopen: how to arrange it?
(03:33:50) interopen: follow with a documentation in the wiki
(03:34:53) CarlosRuiz: if you need to download continuously those scripts (maintain them in adempiere) they can be added to adempiere repository
(03:35:11) CarlosRuiz: if you are going to maintain them by yourself then you can add them to a contributions folder
(03:35:42) CarlosRuiz: hmm - didn't sound right :-) in both you can maintain the versions in adempiere
(03:36:16) CarlosRuiz: in other words - whatever you prefer - I think a folder in contributions can be good - but if you want the scripts to be in core we can make space for them in a special folder CI or something like that
(03:36:57) interopen: i think a folder in contributions is fine
(03:37:10) interopen: and i can maintain it there
(03:37:15) CarlosRuiz: do you have svn permissions?
(03:37:27) interopen: no, not have
(03:37:36) CarlosRuiz: do you want? :-)
(03:38:19) interopen: if is a way to share the scripts so others can review it and test it, yes
(03:38:51) CarlosRuiz: done - sourceforge interopen user have permissions
(03:38:59) CarlosRuiz: feel free to create your contributions folder and maintain it there
(03:39:13) interopen: ok, i arrange it later
(03:39:37) interopen: also i see there is no folder for China localization, can i arrange one?
(03:40:34) CarlosRuiz: yep
(03:40:44) interopen: ok, move to point 2.
(03:41:37) interopen: i have been following the bugs triage this week, and see Mark organize it
(03:42:17) interopen: Carlos: if you know Mark can you ask him if he want to join QA team as i see he also did a presentation about it in last Adempiere conference
(03:42:57) CarlosRuiz: sure - I'll send him an e-mail copying you
(03:43:16) interopen: also i notice all bugs are tested agains testadempiere.com, what version is using there, release or trunk (experimental)?
(03:43:35) interopen: thanks, Carlos
(03:43:38) CarlosRuiz: currently is pointing to release
(03:44:00) hengsin: Ivan: any progress on sahia ?
(03:44:29) interopen: yes, quite a lot, we are going to add documentation in the wiki today and tomorrow
(03:44:41) interopen: just need to finish the POC with webui, all documented
(03:44:59) interopen: there was some issues with Xvfb in the test server
(03:45:26) interopen: we are focusing on finish first Sahi and later Selenium
(03:45:33) hengsin: thats great, we need regresssion test ASAP
(03:46:44) hengsin: Ivan, if you can, please publish the soonest you can. I would like to look into this but I don't want to duplicate the effort if possible.
(03:47:53) interopen: yes, is on the way...
(03:48:08) interopen: several documents, also about the CI server i review before
(03:48:47) interopen: and some documents about the design of the CI-test server, so the concepts are clear for those who want to work with QA group
(03:49:28) interopen: i want to have those finish before any talk in the forums, so the understanding is faster
(03:51:04) interopen: this days we have spend quite a time on research and that takes time, but now concepts start to be more clear
(03:52:00) CarlosRuiz: yep - thanks about that
(03:54:20) CarlosRuiz: Ivan - 7 minutes to go - any other topic?
(03:54:24) interopen: 3. on review task list
(03:54:33) CarlosRuiz: ok :-)
(03:54:38) interopen: i will reorganize it a little
(03:54:58) CarlosRuiz: ok - try to not change the original #
(03:55:21) CarlosRuiz: because in the published chat meetings there can be references to #
(03:55:29) interopen: you mean the numbering
(03:55:36) CarlosRuiz: yep
(03:55:52) interopen: ok, i not change it, but want to change some descriptions to adapt them to what we are working now on
(03:56:15) CarlosRuiz: good
(03:57:02) viola [~viola@p4FE2F278.dip.t-dialin.net] entered the channel.
(03:58:15) interopen: as i see now some concepts more clear
(03:58:57) interopen: i think better i change it and we review it in next meeting
(03:59:26) CarlosRuiz: sure, next meeting is march 24
(03:59:28) interopen: as now my focus is complete the basic tasks and document them for ask community for help and review
(03:59:44) interopen: yes, 24
(04:00:55) interopen: Thanks all for the help
(04:01:05) CarlosRuiz: thanks to you
(04:01:48) interopen: bye Carlos
(04:02:00) CarlosRuiz: bye Ivan, bye to all
