balunasj
:
Here is the agenda for today http://community.jboss.org/wiki/RichFacesTeamMeetingAgenda11-23-2010
[
11:00am
]
balunasj
:
ok, so the majority of todays meeting is going to be the M4 post-mortem
[
11:01am
]
balunasj
:
First I wanted a quick rundown of the component status for M5
[
11:01am
]
balunasj
:
if there are any obvious concerns, etc...
[
11:02am
]
AlexBc joined the chat room.
[
11:03am
]
balunasj
:
https://jira.jboss.org/browse/RF-9332
[
11:03am
]
jbossbot
:
jira [RF-9332] New or migrated 4.0.0.M5 components [Open, Critical, Jay Balunas] https://jira.jboss.org/browse/RF-9332
[
11:03am
]
balunasj
:
Konstantin1: how is fileupload looking?
[
11:03am
]
balunasj
:
any major blockers that we have not discussed
[
11:04am
]
balunasj
:
just to multi-task
[
11:04am
]
balunasj
:
Alex_Kolonitsky: Welcome back   I assuming you are going to start on panel menu right?
[
11:05am
]
Alex_Kolonitsky
:
yes
[
11:05am
]
balunasj
:
Alex_Kolonitsky: ok
[
11:06am
]
balunasj
:
amarkhel: and the items for you.  Any major blockers to discuss?
[
11:06am
]
Konstantin1
:
balunasj:I have some problems. But they are resolving. And I am going to finish fileUpload in time.
[
11:06am
]
balunasj
:
Konstantin1: perfect!
[
11:08am
]
balunasj
:
abelevich: Any how about you with toolbar, etc...? 
[
11:08am
]
abelevich
:
Toolbar is ready. Waiting for the review when move them to the trunk
[
11:08am
]
nbelaevski
:
balunasj: yes, according to the little change in upload plans we've discussed on Friday
[
11:08am
]
balunasj
:
nbelaevski: up
[
11:08am
]
abelevich
:
have some troubles with dnd client side
[
11:08am
]
balunasj
:
yup
[
11:08am
]
nbelaevski
:
balunasj: just to clarify Konstantin1 information
[
11:08am
]
nbelaevski
:
ok
[
11:09am
]
balunasj
:
abelevich: great - toolbar
[
11:09am
]
balunasj
:
abelevich: What is going on with dnd - worth a separate meeting?
[
11:10am
]
amarkhel
:
There are no problems with calendar (extra features adding) and drop-down menu.
[
11:10am
]
balunasj
:
amarkhel: +1
[
11:11am
]
balunasj
:
amarkhel: Jason Lee on JSF channel si reporting a JS error with "toLowerCase" and calendar
[
11:11am
]
balunasj
:
looks a lot like https://jira.jboss.org/browse/RF-9666
[
11:11am
]
jbossbot
:
jira [RF-9666] Autocomplete: JS error after AJAX request [Open, Minor, Pavel Yaschenko] https://jira.jboss.org/browse/RF-9666
[
11:12am
]
balunasj
:
abelevich: So should we discuss dnd now, or is it a bigger discussion for offline?
[
11:13am
]
nbelaevski
:
balunasj: RF-9666 happens because of incorrect selection of data on server side
[
11:13am
]
jbossbot
:
jira [RF-9666] Autocomplete: JS error after AJAX request [Open, Minor, Pavel Yaschenko] https://jira.jboss.org/browse/RF-9666
[
11:13am
]
abelevich
:
seems no ...
[
11:14am
]
balunasj
:
nbelaevski: Jason Lee just confirmed the issue only happens with datePattern set.
[
11:14am
]
balunasj
:
abelevich: Seems no... what are you answering?   
[
11:14am
]
balunasj
:
abelevich: Talk offline or now?
[
11:14am
]
nbelaevski
:
balunasj: ok, can you please ask him to file in the JIRA?
[
11:14am
]
abelevich
:
)) need to think
[
11:14am
]
balunasj
:
nbelaevski: already did
[
11:15am
]
balunasj
:
abelevich: ok, so lets talk more offline then
[
11:15am
]
abelevich
:
ok
[
11:15am
]
nbelaevski
:
balunasj: thanks - joined the channel too
[
11:15am
]
nbelaevski
:
balunasj: abelevich: if nobody objects, I'd suggest to take DnD offline
[
11:15am
]
balunasj
:
nbelaevski: agree
[
11:15am
]
nbelaevski
:
balunasj: abelevich: unless this affects planning much
[
11:17am
]
abelevich
:
let's take it offline
[
11:17am
]
balunasj
:
ok
[
11:17am
]
balunasj
:
alexsmirnov & pyaschenko : what is going on with CSV and messages
[
11:17am
]
balunasj
:
still looking ok?
[
11:18am
]
alexsmirnov
:
balunasj: Work going ok, but I had delayed by portletbridge and EPP issues.
[
11:18am
]
pyaschenko
:
balunasj: developing validators and tests
[
11:19am
]
balunasj
:
alexsmirnov: pyaschenko : are there concerns on scheduled time?  We has discussed being a bit early with CSV, has that changed?
[
11:20am
]
alexsmirnov
:
I'm about one week ahead of my initial plan.
[
11:20am
]
balunasj
:
alexsmirnov: so one week later?  just not sure what you mean by "ahead"
[
11:21am
]
alexsmirnov
:
Yes, I meant 'later'
[
11:21am
]
alexsmirnov
:
not wake up yet
[
11:21am
]
balunasj
:
al
[
11:22am
]
balunasj
:
ok
[
11:22am
]
balunasj
:
that should still put us inline for component code freeze though - right?
[
11:23am
]
alexsmirnov
:
balunasj: Yes
[
11:23am
]
balunasj
:
alexsmirnov: +1
[
11:23am
]
balunasj
:
nbelaevski: I know you have been working on tree features - any issue we need to discuss?
[
11:25am
]
nbelaevski
:
I think no - we've discussed some concerns with Alex & Ilya yesterday - decided on decreasing tree code complexity, so I'm working on the prototype now
[
11:25am
]
balunasj
:
ok great
[
11:25am
]
balunasj
:
so unless there is anything else with component status we'll move on the GAE, then to post-mortem
[
11:25am
]
nbelaevski
:
balunasj: btw, I'm working on github, flushing commits to SVN from time to time - hope that's not a problem
[
11:25am
]
balunasj
:
nbelaevski: no that is perfect
[
11:25am
]
nbelaevski
:
balunasj: ok, good
[
11:26am
]
balunasj
:
nbelaevski: unless we switch completely ( thinking post 4.0 ) that is how it needs to be to use git
[
11:27am
]
balunasj
:
so last week prabhaat ran through some load testing on the GAE showcase
[
11:27am
]
nbelaevski
:
balunasj: looking at GIT I think we can even migrate earlier a point to discuss anyway
[
11:27am
]
balunasj
:
nbelaevski: agree, just worried about disruption ( perhaps post M5 )
[
11:27am
]
nbelaevski
:
balunasj: completely agree
[
11:27am
]
balunasj
:
prabhaat: I have some server side data I can put together, and I know you have some client side.
[
11:28am
]
balunasj
:
Overall I was happy with the performance except
[
11:28am
]
balunasj
:
1) initial request is slow
[
11:28am
]
lightguard_jp left the chat room. (Quit: Computer has gone to sleep)
[
11:28am
]
balunasj
:
2) Ajax timing issues that caused failed pages, and browser restarted
[
11:28am
]
ilya_shaikovsky
:
I do not find discussion about required settings for optimizatio
[
11:28am
]
balunasj
:
1) we can't really do much about , it is how GAE dynamically loads/unloads
[
11:29am
]
balunasj
:
ilya_shaikovsky: I'll search and I find - I know the very least it was in meeting transcript
[
11:29am
]
ilya_shaikovsky
:
as discussed earlier and as I told you Jay I do not added anything to production.. so we could look more there for performance
[
11:29am
]
nbelaevski
:
3) I'm concerned by 404 requests with improper URIs
[
11:29am
]
nbelaevski
:
like /static-resources/blueSky/org.richfaces/images/InputBackgrou
[
11:29am
]
prabhaat
:
oops I forgot to monitor this channel ..my bad
[
11:29am
]
balunasj
:
3) yes the failed image requests
[
11:29am
]
balunasj
:
resource etc..
[
11:29am
]
prabhaat
:
balunasj, ok
[
11:30am
]
balunasj
:
So I don't think we can go live until we figure out 2)
[
11:31am
]
balunasj
:
3) needs to be looked into - but seemed not to have too much effect on client side ( i.e. most pages looked fine to me )
[
11:31am
]
balunasj
:
I know we are all busy with our M5 work, so we'll just have to look into 2) as time permits
[
11:33am
]
balunasj
:
ilya_shaikovsky: nbelaevski prabhaat : anything else keeping us from announcing?
[
11:34am
]
ilya_shaikovsky
:
balunasj, I think no.. so I will also look for settings we could add for optimization
[
11:34am
]
nbelaevski
:
balunasj: I think we can further optimize app settings a little for this issue: http://pastebin.com/w3UYDXJw
[
11:34am
]
prabhaat
:
balunasj, nope..we can only validate when there are about 50 threads hitting GAE and we don't find any issue when we are playing with demo at the same time
[
11:35am
]
nbelaevski
:
balunasj: i.e. switch off annotation scanning
[
11:35am
]
balunasj
:
prabhaat: We'll have to see if we can reproduce the 2) issue with the local container from GAE
[
11:35am
]
balunasj
:
nbelaevski: that could be good
[
11:37am
]
•
balunasj
 
thinking of best way to track - jira's for examples likely
[
11:37am
]
balunasj
:
with GAE label
[
11:38am
]
ilya_shaikovsky
:
balunasj, yup.. seems need to define some action items.. as seems in other case we will look for similar things at once
[
11:38am
]
balunasj
:
ok, lets take this offline so we can move the post-mortem - but please add jira's as appropriate to examples and use GAE label
[
11:40am
]
balunasj
:
ok everyone ready to move on to post-mortem?
[
11:40am
]
balunasj
:
http://community.jboss.org/message/571660#571660
[
11:40am
]
balunasj
:
and minutes from last post-mortem - http://community.jboss.org/wiki/RichFacesTeamMeetingMinutes40M3Post-Mortem10-19-2010
[
11:41am
]
balunasj
:
For the most part I think many things went well, and continue to do well.
[
11:41am
]
balunasj
:
The req/dev meeting seem good.
[
11:41am
]
balunasj
:
nbelaevsks git investigation is good, but also too risky to move forward.
[
11:41am
]
balunasj
:
until post M5
[
11:42am
]
balunasj
:
some con's for me
[
11:42am
]
balunasj
:
1) There was still a mad dash at the end of cycle closing and updating jira's.
[
11:43am
]
balunasj
:
1.1) how many could have been updated regularly.
[
11:43am
]
balunasj
:
2) The code-reviews did not seem to happen, or if did had little outcome
[
11:43am
]
nbelaevski
:
agree some cons also -  default setup for windows is quirky and seems to producing conflicts during merge and cygwin crashes my firewall sometimes
[
11:44am
]
balunasj
:
nbelaevski: you talking about git
[
11:44am
]
balunasj
:
?
[
11:45am
]
balunasj
:
3) PanelMenu markup delays
[
11:45am
]
balunasj
:
another pro - I thought the wiki update were helpful for all - i.e. req/dev and final feature list
[
11:46am
]
balunasj
:
4) communication on blocking issues ( carry over from M3 ) - blocking issues need to be communicated so we can work past them.
[
11:46am
]
nbelaevski
:
balunasj: yes, git cygwin client
[
11:47am
]
balunasj
:
nbelaevski: ic
[
11:47am
]
nbelaevski
:
anyway, good impression
[
11:47am
]
balunasj
:
As for focus on M5: Component feature completion, and communication.  We need to nail this last milestone so that we can release early next year.
[
11:48am
]
balunasj
:
we need to be careful of any redesigns now, or additional features that can be address either in Cr, or post 4.0
[
11:48am
]
alexsmirnov
:
balunasj: I only have one suggestion for component development: write out more detail architecture articles before actual component coding, similar to the CSV articles.
[
11:49am
]
alexsmirnov
:
It will be helpful for code review, and can help us to avoid bad solutions.
[
11:49am
]
balunasj
:
alexsmirnov: thanks for mentioning that - for the req/dev meetings we sometime need more impl, and not just features.
[
11:49am
]
balunasj
:
so overall I was happy with M4, we still shifted out components, but steady progress.
[
11:50am
]
balunasj
:
nbelaevski: I know you already posted in the forum - is there anything else you would like to add, or bring up?
[
11:51am
]
nbelaevski
:
balunasj: seems no
[
11:51am
]
balunasj
:
ok, one question - what was you impression on initial quality of components to QE?  Did it get better, stay the same, did the jira, and wiki upates help
[
11:51am
]
balunasj
:
prabhaat: alexsmirnov ilya_shaikovsky etc... ^
[
11:52am
]
ilya_shaikovsky
:
I think that architectural wiki's not needed for components that should be just migrated/simple ones.. it will take dev time and will not provide much effect in that case.. (e.g. all the inputs do not needed that I believe)
[
11:53am
]
nbelaevski
:
also it looks like somewhat hard to create/understand such documents in prose
[
11:53am
]
nbelaevski
:
we need something more visual I think
[
11:53am
]
ppitonak
:
balunasj: devs should check showcase before release process is started, e.g. broken inplace select
[
11:53am
]
prabhaat
:
balunasj, i did not see any better/worse..about the same
[
11:54am
]
balunasj
:
nbelaevski: you mean something like UML doc?
[
11:54am
]
ilya_shaikovsky
:
about initial quality - there was number of issues for every component repiorted during addition to demo.. But I believe only one ore two of them was stopper for some samples creation(in the past it happens that a few components could not be added to demo at all).. so most of them was not critical for me.. so I think we was better with initial quality
[
11:54am
]
nbelaevski
:
balunasj: yes, more like this is better for arch. spec I think
[
11:54am
]
nbelaevski
:
balunasj: class & interaction diagrams
[
11:54am
]
ilya_shaikovsky
:
nbelaevski, balunasj, we had such diagrams for panels by Alex K and that was usefull for review structure and api
[
11:54am
]
nbelaevski
:
balunasj: but just to mention that it's adding more work
[
11:55am
]
nbelaevski
:
ilya_shaikovsky: they show static and that's good. but not dynamic aspects
[
11:55am
]
ilya_shaikovsky
:
what do you mean by dynamic
[
11:55am
]
ilya_shaikovsky
:
?
[
11:55am
]
ilya_shaikovsky
:
I mean which documents you have in mind
[
11:55am
]
ilya_shaikovsky
:
?
[
11:55am
]
balunasj
:
nbelaevski: I think it depends on the component - something with a basic migration, is idfferent than a big change in components like fileupload
[
11:56am
]
balunasj
:
prabhaat: we'll get back to that in one min
[
11:56am
]
ilya_shaikovsky
:
and even that I think not required for example for inplaces or tooltip
[
11:56am
]
nbelaevski
:
balunasj: yes
[
11:57am
]
nbelaevski
:
ilya_shaikovsky: http://www.visualcase.com/tutorials/interaction-diagrams.htm
[
11:57am
]
nbelaevski
:
ilya_shaikovsky: for in-places can be useful too btw
[
11:57am
]
balunasj
:
ok, so design diagrams are needed for components that are more than just a basic migration
[
11:58am
]
ilya_shaikovsky
:
I see sorry do not read last two words in your phrase about diagrams
[
11:58am
]
balunasj
:
that said - this is the last Milestone release, and we won't be adding components
[
11:58am
]
balunasj
:
but still good to determine for future
[
11:58am
]
nbelaevski
:
ilya_shaikovsky: sure np
[
11:59am
]
balunasj
:
lets move back to initial quality - other thoughts on this?
[
11:59am
]
AlexBc left the chat room.
[
12:00pm
]
nbelaevski
:
balunasj: two things to suggest
[
12:00pm
]
ilya_shaikovsky
:
nbelaevski, I still think we should postpone such changes till new components(it not for simple migration cases).. as It will takes additional time and we almost do not have it
[
12:00pm
]
nbelaevski
:
1) QUnit test runner as part of jboss-test suite
[
12:01pm
]
nbelaevski
:
2) complete alexsmirnov work on template example
[
12:01pm
]
nbelaevski
:
ilya_shaikovsky: agree
[
12:02pm
]
alexsmirnov
:
nbelaevski: I'm going to finish template project with CSV development example.
[
12:02pm
]
lightguard_jp joined the chat room.
[
12:02pm
]
balunasj
:
I'm not sure we'll have time on a template example, unless someone has more time on their hands
[
12:02pm
]
balunasj
:
alexsmirnov: d'oh timing that wrong
[
12:02pm
]
balunasj
:
alexsmirnov: ok good, but still would need others to move to it.
[
12:02pm
]
nbelaevski
:
alexsmirnov: good!
[
12:03pm
]
alexsmirnov
:
balunasj: In any case, development example should cover a lot of cases:
[
12:03pm
]
alexsmirnov
:
- skins
[
12:03pm
]
alexsmirnov
:
- test component inside different containers: plain form, table, modal panel, tabs....
[
12:04pm
]
balunasj
:
ok good
[
12:04pm
]
cypo left the chat room. (Quit: Leaving)
[
12:04pm
]
alexsmirnov
:
- render component in plain get request, update by ajax, update after post.
[
12:04pm
]
balunasj
:
how much work would it take for people to migrate, or use the template example?
[
12:05pm
]
alexsmirnov
:
I just want to put code that covers these cases as separate project that can be used with other components.
[
12:05pm
]
abelevich
:
sorry guys I need to go
[
12:06pm
]
balunasj
:
abelevich: onything to add?  or please send email or thread on forums
[
12:06pm
]
alexsmirnov
:
In any case, our examples cover a little from that list.
[
12:07pm
]
balunasj
:
ok
[
12:07pm
]
balunasj
:
before other need to go
[
12:07pm
]
abelevich
:
from my point all was good on M4
[
12:08pm
]
balunasj
:
does anyone else have comments
[
12:08pm
]
ppitonak
:
balunasj: yup
[
12:08pm
]
balunasj
:
amarkhel, Alex_Kolonitsky, ppitonak , others... ?
[
12:08pm
]
abelevich left the chat room. (Quit: Ухожу я от вас)
[
12:08pm
]
ppitonak
:
balunasj: a lot of my and Lukas' jiras found in M3 were postponed to M5
[
12:08pm
]
ppitonak
:
balunasj: shouldn't we try to fix bugs asap?
[
12:09pm
]
ilya_shaikovsky
:
balunasj, I leaved at thread.. in general from my point of view things much better now and have no major suggestions
[
12:09pm
]
balunasj
:
ppitonak: Yes ideally we would resolve asap - but we also needed to prioritize based on milestone targets, and CR stablization.
[
12:10pm
]
balunasj
:
ppitonak: However we will look closer what when a bug was found, and when planned to resolve.
[
12:10pm
]
ilya_shaikovsky
:
balunasj, ppitonak, agree it depends on issue.. if it has not much impact on initial migration usage - we have to concentrate on final release targets and postpone issue
[
12:10pm
]
ilya_shaikovsky
:
we need just review and not blindly move(and I believe we're doing that now )
[
12:10pm
]
ppitonak
:
balunasj: there were problems with which version of Mojarra to use
[
12:11pm
]
ppitonak
:
balunasj: this should be decided much sooner
[
12:11pm
]
ppitonak
:
balunasj: not after release started
[
12:11pm
]
ppitonak
:
balunasj: our demos weren't ready
[
12:11pm
]
ilya_shaikovsky
:
ppitonak, but that really good catch! I was also confused with the respin which should be really solved earlier
[
12:12pm
]
balunasj
:
ppitonak: yes, the demo did use the correct version of mojarra - I agree that was a bug.
[
12:12pm
]
balunasj
:
ilya_shaikovsky: can you explain the last part of that?
[
12:14pm
]
ilya_shaikovsky
:
i meant the respin when we decided to update JSF or not and that was a part of respin reason
[
12:14pm
]
balunasj
:
you mean we should have resolved earlier than the respin?
[
12:14pm
]
ilya_shaikovsky
:
I think such decisions should not be made even if respin really need because of some other issues.. there are always big risks of some additional regressions
[
12:15pm
]
ilya_shaikovsky
:
yes I think we should decide which JSF to use before code freeze and leave with that in current
[
12:15pm
]
ilya_shaikovsky
:
m,ilestone
[
12:15pm
]
balunasj
:
ilya_shaikovsky: yup - agree we should of.
[
12:16pm
]
balunasj
:
we'll not make the same issue this release
[
12:16pm
]
balunasj
:
ppitonak: anything else?
[
12:16pm
]
ppitonak
:
balunasj: no
[
12:17pm
]
balunasj
:
ppitonak: thank you for your input
[
12:18pm
]
balunasj
:
anyone else have comments, before alexsmirnov nbelaevski ilya_shaikovsky and I continue?
[
12:18pm
]
nbelaevski
:
me none
[
12:19pm
]
pmuir left the chat room. (Ping timeout: 240 seconds)
[
12:20pm
]
balunasj
:
ok then, we can continue our discussion from above, or if no futher items we can be done, and I'll write up minutes this week.
[
12:20pm
]
balunasj
:
I think we could conitnue for a while on topics from above though
[
12:22pm
]
nbelaevski
:
can we make s hort break before that?
[
12:22pm
]
nbelaevski
:
* short
[
12:23pm
]
balunasj
:
sure - 5 min
[
12:23pm
]
balunasj
:
?
[
12:23pm
]
nbelaevski
:
thanks!
[
12:23pm
]
ilya_shaikovsky
:
good
[
12:24pm
]
pmuir joined the chat room.
[
12:27pm
]
ilya_shaikovsky
:
+-+------------+
[
12:28pm
]
ilya_shaikovsky
:
sorry.. droped cup to the keyboard
[
12:31pm
]
balunasj
:
really - that is a very consistent drop for a cup
[
12:32pm
]
ilya_shaikovsky
:
[
12:32pm
]
balunasj
:
ok - so lets narrow what we want to discuss for now
[
12:32pm
]
balunasj
:
we identified many of the major items
[
12:32pm
]
balunasj
:
already
[
12:33pm
]
balunasj
:
We have initial quality
[
12:33pm
]
balunasj
:
code reviews
[
12:34pm
]
balunasj
:
samples
[
12:34pm
]
balunasj
:
others?
[
12:34pm
]
balunasj
:
want to focus on any changes needed now - to get M5 + future better
[
12:35pm
]
nbelaevski
:
I have suggestion of publishing showcase regularly
[
12:35pm
]
nbelaevski
:
e.g. on weekly basis
[
12:35pm
]
ilya_shaikovsky
:
nbelaevski, who using it now?
[
12:35pm
]
nbelaevski
:
ilya_shaikovsky: me
[
12:35pm
]
ilya_shaikovsky
:
no problem
[
12:36pm
]
ilya_shaikovsky
:
just want to be sure that it's useful
[
12:36pm
]
ilya_shaikovsky
:
me too but I'm doing my own deployments
[
12:36pm
]
ilya_shaikovsky
:
so seems you're right
[
12:36pm
]
nbelaevski
:
ilya_shaikovsky: I've used old versions of 3.x richfaces-demo constantly
[
12:36pm
]
balunasj
:
nbelaevski: my concern with that would be once we update
[
12:37pm
]
balunasj
:
and make public
[
12:37pm
]
balunasj
:
we can't switch the main version that much
[
12:37pm
]
balunasj
:
we could leave it staged
[
12:37pm
]
balunasj
:
i.e. the new versions
[
12:37pm
]
pmuir left the chat room. (Ping timeout: 245 seconds)
[
12:37pm
]
balunasj
:
like still available for dev testing
[
12:37pm
]
nbelaevski
:
balunasj: that's np, we can keep several versions accessible by different URIs
[
12:37pm
]
ilya_shaikovsky
:
nbelaevski, yup for us and QE
[
12:37pm
]
nbelaevski
:
balunasj: sure it needs to be staged
[
12:38pm
]
balunasj
:
nbelaevski:right - that is just what I wanted to make sure one same page
[
12:38pm
]
nbelaevski
:
balunasj: ok
[
12:39pm
]
ilya_shaikovsky
:
balunasj, except migration which is really critically needed to be started my most concern is demo for now.. I think it's really big gap between our first milestones and first online demo available (even considering compatibility it's too long)
[
12:39pm
]
balunasj
:
agree migration is huge and a priority - I recommend we focus on that next week when I get back from vacation
[
12:40pm
]
balunasj
:
ilya_shaikovsky: agree - I would also like to announce GAE next week, but need to figure out the timing Ajax issue first
[
12:40pm
]
ilya_shaikovsky
:
balunasj, sure
[
12:40pm
]
ilya_shaikovsky
:
all sounds good
[
12:40pm
]
balunasj
:
we can't have users getting failed Ajax requests, and then need to restart their browser.
[
12:41pm
]
balunasj
:
I have a feeling that is going to be a very tricky issue because it is load based, and timing
[
12:42pm
]
ppitonak left the chat room. (Quit: Konversation terminated!)
[
12:42pm
]
ppitonak joined the chat room.
[
12:43pm
]
balunasj
:
nbelaevski: what about code reviews?  What do you think we can do to assist that so we get feedback?
[
12:43pm
]
ppitonak left the chat room. (Client Quit)
[
12:43pm
]
ppitonak joined the chat room.
[
12:44pm
]
nbelaevski
:
balunasj: post-M5 we are going to have more time, so we'll need to do review for core
[
12:44pm
]
nbelaevski
:
a massive oone
[
12:44pm
]
balunasj
:
agree - I've been trying to spend time there myself, but without much success
[
12:44pm
]
nbelaevski
:
balunasj: and I'll ask all team members to provide more feedback
[
12:44pm
]
ppitonak left the chat room. (Read error: Connection reset by peer)
[
12:45pm
]
nbelaevski
:
balunasj: why? timing issue or smth. other?
[
12:45pm
]
balunasj
:
nbelaevski: timing and conflicts
[
12:45pm
]
nbelaevski
:
balunasj: ok I see
[
12:45pm
]
balunasj
:
meetings, reviews, meetings, planning, meetings, etc...
[
12:46pm
]
balunasj
:
[
12:46pm
]
alexsmirnov
:
balunasj: It's may be fine to cross rewiews: every developer should take a look for code that he didn't touch before.
[
12:46pm
]
balunasj
:
alexsmirnov: agree, but not really seeing much in the way of impact from what has happened so far
[
12:48pm
]
nbelaevski
:
alexsmirnov: that's how we worked... my concern is that for some code reviews there are not ouctomes documented either as JIRA comments or traces in JIRA commits history
[
12:48pm
]
balunasj
:
nbelaevski: yup
[
12:49pm
]
balunasj
:
at this point I'm not sure if this meeting is productive.  We have the a list of issues, and I'll create the minutes from them ( alexsmirnov you are off the hook this week for minutes).
[
12:50pm
]
•
balunasj
 
not in a bad way, just don't want force the meeting time
[
12:50pm
]
nbelaevski
:
balunasj: just to clarify - post-M5 we are hardening our code base, correct?
[
12:51pm
]
alexsmirnov
:
balunasj: I see - reminder shown on Google calendar, it's helpful
[
12:51pm
]
nbelaevski
:
balunasj: like a main development vector
[
12:51pm
]
balunasj
:
nbelaevski: yes, and that is it - no new features - unless we really missed something in a core component
[
12:51pm
]
balunasj
:
alexsmirnov: I thought that would be
[
12:51pm
]
nbelaevski
:
balunasj: ok, this is a good direction that should increase quality
[
12:52pm
]
balunasj
:
nbelaevski: exactly we have not been able to spend much time on jira's, but as soon as M5 is tagged
[
12:52pm
]
nbelaevski
:
balunasj: so I think we should be probably thinking about some changes in process
[
12:52pm
]
balunasj
:
everyone should be focused on jira's and review
[
12:52pm
]
balunasj
:
nbelaevski: what were you thinking
[
12:52pm
]
balunasj
:
We'll be having jira reviews and discussions
[
12:53pm
]
nbelaevski
:
balunasj: yes + we have number of unit testing tasks postponed
[
12:53pm
]
balunasj
:
update priorities and assing to CRx as needed.
[
12:53pm
]
nbelaevski
:
ok, good
[
12:53pm
]
balunasj
:
nbelaevski: ah yes, that is right, and I think those ( as I've said before ) should increase in priority, so we'll need to get them too
[
12:54pm
]
nbelaevski
:
maybe more frequent releases - once a week?
[
12:54pm
]
nbelaevski
:
internal ones of coarse
[
12:54pm
]
balunasj
:
nbelaevski: hmm right now it is scheduled for 3 weeks iirc
[
12:55pm
]
balunasj
:
but we could have more rapid releases - could even make public, but just not push too much, or spend too much time on them.
[
12:55pm
]
balunasj
:
It really comes down to timing for them.
[
12:55pm
]
balunasj
:
perhaps every 2 weeks
[
12:55pm
]
balunasj
:
?
[
12:55pm
]
balunasj
:
so one in mid dec.
[
12:55pm
]
balunasj
:
skip holidays ( but still working as possible )
[
12:55pm
]
balunasj
:
One in mid Jan
[
12:55pm
]
balunasj
:
end of jan
[
12:56pm
]
balunasj
:
then either one mid feb or (final )
[
12:56pm
]
balunasj
:
then final end of feb
[
12:56pm
]
balunasj
:
that is about what we dicussed before ( close to it anyway )
[
12:56pm
]
balunasj
:
but with fewer Crs
[
12:57pm
]
balunasj
:
I'm concerned over weekly because of overhead
[
12:57pm
]
balunasj
:
thoughts?
[
12:58pm
]
nbelaevski
:
balunasj: bi-weekly are fine too
[
12:58pm
]
nbelaevski
:
want to get quicker turnaround
[
12:59pm
]
nbelaevski
:
balunasj: also release procedure is easy, so we can do weekly I assume
[
12:59pm
]
balunasj
:
agree - we'll also need to review with prabhaat the status of the test automation and make sure we get tools testing during that time as well.
[
12:59pm
]
nbelaevski
:
balunasj: yes
[
12:59pm
]
balunasj
:
balunasj: yup, but also other overhead for QE, or others to move to it, or review it.
[
1:00pm
]
balunasj
:
agree releasing it fairly easy.
[
1:00pm
]
nbelaevski
:
balunasj: that's true
[
1:00pm
]
nbelaevski
:
ok, if you think we should make them bi-weekly - I'm just fine
[
1:01pm
]
balunasj
:
ok, but I'm not feeling strongly - lets discuss as it gets closer and see, perhaps weekly is good at begining ( or end ) of the CRs
[
1:01pm
]
balunasj
:
ok guys - I'm going to have to go.
[
1:01pm
]
balunasj
:
anything else before I leaev?
[
1:02pm
]
nbelaevski
:
none from me for now
[
1:02pm
]
balunasj
:
ok then - thanks all - I think this went well - I'll write up minutes and later today