Chat Meetings/Log 20090729

Openbravo Product development meeting chat log - 29th of July 2009 11.30 GMT

[11:32] < pjuvara> Hi everybody
[11:32] < pjuvara> we will be starting the product development meeting in 1 minute.
[11:34] < pjuvara> Hi everybody
[11:34] < pjuvara> let's start today's product development team meeting. Today we will cover a status update on ongoing tasks so we should be able to fit the meeting into 60 minutes.
[11:34] < pjuvara> The topics on the agenda are:
[11:34] < pjuvara> 1) Status of existing ERP releases
[11:34] < pjuvara> 2) Current projects
[11:34] < pjuvara> 3) POS status
[11:34] < pjuvara> 4) Q&A
[11:35] < pjuvara> Let's start with the first topic: status of existing ERP releases.
[11:35] < pjuvara> As usual, let's start with some statistics...
[11:35] < pjuvara> The total defects, including those reported agains pi or main, has increased a lot since the last meeting and in particular for the past few days.
[11:35] < pjuvara> Compared to the last IRC meeting, this number has gone up by a scary 23% and we now have a total of 380, with a breakdown of:
[11:35] < pjuvara> * 2 critical
[11:35] < pjuvara> * 91 major
[11:35] < pjuvara> * 233 minor
[11:35] < pjuvara> * 54 trivial
[11:35] < pjuvara> Two weeks ago, I mentioned light at the end of the tunnel and I would like to confirm that statement now.
[11:36] < pjuvara> Looking into more details into these numbers, however, they are not as bad as they look on the surface. Quite the opposite: they could even be good.
[11:36] < pjuvara> As I said, the major spike happened over the past week when we went from 320 to 380.
[11:36] < pjuvara> During this week, the major source of defect has been QA that logged 55 defects in the past week and a half; another 33 defects were logged internally by developers.
[11:36] < psarobe> pjuvara, as we have discuss only 1 critical
[11:36] < pjuvara> By contrast support only reported 6 and the community 9 defects.
[11:37] < pjuvara> psarobe: you are right. the numbers above are from this morning at 7am
[11:37] < pjuvara> 7am cet
[11:37] < pjuvara> The volume of defects reported by community and support s less than usual and, in fact, over the past 3 months, the trend of issues reported by users (support and community) has been consistently going down and went from 22 per week 3 months to 10 per week last week.
[11:38] < pjuvara> Additionally, the most significant increase in defects is among minor and trivial issues. Critical and major have increased as well but not as much.
[11:38] < psarobe> pjuvara, from QA side those 55 defect are mostly minor or trivial bugs
[11:38] < pjuvara> yes
[11:38] < pjuvara> My conclusion therefore is that the product, as perceived by end users, is stabilizing and that our QA team is doing an increasingly good job at finding more and more detailed issues.
[11:39] < pjuvara> Hence good news :)
[11:39] < pjuvara> Let's look at the two critical issues (as of this morning):
[11:39] < pjuvara> * 10095: Not able to apply 250MP3 in 250MP2 community appliance. An error shows up
[11:39] < pjuvara> * 10096: Not able to apply 250MP3.obx file in 250MP2 community appliance
[11:39] < pjuvara> Both of them are assigned to marvintm.
[11:39] < pjuvara> marvintm: can you please provide an update?
[11:39] < marvintm> yes
[11:40] < marvintm> i'm currently working on 10096
[11:40] < marvintm> i'm currently testing the fix
[11:40] < marvintm> it should be ready by this morning
[11:40] < marvintm> i haven't taken a look at 10095 yet
[11:40] < pjuvara> great
[11:41] < pjuvara> psarobe: can you comment on the nature of 10095?
[11:41] < psarobe> sure
[11:41] < psarobe> right now there is a new ant task to create an obx file for just core
[11:41] < psarobe> package.core
[11:42] < psarobe> if you use that to create the obx file, then when applying to 250MP2 the process gets stuck at some point
[11:42] < psarobe> but if you create the obx file manually then it doesn't
[11:43] < iciordia> alostale should take care of this one
[11:43] < pjuvara> so it looks like that ant task is broken and should not be used, right?
[11:43] < psarobe> here the point is that I'm not sure how RM creates the obx
[11:43] < iciordia> alostale: did you test it?
[11:43] < psarobe> I have sent an email to priya asking this
[11:43] < pjuvara> I think this is not a showstopper to release MP3 (we can create the obx manually) but it should be fixed urgently anyway.
[11:44] < alostale> iciordia, when i developed the task i tested it without problem
[11:45] < pjuvara> OK.
[11:45] < pjuvara> let's move on.
[11:45] < psarobe> I will assing the bug to alostale
[11:45] < pjuvara> regardless of severity, we should work on defects in order of priority and we have been changing a bit the policy to decide which defects are handled with immediate priority so that that number remains manageable.
[11:45] < pjuvara> As of this morning, we had:
[11:45] < pjuvara> * 5 immediate
[11:45] < pjuvara> * 30 urgent
[11:45] < pjuvara> * 45 high
[11:45] < pjuvara> * 212 normal
[11:45] < pjuvara> * 79 low
[11:45] < pjuvara> * 9 none
[11:46] < pjuvara> So the policy change seem to be effective as the number of immediate priorities has gone down quite a bit.
[11:46] < pjuvara> Congratulations to all of you who worked on immediate issues!
[11:47] < pjuvara> Now, we have a handful of them that are not making the SLA or are at risk:
[11:47] < pjuvara> * 9319 and its backport 9491: Manufacturing Plan always creates requisitions - assigned to rafaroda and overdue.
[11:47] < pjuvara> rafaroda: can you please give an update?
[11:47] < rafaroda> yes
[11:47] < rafaroda> I'm working on it and hope to finish it by the end of the week
[11:49] < pjuvara> thanks
[11:49] < pjuvara> With regards to backports, we now have a total of 51, which is an increase compared with 2 weeks ago (+7). Again, I think we could abandon many of them because out of 51 only 6 of them are requested by professional subscription customers.
[11:49] < pjuvara> In terms of maintenance packs, we released 2.40 MP7 to professional subscription customers on July 17th, so we continue our winning streak of on time release of MPs.
[11:50] < pjuvara> We are now working on 2.50 MP3 (community release), scheduled to be released by July 31st.
[11:50] < pjuvara> psarobe: how is that going, besides the two issues above?
[11:50] < priyam> psarobe: obx is generated manually, replied ur mail
[11:50] < psarobe> thanks priyam
[11:51] < psarobe> things were going on time now a little bit tight
[11:51] < pjuvara> what is outstanding?
[11:52] < psarobe> ell, we have to test the upgrading process and for that we need the obx file
[11:52] < psarobe> we test it updating from 250MP2 community appliance
[11:52] < psarobe> then from an OPS
[11:53] < psarobe> and after that we have to test 250MP3 community appliance before publishing
[11:53] < psarobe> :)
[11:53] < pjuvara> OK. Thanks.
[11:54] < psarobe> a little bit tight, but we could make depending on marvintm and RM
[11:54] < pjuvara> The next pack will be 2.35 MP14 (professional subscription only), scheduled to freeze on August 1st and release by August 10th.
[11:54] < pjuvara> Let's move to the next topic. We have a number of new project going on and I would like to ask developers to give a quick update on them to the Community.
[11:54] < gnuyoga> psarobe: current sprint priyam is asigned just for MP release. any support you require lets us know, thx
[11:55] < pjuvara> * Modularizing the Post procedures
[11:55] < pjuvara> * Inter-company invoicing
[11:55] < pjuvara> * Mass Invoicing
[11:55] < pjuvara> * HCM
[11:55] < pjuvara> * Apparel product support
[11:55] < pjuvara> * Support for different numeric formats
[11:55] < pjuvara> * Performance improvements
[11:55] < pjuvara> * Spanish Professional Localization Pack: Invoice Register Book and 347 report
[11:55] < pjuvara> * Booking control
[11:55] < pjuvara> gorkaion: can you please give an update on the first 2?
[11:55] < gorkaion> I pushed yesterday the development, now I'm fixing some bugs
[11:56] < pjuvara> is it in PI?
[11:56] < gorkaion> yes
[11:56] < pjuvara> Cool!
[11:57] < pjuvara> The first project (Modularizing the Post procedures) is really interesting because it will allow our community to extend Invoice Post and Order Post in a much easier way.
[11:57] < pjuvara> It is small but very significant.
[11:58] < pjuvara> The second one (Intercompany Invoices) leverages it.
[11:58] < gorkaion> I'll update the documentation in the wiki the next days
[11:58] < pjuvara> Thanks.
[11:58] < psarobe> Suresh, any update on intercompany invoicing?
[11:59] < Suresh> I am about to finish preparing the test cases
[11:59] < Suresh> Also i am waiting for Ainhoa review comments on test cases..
[12:00] < pjuvara> Who can speak about Mass Invoicing?
[12:00] < apagola> I have already integrated intercompany invoices with Modularizing Post procedures
[12:00] < apagola> and it is working on Postgresql.
[12:01] < apagola> I will test in on Oracle soon so QA can start testing.
[12:01] < psarobe> ok apagola please let QA know when everything is ready to start testing
[12:01] < psarobe> apagola, thanks
[12:02] < pjuvara> katratxo, iciordia, xxDaViDxx: one of you want to talk about Mass Invoicing?
[12:02] < iciordia> I will do
[12:02] < katratxo> ok
[12:02] < iciordia> On this project code is complete, yesterday we show it to QA
[12:03] < iciordia> there are some issues already known, and for sure some others coming
[12:03] < iciordia> but in my opinion very small things
[12:04] < iciordia> We plan to put it in the customer testing environment at the end of this week
[12:04] < iciordia> so it will help to do testing as well
[12:04] < iciordia> in any case, the module will not be released till September
[12:05] < iciordia> because it depends on changes in pi that will be released with MP4
[12:05] < psarobe> 1st september, 30th september?
[12:05] < iciordia> so we will do an ad-hoc core obx file for the customer
[12:05] < iciordia> September 1st
[12:05] < iciordia> (just after MP4 is released)
[12:06] < iciordia> but QA process needs to be done much earlier
[12:06] < iciordia> because the customer will go to production before that date
[12:06] < iciordia> so we will use an alpha release (and an ad-hoc core update) to release it to the customer
[12:07] < iciordia> and thats all
[12:07] < pjuvara> Can you also talk about Apparel Product Support?
[12:07] < iciordia> sure
[12:07] < psarobe> iciordia, it would help us a lot to know what the developers have tested before continue us
[12:07] < iciordia> Apparel product support is split into three main features: prod.tech.spec, entering document lines and managing product prices and cost
[12:09] < iciordia> The first is done (just code complete), second will be finished (hopefully) by tomorrow and third will happen next week
[12:09] < iciordia> we are tight on this project, and QA should prioritize testing on this one because the customer plans to put it in production by August 10th
[12:10] < pjuvara> Thanks.
[12:10] < iciordia> (we will use similar approach to release it)
[12:10] < pjuvara> apagola: an update on HCM?
[12:11] < apagola> No progress in the moment (since working on Intercompany) but the plan is to finnish the developement this week
[12:11] < apagola> sorry, next week.
[12:11] < pjuvara> thanks
[12:12] < pjuvara> Who wants to talk about Support for different numeric formats?
[12:12] < iciordia> Ivan, can you please do it?
[12:12] < katratxo> iciordia: yes
[12:13] < katratxo> i'm finishig the functional spec to complete the QA test plan
[12:13] < katratxo> some of the static front-end and back-end test are done
[12:14] < katratxo> *tests ... so after finishing the functional spec, i'll work in the integration of this changes on wad
[12:14] < katratxo> that's all
[12:14] < pjuvara> thanks
[12:14] < plujan> from QA side, test plan for Dynamic Numeric Formats is 50% complete. Still working on the test cases. We are on time for starting the QA cycle when development finish
[12:15] < pjuvara> We also made a number of performance improvements that I understand are part of 2.50 MP3.
[12:15] < pjuvara> huehner: can you please comment?
[12:16] < huehner> pjuvara: sure
[12:16] < huehner> The improvements delivered in mp3 are the already finished parts of my ongoing performance work: they include speeding up i.e. selectors with many products / bpartners
[12:17] < huehner> ongoing right now in performance: paged datagrid (limit scrollable range to 10.000 records) and provide some new preivous/next page buttons (in all datagrids)
[12:17] < huehner> prototype is functionally complete. next steps finalize/develop ui with Rob and David
[12:17] < huehner> then finish implementation
[12:17] < huehner> additionally i am working with rm-team to include performance testing in the nightly build runs
[12:18] < huehner> which 2.40 tests being done first (as they already exist)
[12:18] < huehner> that'l all
[12:19] < pjuvara> thanks,
[12:19] < pjuvara> next would be an update on the Spanish Localization Pack.
[12:19] < pjuvara> psanjuan: can you please take this?
[12:19] < vmromanos> pjuvara, I'll do it
[12:19] < pjuvara> ok
[12:19] < vmromanos> Invoice Register Book: we are currently working on it. Great progress there, a lot of functionality is already finished, however we're a bit delayed compared to our initial schedule...
[12:20] < vmromanos> I think it will be completed (including the required deep testing) by the end of the next week
[12:20] < pjuvara> marvintm: good job on 10096!
[12:20] < vmromanos> 347 report: The draft functional specifications is completed. We're working on the technical documentation
[12:20] < marvintm> :)
[12:20] < vmromanos> that's all
[12:20] < pjuvara> thanks.
[12:21] < pjuvara> who can speak about Booking Control?
[12:21] < amedio> I'll do
[12:21] < amedio> We are quite close to finalize it
[12:21] < amedio> there are some issues with the UI for some tabs
[12:21] < amedio> And a really simple proces is being finished now
[12:22] < amedio> I will have a demonstration from the team today
[12:22] < amedio> I hope to have something showable tomorow
[12:22] < pjuvara> Cool! Good news on all fronts today :)
[12:22] < amedio> but some tasks related to registering code in forge are pending
[12:23] < amedio> the UI needs to be fixed
[12:23] < amedio> because is a key point when demonstrating anything to end customers
[12:23] < amedio> thats all
[12:23] < pjuvara> Thanks.
[12:23] < pjuvara> Finally, I would like an update on the Continuous Integration framework.
[12:23] < pjuvara> gnuyoga: can you please give an update on the Continuous Integration framework?
[12:24] < gnuyoga> pjuvara: Yes
[12:24] < gnuyoga> we have scheduled to demo new smoke test system to QA this week
[12:25] < gnuyoga> we have decided include performance testing for 2.40 and design of performance testing for 2.50
[12:25] < gnuyoga> that's all from our side this week
[12:25] < gnuyoga> ah one more thing
[12:25] < plujan> gnuyoga: I am looking in builds page that all 2.3x smoke failed, do you know why?
[12:26] < gnuyoga> 2.3x is a real failure and is reported
[12:27] < gnuyoga> we have decided to write a Project Plan for CI, and would like to get inputs from all the team ... will perhaps write a mail in staff.engineering for the same
[12:27] < pjuvara> good initiative.
[12:27] < pjuvara> all: please write emails for what you would like CI to do.
[12:28] < gnuyoga> intitial doc is here http://wiki.openbravo.com/wiki/Release_Management/Continuous_Integration_Vision
[12:28] < gnuyoga> and the theme is I Build So Consistently
[12:28] < gnuyoga> I - Identify, what to automate
[12:28] < plujan> gnuyoga: sorry, what issue you said it was reported? both oracle and postgres context have different errors
[12:28] < gnuyoga> B - Build, use apache ant/maven, etc
[12:28] < gnuyoga> S - Share, use version control
[12:28] < gnuyoga> C - Continuous, make sure automated process is run with every SCM changes
[12:29] < pjuvara> Cute.
[12:29] < gnuyoga> plujan: oracle fails at E_06_CreateRemittance.testCreateRemittance[0] this for oracle
[12:30] < gnuyoga> plujan: pgsql fails at E_07_CreateBankStatement.testCreateBankStatement[0]
[12:30] < gnuyoga> pjuvara: Yes
[12:30] < plujan> ok, so both are real errors and were reported?
[12:30] < gnuyoga> plujan: i can ask priyam to get in touch to sync up with you on this issues
[12:30] < pjuvara> Let's move to the last topic on the agenda: POS.
[12:30] < pjuvara> adrianromero: can you please take the lead?
[12:30] < plujan> gnuyoga: ok
[12:30] < adrianromero> yes
[12:31] < adrianromero> For POS the status of issues is the following:
[12:31] < adrianromero> * Major bugs 6 (+1)
[12:31] < adrianromero> * Minor bugs 16 (+1)
[12:31] < adrianromero> And the chart statistics for issues is published here:
[12:31] < adrianromero> http://spreadsheets.google.com/pub?key=pWEbJ3VuNci0-7pcXvhrLSQ&oid=1&output=image
[12:31] < adrianromero> And the chart statistics for forum messages is published here:
[12:32] < adrianromero> http://spreadsheets.google.com/pub?key=pWEbJ3VuNci0-7pcXvhrLSQ&oid=5&output=image
[12:32] < adrianromero> That is all from POS
[12:32] < pjuvara> Thanks!
[12:32] < pjuvara> Anything else?
[12:33] < pnuding> A quick comment about the Forge
[12:33] < pnuding> the new homepage design has gone live
[12:34] < pnuding> so some of the annoying usability issues when looking for projects are now belonging to the past
[12:34] < pnuding> and I will be blogging about this in the next days
[12:34] < katratxo> need to refresh your browser cache, otherwise you get weird links positioning
[12:34] < pjuvara> Great!
[12:34] < pjuvara> I had not noticed it yet. Fantastic news!
[12:34] < pnuding> good note, thanks katratxo
[12:35] < katratxo> np
[12:35] < amedio> ciao
[12:36] < dmezentse1> I would also like to mention that OB Demo is upgraded to the 2.50 MP2. It was a question regarding this last meeting.
[12:36] < iciordia> Cool!
[12:36] < gnuyoga> harpreet: is the demo update complete or partial ?
[12:37] < harpreet> gnuyoga: it is complete.
[12:37] < gnuyoga> harpreet: perfect !
[12:38] < gnuyoga> plujan: 2.3x oracle issue here https://issues.openbravo.com/view.php?id=9842
[12:38] < iciordia> These are very good news, we had had some problems with bugs reported on our live demo
[12:39] < plujan> gnuyoga: that's an error in QA scripts
[12:39] < gnuyoga> plujan: k
[12:40] < gnuyoga> plujan: any effor to fix the issue soon ?
[12:41] < plujan> we will modify the build.xml so no error will be triggered next hudson smoke
[12:41] < plujan> it will be very handy if an email were sent on a failure
[12:42] < plujan> since now i have no notice of this error till I open the builds page
[12:43] < plujan> and defined process for fixing this things is started when an emial from hudson is received
[12:43] < gnuyoga> plujan: sure, i will add that
[12:44] < plujan> thanks. I will ask Leo to modify the build
[12:44] < gnuyoga> plujan: one more idea that came to me is to pass th build if 95% of tests is sucess .. what do u think ?
[12:44] < plujan> how do you plan to measure completion?
[12:45] < gnuyoga> no of sucessful tests
[12:45] < gnuyoga> since its unit test adn we have a count of how many test ran
[12:46] < plujan> yes, but note that you will always have zero or one failures
[12:46] < plujan> I mean, number of failed tests is always 0 or 1
[12:46] < gnuyoga> ah okay, i will try that feature and let u know
[12:46] < plujan> since once a failure is detected, rest of test cases are not executed
[12:46] < gnuyoga> u back from vacation ?
[12:46] < plujan> so 95% is not a good metric
[12:47] < gnuyoga> i mean if it ran 60 test and 55 was sucessful ... something like that
[12:48] < gnuyoga> s/ran/has/
[12:48] < plujan> that will never happen
[12:48] < gnuyoga> k
[12:48] < plujan> at the first error, smoke will stop
[12:48] < plujan> so you will have 54 of 55
[12:48] < plujan> never 60 of 55
[12:48] < plujan> so a 95% simply has no sense
[12:49] < gnuyoga> ah okay,,, that will be tough to decide then :-(
[12:49] < plujan> I will let a binary decision. It passes or not. 100% is success, otherwise is a fail
[12:49] < plujan> note that except 2.3x, other branches are performing quite well
[12:50] < gnuyoga> Sure, let take that appraoch (100% is success)
[12:50] < gnuyoga> (other branches) are good
[12:51] < plujan> regarding 2.3x, a temporary fix is now ready. So next build should be successful although less test cases will be executed
[12:52] < gnuyoga> ah okay
[12:53] < katratxo> @rm guys .. the redirection script on demo.openbravo.com sometimes redirects you to demo1.openbravo.com .. and demo1 is down
[12:53] < gnuyoga> katratxo: will check that
[12:53] < katratxo> ok

Retrieved from "http://wiki.openbravo.com/wiki/Chat_Meetings/Log_20090729"

This page has been accessed 56 times. This page was last modified 21:28, 1 August 2009. Content is available under Creative Commons Attribution-ShareAlike 2.5 Spain License.

Category: Community