Chat Meetings/Log 20090506

Product development meeting - 6th of May 2009 at 11:30 UTC+1

[11:28] < psanjuan> hi
[11:28] < shor123> hi psanjuan
[11:29] < jmas> hi
[11:30] < huehner> hi all
[11:30] < raejohnston> Hi everyone
[11:31] < shor123> hi huehner and raejohnston
[11:31] < pjuvara> Hi everybody
[11:31] < pjuvara> we will start today's product development team meeting in 2 minutes.
[11:33] < shor123> @mtaal/gorkaion now i am confused. i created my own attribute set (see http://pastebin.com/m28bfa10a) and now i am seeing AttributeSetInstance with id 1000000 not found
[11:34] < gorkaion> shor123: it is different the attributeset and the attributesetinstance
[11:34] < gorkaion> you should also create an instance of that attributeset
[11:34] < mtaal> also when creating data through rest you have to check the return xml to see what the id of the inserted record is
[11:35] < shor123> mtaal: poster returned: <log>Inserted entity Standard, with import id: 1000000 Updated 0 business objects, Inserted 1 business objects </log> <inserted>
[11:35] < shor123> mtaal: so it should be the right id
[11:36] < mtaal> yes, it tries to keep the id
[11:36] < shor123> gorkaion: erm what is the difference between them?
[11:36] < pjuvara> We will let the current conversation end and then start the meeting. A few more minutes...
[11:37] < shor123> pjuvara: your meeting is here?
[11:38] < katratxo> shor123: yes
[11:38] < iarwain> shor123: http://article.gmane.org/gmane.comp.erp.openbravo.devel/255
[11:38] < shor123> okay... then tell me when i should keep my mout shut :D
[11:38] < pjuvara> Take your time.
[11:40] < pjuvara> OK. Let's start.
[11:40] < pjuvara> Today we will cover a status update on ongoing tasks so we should be able to fit the meeting into 60 minutes.
[11:40] < pjuvara> The topics on the agenda are:
[11:40] < pjuvara> 1) Status of existing ERP releases
[11:40] < pjuvara> 2) Clean up activities
[11:40] < pjuvara> 3) POS 2.30 status
[11:40] < pjuvara> 4) Q&A
[11:40] < pjuvara> Let's start with the first topic: status of existing ERP releases.
[11:41] < pjuvara> First the numbers...
[11:41] < pjuvara> The overall backlog of defects affecting production releases has gone down quite a bit since the last community meeting.
[11:41] < pjuvara> We are now are at a total of 94 defects (-56 compared to the last meeting) with the following breakdown:
[11:41] < pjuvara> * 0 critical (-)
[11:41] < pjuvara> * 21 major (-31)
[11:41] < pjuvara> * 63 minor (-10)
[11:41] < pjuvara> * 10 trivial (-4)
[11:41] < pjuvara> In terms of total defects, including those reported agains pi or main, we have 190, with a breakdown of:
[11:41] < pjuvara> * 0 critical
[11:41] < pjuvara> * 41 major
[11:41] < pjuvara> * 134 minor
[11:41] < pjuvara> * 15 trivial
[11:42] < pjuvara> Now, regardless of severity, I remind you that we should work on defects in order of priority.
[11:42] < pjuvara> In this respect, we have:
[11:42] < pjuvara> * 6 immediate
[11:42] < pjuvara> * 17 urgent
[11:42] < pjuvara> * 14 high
[11:42] < pjuvara> * 103 normal
[11:42] < pjuvara> * 39 low
[11:42] < pjuvara> * 11 none
[11:42] < pjuvara> With regards to backports, we now have a total of 55 (-9) with a breakdown by branch of:
[11:42] < pjuvara> * 8 for 2.3x (-)
[11:42] < pjuvara> * 47 for 2.40 (-9)
[11:42] < pjuvara> That was quite a handful of numbers and I will give you a few moments to digest them but, overall, this is great progress.
[11:43] < pjuvara> So... congratulations, everyone!
[11:43] < pjuvara> Now that we have fixed all this stuff, we need to make the fixes available to our users in the form of maintenance packs.
[11:43] < pjuvara> For the community, we are in the process of closing 2.50 MP1, while for professional subscribers we are way overdue with both 2.40 MP4 and 2.35 MP12.
[11:44] < pjuvara> psarobe: can you please give us an update on how 2.50MP1 is going?
[11:44] < psarobe> I would rather if plujan does it instead of me
[11:44] < pjuvara> sure. plujan?
[11:45] < plujan> mp1 candidate (current main) is under testing this week
[11:46] < pjuvara> how is it proceeding?
[11:46] < plujan> we are facing a couple of major issues but we could manage to continue
[11:46] < plujan> current status is: bug revision is 60% done
[11:47] < plujan> functional smoke test is 80% done
[11:47] < plujan> exploratory test is 40% done
[11:47] < plujan> upgraders test still not started (planned for tomorrow)
[11:47] < psarobe> plujan, smoke test 100% done at this point
[11:47] < pjuvara> Great!
[11:48] < pjuvara> Do you know, on top of your head, how many bug fixes are included in MP1?
[11:48] < psarobe> i hope to finish bug revision today just 25 bugs left
[11:48] < plujan> we are currently on track so we expect to finish for tomorrow so friday release management can start packaging
[11:48] < psarobe> iwould say 190
[11:48] < psarobe> more and less
[11:49] < pjuvara> Fantastic. This is going to be very important for the community.
[11:49] < plujan> since we move all PI to Main is difficult to have bug number
[11:49] < iarwain> pjuvara: Between tag 2.50 and the tip there are 341 changesets. We'd have to see how many are related to issues.
[11:49] < psarobe> plujan, jejej, but 190 more and less for sure ;)
[11:49] < plujan> but I think psarobe's numbers are correct
[11:50] < pjuvara> plujan: Yes, I know. We need to figure out a better way of getting this information our of issues.openbravo.com.
[11:50] < pjuvara> s/our/out
[11:50] < plujan> psarobe: yes, more and less
[11:50] < psarobe> pjuvara, it's easy. Look for the ones that have the flag main
[11:50] < iarwain> a quick grep says 257...
[11:50] < psarobe> plus the ones resolved or closed with the tag 250mp1
[11:52] < pjuvara> All of this is very error prone (and the fact that we cannot agree on the right number demonstrates it). We have a similar issue with the stable repository: I tried and failed to figure out how many fixes are pending release in 2.40 MP4.
[11:52] < pjuvara> OK. Let's move to the next topic: clean up.
[11:53] < iarwain> (on main: hg log --rev 2.50:tip)
[11:54] < pjuvara> With this term we mean a number of pending task that require to be closed before we start the full speed development of 2.60, in order to be productive during the development cycle.
[11:54] < pjuvara> They are:
[11:54] < pjuvara> 1) Documenation:
[11:54] < pjuvara> * Developer's Guide
[11:54] < pjuvara> * Configuration Guide
[11:54] < pjuvara> * Data Sheet
[11:54] < pjuvara> * How to Customize
[11:54] < pjuvara> * Guidelines to develop modules in an upgrade safe manner
[11:54] < pjuvara> * Technical Documentation
[11:54] < pjuvara> 2) Continuous Integration framework
[11:54] < pjuvara> 3) Development Process Definition
[11:54] < pjuvara> We will not be able to review them all in details but I would like to ask for some status update on some of them.
[11:55] < pjuvara> mtaal: can you please give an update on the Developer's Guide?
[11:55] < mtaal> part of the team has just re-started the documentation effort in this sprint after mainly solving bugs
[11:56] < iciordia> Can all people involved in developers guide write here his estimation about pending effort?
[11:56] < pjuvara> are we still on track to complete in the current sprint (by May 12)?
[11:57] < xxDaViDxx> dbaz: 37 hours of pending work
[11:57] < alostale> for me about 30hrs
[11:57] < alostale> plus ad help review
[11:58] < alostale> plus automatic database model document new version
[11:58] < alostale> including pl, etc
[11:58] < mtaal> for me about 20-25 hours
[11:58] < iciordia> for me about 20 hour
[11:58] * huehner about 1-2days
[11:59] < pjuvara> Still committed to complete in the sprint?
[11:59] < mtaal> Ivan?
[11:59] < katratxo> don't know, still have ccc pending issues
[12:00] < mtaal> Ivan has a number of topics assigned to him so there the schedule is tight I assume
[12:00] < mtaal> so afaics the guide will not be finished this sprint, although we are close...
[12:00] < pnuding> and could anyone take over parts from him? (e.g. shu)
[12:00] < mtaal> with finished I mean main writing done, proof read done etc.
[12:00] < xxDaViDxx> on my side, I won't be able to complete within this sprint. We have 24 hours left of work and I have 37 pending
[12:01] < mtaal> I have asked Rachel to do proof reading after we are finished so that will take time to
[12:01] < xxDaViDxx> one of my tasks: "Concepts/UI/Javascript_Utilities" could be done by Stefan perfectly
[12:01] < pjuvara> OK. Please discuss in your daily meetings how to recover to get the maximum out of the sprint. If not everything can be achieved please make sure that the product owner has visibility and control of what is falling out of scope.
[12:02] < mtaal> ok
[12:02] < pjuvara> raejohnston: can you please give an update on the Configuration Guide?
[12:02] < raejohnston> Re the developer's guide - if you have topics that are already finished, it's easier to find 5 minutes to proofread than it is to find a day, so perhaps it is worth me making a start on some finished topics?
[12:03] < mtaal> the how-tos can all be proof read
[12:03] < raejohnston> OK.
[12:03] < raejohnston> Re: the configuration guide, we have a new process in place for dealing with my questions to the development team.
[12:04] < raejohnston> I'm keeping a spreadsheet on google docs and every time I have a question I write it there. Paolo periodically allocates the questions to the right people.
[12:04] < pjuvara> I will allocate some today.
[12:04] < alostale> mtaal, i have to split how to create columns and tables in 2
[12:04] < raejohnston> Hopefully this will speed up the flow of info - so far it is working very well, thanks to those who have already stepped up and answered things.
[12:05] < raejohnston> David Alsasua, sorry to tell you you have a big list coming your way.
[12:05] < mtaal> alostale yep that's true
[12:05] < txasu> no problem
[12:05] < raejohnston> I will be in PNA next week 11th - 15th.
[12:05] < mtaal> I will discuss separately with Rachel in an email
[12:05] < pjuvara> cool.
[12:05] < pjuvara> gnuyoga: can you please give an update on the Continuous Integration framework
[12:07] < gnuyoga> we have integrated database consistency checkin full / incremental build
[12:08] < gnuyoga> smoke test for postgres is done, oracle shoudle be done in coming sprint
[12:08] < gnuyoga> Work in progress: module installation / module integrity / release upgrade sanity test
[12:09] < gnuyoga> Issues: selenium tests are untestable.
[12:09] < iarwain> untestable or unstable?
[12:09] < gnuyoga> typo
[12:09] < gnuyoga> unstable
[12:10] < plujan> what do you mean by unstable?
[12:11] < gnuyoga> priyam / iarwain : u want to give an update to plujan
[12:12] < priyam> unstable is test failure
[12:13] < iarwain> e.g. connections are kept open in selenium. If something changes in the ERP the tests may probably be broken.
[12:14] < iciordia> iarwain: what "connection are kept open in selenium"?
[12:14] < pjuvara> OK. We need to stabilize this. Can the two teams (RM and QA) work together to fix it?
[12:14] < iciordia> means?
[12:14] < gnuyoga> will initiate a email with the problem faced to respective members
[12:15] < pjuvara> Cool.
[12:15] < iarwain> iciordia: there is a selenium process that never dies. This is not a big issue because we can pkill it manually.
[12:15] < iarwain> The other issue is bigger.
[12:16] < gnuyoga> Goal for CI is to produce a usable software of openbravo after every commit and we hope to achieve it soon.
[12:16] < pjuvara> That would be fantastic. The goal should actually be not just usable but "potentially shippable". Usable would be a good starting point.
[12:17] < pjuvara> One last update on "clean up" stuff. pnuding: you please give an update on the Development Process Definition.
[12:17] < gnuyoga> pjuvara: Yes, agreed
[12:19] < pnuding> sorry, got disconnected for a moment
[12:19] < pjuvara> np
[12:19] < pnuding> I still need to update the Wiki with the changes we discussed last week
[12:19] < pjuvara> can you please give an update on the Development Process Definition?
[12:20] < pjuvara> ok.
[12:20] < pnuding> will do this before the end of the week and get back to you
[12:20] < pjuvara> Let's move to the last topic on the agenda: POS.
[12:20] < adrianromero> Hello
[12:20] < pjuvara> adrianromero: can you please give an update on POS 2.30?
[12:21] < adrianromero> Yes
[12:21] < adrianromero> The status for POS is that this week we plan to finish all tasks before the launching of Openbravo POS 2.30
[12:21] < adrianromero> These tasks includes all documentation of new functionalities and testing
[12:21] < adrianromero> The pending bugs for 2.30 are 4 minor bugs
[12:22] < adrianromero> And this is the chart of the evolution of bugs:
[12:22] < adrianromero> http://spreadsheets.google.com/pub?key=pWEbJ3VuNci0-7pcXvhrLSQ&oid=1&output=image
[12:22] < pjuvara> Will we be able to launch on Friday?
[12:22] < adrianromero> Do not think so
[12:23] < adrianromero> we need to create all packages
[12:23] < adrianromero> and update release notes
[12:23] < adrianromero> I think that next week it will be possible.
[12:24] < adrianromero> And this other chart is corresponding to the forums activity:
[12:24] < adrianromero> http://spreadsheets.google.com/pub?key=pWEbJ3VuNci0-7pcXvhrLSQ&oid=5&output=image
[12:25] < adrianromero> That is all from the POS team
[12:25] < pjuvara> Thanks.
[12:25] < pjuvara> Any other question / topic from anybody?
[12:25] -ci-update:#openbravo- erp_devel_pi-full-oracle build fixed (http://builds.openbravo.com/job/erp_devel_pi-full-oracle/58/)
[12:26] < pjuvara> CI in action :)
[12:26] < gnuyoga> pjuvara: YES
[12:27] < pnuding> does this message mean people are fixing issues during the meeting? ;)
[12:27] < mtaal> this full build is done every 4 hours :-)
[12:27] < mtaal> I think
[12:28] < pjuvara> Not really. We hope that they fixed them ahead of time that and that they are giving us their 100% attention. But builds.openbravo.com just completed a successful build.
[12:28] < pnuding> ah ok....
[12:28] < gnuyoga> pnuding: ci does everything automatic ;-)
[12:28] < pjuvara> :)
[12:28] < huehner> pjuvara: one question open
[12:28] < pjuvara> huehner: go ahead.
[12:28] < huehner> pjuvara: we (platform team) did prepare the api compatibility checks (to ensure we do not break some modules when releasing a MP)
[12:29] < huehner> pjuvara: they are not yet integrated bu can be run manually
[12:29] < iciordia> including javascript?
[12:29] < huehner> pjuvara: question is if we ant to do it manually, check and (fix or ack) the violations before releasing mp1)
[12:29] < huehner> iciordia: all parts: model,java,javascript
[12:29] < iciordia> that's great!
[12:29] < pjuvara> yes, that would be a very good thing to do.
[12:29] < pjuvara> I propose that:
[12:30] < huehner> pjuvara: mini summary: model some violations, javascript ok, java some/many
[12:30] < pjuvara> 1) Platform team send out an email to openbravo-development with links to documentation on how to run it so that developers can do this test on their own manually before committing a change
[12:30] < pjuvara> 2) Release management runs this test manually on 2.50 MP1
[12:31] < huehner> pjuvara: the java checks need to be checked/fine-tuned on the way do seperate the public api from the private (potentially unstable) api
[12:31] < pjuvara> 3) Release management integrates this in the CI framework (we are planning a sprint today)
[12:31] < gnuyoga> pjuvara: perhaps we can add a pre-commit hook and do this automatic ?
[12:31] < iciordia> huehner: It was planned to move to private a big number of not needed public members, is it pending?
[12:31] < huehner> pjuvara: 1.) i sent an email with this info to release.management some minutes ago
[12:32] < huehner> iciordia: this is pending
[12:32] < huehner> pjuvara: 2.) + 3.) ok
[12:32] < pjuvara> gnuyoga: adding a pre-commit hook would be great
[12:32] < huehner> pjuvara: gnuyoga i would not do this pre-commit. but just schedule it to be run an email-sent, at least until we have fine tuned the checks and defined the public part
[12:32] < alostale> pjuvara, i'm not sure about this, since we can decide in some cases to have exceptions to the rules
[12:33] < pjuvara> huehner: alostale: good points.
[12:33] < huehner> pjuvara: question if we want to checks and perhaps repair some violations for mp1 or not
[12:33] < pjuvara> Any other questions?
[12:33] < huehner> pjuvara: needs to be checked with qa as it would mean delay + potentially changes to main
[12:34] < pjuvara> huehner: yes, but the test is worth it. We cannot release MP1 if it breaks existing modules.
[12:35] < pjuvara> Hopefully it does not and this would be a moot point but I rather be the first to know rather than having the community discover it.
[12:36] < pjuvara> If there are no further questions, let's call the meeting over. Thanks a lot for your participation.
[12:36] < huehner> pjuvara: i'll coordinate the analysis and make a summary to you+rm+qa when ready to decide how to proceed for mp1, ok?
[12:37] < pjuvara> Start 11:40 - end 12:36: 56 minutes - not bad :)
[12:38] < gnuyoga> thx

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

This page has been accessed 49 times. This page was last modified 17:04, 18 May 2009. Content is available under Creative Commons Attribution-ShareAlike 2.5 Spain License.

Category: Community