10:59am
]
balunasj_mtg
:
HI All
[
10:59am
]
balunasj_mtg
:
Here is teh agenda for today - http://community.jboss.org/wiki/RichFacesTeamMeetingAgenda10-19-2010
[
10:59am
]
alexsmirnov joined the chat room.
[
11:00am
]
balunasj_mtg
:
ok - lets get started
[
11:00am
]
balunasj_mtg
:
We have a lot to got through
[
11:00am
]
balunasj_mtg
:
http://community.jboss.org/wiki/RichFacesTeamMeetingAgenda10-19-2010
[
11:01am
]
balunasj_mtg
:
I would like to cover the first few items quickly so we can start in on the post-mortem
[
11:01am
]
balunasj_mtg
:
So first up some community items
[
11:01am
]
balunasj_mtg
:
last week we discussed a review of Bernards components.  Unfortunately I have not been able to get to it yet
[
11:02am
]
balunasj_mtg
:
has anyone else been able to?
[
11:02am
]
balunasj_mtg
:
alexsmirnov: nbelaevski ishaikovsky ^
[
11:02am
]
nbelaevski
:
sorry, but no yet
[
11:02am
]
nbelaevski
:
but it's on my nearest TODO list
[
11:03am
]
balunasj_mtg
:
As with mine
[
11:03am
]
balunasj_mtg
:
I'm hoping to get to it today/tomorrow.
[
11:03am
]
ishaikovsky
:
balunasj_mtg, the same for me.. today I was able to answer about popup panel but has no time remained for components.. I think tommorow is most likelly do
[
11:03am
]
balunasj_mtg
:
ishaikovsky: ok - I saw your response to the popup.
[
11:04am
]
balunasj_mtg
:
ishaikovsky: thanks.
[
11:04am
]
ishaikovsky
:
It was just faster to do so decided to go with it from the beginning to complete today
[
11:04am
]
balunasj_mtg
:
ok lets just move on M4 items
[
11:04am
]
balunasj_mtg
:
First a quick status on components planned for 4.0
[
11:04am
]
alexsmirnov
:
Hy guys
[
11:05am
]
balunasj_mtg
:
alexsmirnov: Pavel ( not on ): How is this going?
[
11:05am
]
balunasj_mtg
:
CSV I mean ^
[
11:05am
]
alexsmirnov
:
server side going as expected.
[
11:06am
]
balunasj_mtg
:
alexsmirnov: ok
[
11:07am
]
balunasj_mtg
:
nbelaevski: we have the tree dev/req meeting tomorrow - still good timing for it?
[
11:07am
]
alexsmirnov
:
For Pavel, I asked him to create test runner for converters/validators first, but did not have any questions yet.
[
11:07am
]
nbelaevski
:
I've almost completed with test base for CSV client code
[
11:07am
]
balunasj_mtg
:
alexsmirnov: ok
[
11:07am
]
balunasj_mtg
:
nbelaevski: did you take this over for pavel?
[
11:07am
]
nbelaevski
:
alexsmirnov: I'm working on this runner - almost completed server code, but need some participation from Pavel
[
11:08am
]
nbelaevski
:
balunasj_mtg: yes, there are JSF classes used, so I've decided to create something easily extendable for him
[
11:08am
]
balunasj_mtg
:
nbelaevski: ok - hope it does not impact other areas too much for you.
[
11:08am
]
alexsmirnov
:
For CSV client test, I got an idea yesterday. It's not necessary to use qUnit there - JavaScript engine like rhino well enougth.
[
11:09am
]
alexsmirnov
:
It can interact with java, so test able to compare results from script and java component.
[
11:09am
]
nbelaevski
:
alexsmirnov: that's what we are doing
[
11:09am
]
balunasj_mtg
:
alexsmirnov: I want to a void getting into details for now - so we have enough time for post-mortem.
[
11:09am
]
nbelaevski
:
alexsmirnov: also it's hard to compare results in Java - equals(...) is not overriden there
[
11:10am
]
nbelaevski
:
for JS Rhino objects
[
11:10am
]
nbelaevski
:
balunasj_mtg: for tree timing is fine
[
11:10am
]
balunasj_mtg
:
nbelaevski: ok
[
11:10am
]
balunasj_mtg
:
abelevich: How are things looking with InplaceSelect and Select?
[
11:12am
]
abelevich
:
inplaceSelect is ready need to complete junits
[
11:12am
]
abelevich
:
select almost ready need go through feature list from wiki article once again and write junits too
[
11:13am
]
balunasj_mtg
:
abelevich: ok good - please let me know when it is ready - I would like to review that one.
[
11:14am
]
abelevich
:
sure
[
11:14am
]
balunasj_mtg
:
Alex_Kolonitsky: Panel menu - how is it going?  Anything come up?
[
11:15am
]
Alex_Kolonitsky
:
I've started implementation of server side
[
11:16am
]
balunasj_mtg
:
Alex_Kolonitsky: feeling good on estimates still?
[
11:17am
]
balunasj_mtg
:
amarkhel: How about you and toobar?
[
11:17am
]
balunasj_mtg
:
amarkhel: I know you have other bugs as well to work on.
[
11:17am
]
Alex_Kolonitsky
:
yes, maybe we will move some bugs to M5, but with new component all fine
[
11:18am
]
balunasj_mtg
:
Alex_Kolonitsky: ok - please let me know what you want to shift so nbelaevski and I can review.
[
11:18am
]
Alex_Kolonitsky
:
ok
[
11:18am
]
balunasj_mtg
:
Konstantin1: Fileupload meeting on Thursday - good timing for you?
[
11:19am
]
Konstantin1
:
balunasj_mtg: yes
[
11:19am
]
nbelaevski
:
balunasj_mtg: do you mean tooltip?
[
11:19am
]
amarkhel
:
I've started tooltip server side
[
11:20am
]
balunasj_mtg
:
nbelaevski: yup - sorry typo
[
11:20am
]
balunasj_mtg
:
amarkhel: estimates still seem good?
[
11:20am
]
nbelaevski
:
balunasj_mtg: np
[
11:20am
]
amarkhel
:
yes
[
11:21am
]
balunasj_mtg
:
ok
[
11:22am
]
balunasj_mtg
:
So that covers all the components planned for M4.  nbelaevski I know you have been looking at push updates as well
[
11:23am
]
balunasj_mtg
:
Does anyone have anything else they would like to bring up before we start M3 post-mortem meeting?
[
11:23am
]
nbelaevski
:
balunasj_mtg: it seems we are all set with filleUpload - so I'd suggest to save some time for meeting
[
11:23am
]
nbelaevski
:
ishaikovsky: ^
[
11:25am
]
ishaikovsky
:
I agree
[
11:25am
]
balunasj_mtg
:
nbelaevski: Even if no open questions I would still like to review the wiki descriptions, estimates, and basic plan.
[
11:25am
]
balunasj_mtg
:
ishaikovsky: Konstantin1 : Is that up to date with this info?
[
11:25am
]
nbelaevski
:
balunasj_mtg: sure np. then we definitely need it
[
11:26am
]
balunasj_mtg
:
nbelaevski: If the wiki is complete, I can just review that.
[
11:26am
]
balunasj_mtg
:
nbelaevski: just want to make sure the info is captured somewhere
[
11:27am
]
nbelaevski
:
balunasj_mtg: thanks - this sounds good
[
11:27am
]
ishaikovsky
:
nbelaevski, balunasj_mtg, ok so we will just highlight points which are questionable.. but I believe we will have to cimplify the component in questionable parts and extend later for speeding up process
[
11:27am
]
ishaikovsky
:
balunasj_mtg, wiki with high level points for FU not ready
[
11:27am
]
nbelaevski
:
Konstantin1: ishaikovsky: so what's with mtg time?
[
11:27am
]
ishaikovsky
:
but will be for meeting
[
11:27am
]
Konstantin1
:
nbelaevski: yes
[
11:28am
]
balunasj_mtg
:
ishaikovsky: please let know when it is ready.  FileUpload is one of those key components that has had some issues in the past.
[
11:28am
]
ishaikovsky
:
ok
[
11:28am
]
ishaikovsky
:
balunasj_mtg, sure
[
11:28am
]
balunasj_mtg
:
ok
[
11:29am
]
balunasj_mtg
:
So lets keep the meeting for now, and if the wiki is ready first I'll review, and perhaps we can skip the meeting if no open questions.
[
11:31am
]
balunasj_mtg
:
anything else before the post-mortem?  On anything?
[
11:32am
]
balunasj_mtg
:
ok
[
11:32am
]
balunasj_mtg
:
Good so lets get started
[
11:32am
]
balunasj_mtg
:
I want to change things up a little bit that what we have done in the past.
[
11:33am
]
balunasj_mtg
:
I'd like to kind of go in reverse order, so that 3-4 of us don't end up taking all the time
[
11:33am
]
balunasj_mtg
:
ppitonak: lfryc : I know that prabhat is on vacation ( hope you guys had a good meeting ). 
[
11:33am
]
balunasj_mtg
:
ppitonak: lfryc : Would like to hear from you guys on the post-mortem points.
[
11:34am
]
balunasj_mtg
:
http://community.jboss.org/message/567152#567152
[
11:34am
]
balunasj_mtg
:
ppitonak: lfryc : If you would rather wait for Quality meeting on Thursday we can do that too, as prabhat will be there for that one
[
11:35am
]
monkeyslikebanan left the chat room.
[
11:35am
]
lfryc
:
balunasj_mtg: I think it would be better to wait for Prabhat
[
11:35am
]
ppitonak
:
balunasj_mtg: yup, I agree with Lukas
[
11:35am
]
balunasj_mtg
:
lfryc: ok that is fair - we will discuss with QE on Thursday
[
11:36am
]
lfryc
:
balunasj_mtg: we prepared some points during meeting last week and Prabhat have all the notes
[
11:36am
]
balunasj_mtg
:
ok so lets move on development
[
11:36am
]
lfryc
:
ok
[
11:36am
]
balunasj_mtg
:
Konstantin1: Would like to get us started.  What are your commented for the post-mortem?
[
11:40am
]
balunasj_mtg
:
Konstantin1: ping^
[
11:41am
]
Konstantin1
:
I didn't see some problems with M3 for me.
[
11:42am
]
balunasj_mtg
:
Konstantin1: What are your thoughts on speeding up component development?  so we don't slip so many components?
[
11:45am
]
Konstantin1
:
I think that we cannot speed up developing without loosing quality.
[
11:47am
]
balunasj_mtg
:
Konstantin1: That leads to another topic, that I know QE will be talking about on Thurs.  How to make sure initial quality and initial expectations match.  In the last release there were a couple of basic issues.  We can cover that later I guess.
[
11:47am
]
balunasj_mtg
:
Konstantin1: Anything else?
[
11:48am
]
alexsmirnov
:
balunasj_mtg: I guess the answer is more test-centric development. At least, I see that only Nick and me use and improve test framework...
[
11:49am
]
balunasj_mtg
:
alexsmirnov: ok that is getting somewhere.  You mean more TDD concepts?
[
11:49am
]
alexsmirnov
:
balunasj_mtg indeed.
[
11:49am
]
balunasj_mtg
:
alexsmirnov: or just more testing during development, instead of waiting for "unit test" jira
[
11:50am
]
Konstantin1
:
balunasj_mtg: I can say about my components only and QA had mistakes in their application not in components.
[
11:51am
]
nbelaevski
:
while I was absent a certain part of iteration, I have several suggestions too
[
11:52am
]
nbelaevski
:
1) we were talking about code reviews but need to get this done on more intensive basis
[
11:53am
]
nbelaevski
:
2) CDK had some blockage issues reported by Alex K.
[
11:53am
]
balunasj_mtg
:
alexsmirnov: When it is you turn - I'd like to hear how you think we can implement that with the team.
[
11:56am
]
nbelaevski
:
3) for prep. if possible we need to agree on requirements befoore iteration, not when it's started - but the question is whether this is realistic
[
11:56am
]
balunasj_mtg
:
nbelaevski: for 1) We'll need to find a way for peer reviews, that do not impact the entire team, but still get done.
[
11:57am
]
nbelaevski
:
balunasj_mtg: agree for #1
[
11:57am
]
balunasj_mtg
:
2) What could be done differently to have avoided?
[
11:57am
]
alexsmirnov
:
nbelaevski: I don't see new CDK issues in JIRA, and no one told me about critical issues in CDK.
[
11:58am
]
balunasj_mtg
:
3) I have been struggling with that too - not sure how to complete req/dev meeting for next iteration, during current iteration...
[
11:59am
]
nbelaevski
:
alexsmirnov: https://jira.jboss.org/browse/RF-9323 but it's not marked as critical so that looks like a problem at ours side
[
11:59am
]
jbossbot
:
jira [RF-9323] CDK annotation @RendererSpecificComponent.attributes doesn't work [Open, Major, Alexander Smirnov] https://jira.jboss.org/browse/RF-9323
[
12:00pm
]
nbelaevski
:
I'll add one item from QA - there were issues discovering what's done on what iteration - we had a talk with Ilya and we'll fix this
[
12:00pm
]
balunasj_mtg
:
yeah - if it is blocking development it should be critical ( and the involved people need to be contacted, not just jira ).
[
12:00pm
]
nbelaevski
:
now reqs. should be updated with that info and be correct
[
12:01pm
]
balunasj_mtg
:
nbelaevski: Yes - we discussed that in last post-mortem - having wiki reflect "actual" work when completed.
[
12:02pm
]
balunasj_mtg
:
before we keep going.  Konstantin1 anything else to add?
[
12:02pm
]
nbelaevski
:
balunasj_mtg: ok
[
12:02pm
]
ishaikovsky
:
balunasj_mtg, yes I'm also concerned with how to deal with future reque's and have all the other activities done also.. count of tasks not reducing but growing stable for now.. and that not add time to start something for new iteration during current one. Besides even if I will prepare something for next iteration - I will need to draw dev attention from current iteration for review which also not looks acceptable in situation where we already post
[
12:03pm
]
•
balunasj_mtg
 
I want to make sure everyone has a chance to comment.
[
12:03pm
]
ishaikovsky
:
so currently could only do the best to make them in sync with code including changes which was made after requirements finalizing
[
12:04pm
]
balunasj_mtg
:
ishaikovsky: Yup - that is part of why I think the initial week after freeze ( the one between freeze and release )
[
12:04pm
]
Konstantin1
:
balunasj_mtg: no
[
12:04pm
]
balunasj_mtg
:
I typically say to work on postponed jira's ( like the unit tests etc... )
[
12:05pm
]
ishaikovsky
:
balunasj_mtg, the week when I made GAE checks in that iteration and reviewed documentation.. so other tasks impact still on the scene
[
12:05pm
]
ishaikovsky
:
balunasj_mtg, but for sure ideally need to find the time during that week
[
12:06pm
]
balunasj_mtg
:
ok, lets see if some other have comments, then we'll keep going.
[
12:07pm
]
balunasj_mtg
:
amarkhel: Any feedback, pros/cons, suggestions from post-mortem meeting?
[
12:07pm
]
amarkhel
:
no
[
12:08pm
]
balunasj_mtg
:
Alex_Kolonitsky: How about you - any items from you?
[
12:08pm
]
amarkhel
:
no
[
12:08pm
]
Alex_Kolonitsky
:
also no
[
12:09pm
]
balunasj_mtg
:
ishaikovsky: I know you already posted in forums, but wanted give you time to say what you would like...
[
12:11pm
]
ishaikovsky
:
wanted to add one item which I not posted in forum.. really the problems with QE exist as Konstantin mentioned but I understand that them partially could be caused by the fact of some assync between reque's and components actual state..
[
12:11pm
]
ishaikovsky
:
and could appears even more if them will get the component at last time too close before release (while updating tests in a hurry)
[
12:12pm
]
ishaikovsky
:
So want to discuss at quality meeting from Prabhat how we could improve there
[
12:12pm
]
ishaikovsky
:
to help them be more in sync
[
12:12pm
]
balunasj_mtg
:
ishaikovsky: good topics and similar to one of mine
[
12:12pm
]
ishaikovsky
:
and points from forum
[
12:13pm
]
abelevich
:
to be in sync with QA dev need a feature checklist per component
[
12:13pm
]
balunasj_mtg
:
How to make sure this QE has same expectations and env so that we avoid some of these issues.
[
12:13pm
]
ishaikovsky
:
abelevich, which could be somtimes modified before release
[
12:13pm
]
ishaikovsky
:
currently
[
12:13pm
]
balunasj_mtg
:
abelevich: That should be part of wiki page imo
[
12:13pm
]
abelevich
:
we should avoid this during iteration
[
12:13pm
]
ishaikovsky
:
so.. in general
[
12:14pm
]
ishaikovsky
:
most points worked well for me
[
12:14pm
]
ishaikovsky
:
problems
[
12:14pm
]
ishaikovsky
:
(considering that I was out half of iteration)
[
12:15pm
]
ishaikovsky
:
During iteration finalizing there was some misscommunication with Lex.. And it was caused by the fact that his expectations from requirements was different from wimi page also
[
12:15pm
]
ishaikovsky
:
so we needed to adjust markup at last time
[
12:16pm
]
ishaikovsky
:
in that case - wiki page was updated.. but from that situation - seems I shouldthink about some way to update Lex more carefully during some changes
[
12:16pm
]
ishaikovsky
:
during - after
[
12:16pm
]
ishaikovsky
:
which affects markups
[
12:16pm
]
ishaikovsky
:
==Several components were postponed - how can we get components out faster with better initial quality?
[
12:16pm
]
ishaikovsky
:
As for posponed components - I believe we just failed to provide right estimations considering vacations of four people. And seems some redesign/refactoring of 3.3.x code was not considered in estimations again.
[
12:17pm
]
ishaikovsky
:
and the next point related to this one
[
12:17pm
]
ishaikovsky
:
==How can we change M4 to make development easier, faster, more stable?
[
12:17pm
]
ishaikovsky
:
so my conclusion is - Migrate closer to original 3.3 code and moving refactoring/redesign work as separate features if possible for future releases more often.
[
12:17pm
]
ishaikovsky
:
as I written at forum only those redesign works which could be really smoothly done later
[
12:17pm
]
ishaikovsky
:
not including critical once for sure
[
12:17pm
]
ishaikovsky
:
In that case we could get better to estimated time.
[
12:18pm
]
ishaikovsky
:
and last point
[
12:18pm
]
ishaikovsky
:
==Planning, prep, and jira updates - where can we improve?
[
12:18pm
]
ishaikovsky
:
1) great to start with separate per-component meetings
[
12:19pm
]
ishaikovsky
:
+ less peoples involved and better feedback from ones who =actually work on it
[
12:19pm
]
balunasj_mtg
:
ishaikovsky: agree with needing a better workflow with lex - nbelaevski ishaikovsky and I should discuss offline
[
12:19pm
]
ishaikovsky
:
2) (really minor) I will ask Sean move actual tasks on documentation review and updates to RF from RFPL
[
12:19pm
]
ishaikovsky
:
and Plan
[
12:20pm
]
balunasj_mtg
:
ishaikovsky: My concern with this one "Migrate closer to original 3.3 code and moving refactoring/redesign work as separate features if possible for future releases more often."
[
12:20pm
]
balunasj_mtg
:
ishaikovsky: Is that never gets done
[
12:20pm
]
balunasj_mtg
:
ishaikovsky: and we end up with 3.3.X code that does not really "fit"
[
12:20pm
]
ishaikovsky
:
even now we twice changed the load and tasks on dev's.. not critically but done that.. that could later looks as "failed to deliver" but for me it looks as failed to plan from the beginning
[
12:21pm
]
ishaikovsky
:
ok comments
[
12:21pm
]
ishaikovsky
:
[19:20:08] balunasj_mtg: ishaikovsky: My concern with this one "Migrate closer to original 3.3 code and moving refactoring/redesign work as separate features if possible for future releases more often."
[
12:21pm
]
ishaikovsky
:
[
12:21pm
]
ishaikovsky
:
1) we could estimate the work thinking in 3.3 therms.. but then real problems appears during redesign and them influence estimations of the M
[
12:22pm
]
ishaikovsky
:
2) again - component have to be reviewed.. all the users features and concerns should be covered
[
12:22pm
]
ishaikovsky
:
but
[
12:22pm
]
ishaikovsky
:
if the issue not breaks the component in general or just markup has some problems - component could go with it having separate task to be created
[
12:23pm
]
balunasj_mtg
:
ishaikovsky: I think that redesign is a key item for 4.0.  We are not able to start-fresh completely, so we need to clean as wel go.
[
12:23pm
]
ishaikovsky
:
redesigned for the end-developer - but with some internal issues to be covered later
[
12:24pm
]
balunasj_mtg
:
ishaikovsky: Idendifing specific issues is fine ( i.e. /*Not changing this method during 4.0 migrations because XXX needs to support YYYY - see RF-ZZZZ */
[
12:24pm
]
ishaikovsky
:
that should be carefully split.. we seems need to find some "middle" solutions to deliver in time and in the same time has no redesigns later
[
12:26pm
]
ishaikovsky
:
yup to create issue (XXX markup still used at that part of YYY comp because of redesign complexity - it should be later rewritten to ZZZ as will not affect the end user)
[
12:27pm
]
balunasj_mtg
:
Yes - we need to make sure we get major design updates in, but other items can push.
[
12:27pm
]
ishaikovsky
:
So I'm not sure that we have to solve all bugs and RFC's from the first component version. We need to cover base and make carefull review - and then add.
[
12:27pm
]
nbelaevski
:
ishaikovsky: are we going to include such issues as part of reqs. spec.?
[
12:27pm
]
balunasj_mtg
:
ok ishaikovsky good topics, but we should move on to hear from abelevich nbelaevski alexsmirnov and wrap up.
[
12:28pm
]
balunasj_mtg
:
nbelaevski: We should - they should be part of what is discussed in component meetings
[
12:28pm
]
ishaikovsky
:
nbelaevski, I've already moved number of RFCs and some issues from 3.3 and developer should check during estimation what fit the release. As actually he's the best person to check the complexity
[
12:28pm
]
ishaikovsky
:
balunasj_mtg, ok
[
12:29pm
]
ishaikovsky
:
nbelaevski, and the links to related issues included in all latest components documents
[
12:30pm
]
nbelaevski
:
balunasj_mtg: agree for RFCs
[
12:30pm
]
nbelaevski
:
and for the links
[
12:30pm
]
balunasj_mtg
:
ishaikovsky: we need to to continue adding those, and if there are redesign items postponed to
[
12:32pm
]
balunasj_mtg
:
All:  Ideally we would solve all of these issues in this meeting
[
12:32pm
]
ishaikovsky
:
balunasj_mtg, he he I was a minute later at forum thread about RF 4
[
12:32pm
]
balunasj_mtg
:
I think it is more important to get our base issues down, and initial discussions, then more on.
[
12:33pm
]
balunasj_mtg
:
I'll have minutes, and follow up items.
[
12:33pm
]
balunasj_mtg
:
So abelevich : I'd like to hear any additional items or feedback related to the post-mortem posts.
[
12:34pm
]
abelevich
:
have some thoughts how to speed up component development but I am not sure that public meeting is a right place for this
[
12:37pm
]
balunasj_mtg
:
abelevich: ok that is fine we can discuss offline
[
12:37pm
]
balunasj_mtg
:
abelevich: anything else?
[
12:37pm
]
abelevich
:
no
[
12:39pm
]
balunasj_mtg
:
nbelaevski: alexsmirnov :  Any thing new or specific you would like to bring up, or just continue our current discussion.
[
12:39pm
]
balunasj_mtg
:
For me I see dev branches ( including migration to git ), and component development improvements as primary topics
[
12:40pm
]
nbelaevski
:
balunasj_mtg: I don't have much to add to the already said
[
12:40pm
]
balunasj_mtg
:
alexsmirnov: How about you?
[
12:40pm
]
nbelaevski
:
planning is one of the problems to discuss I think
[
12:40pm
]
alexsmirnov
:
balunasj_mtg: Artifacts for ui/sample projects don't work. For CSV, i did make them by copy/paste.
[
12:41pm
]
balunasj_mtg
:
nbelaevski: agree with planning as well.
[
12:41pm
]
balunasj_mtg
:
alexsmirnov: Not following - please explain a little more.
[
12:42pm
]
nbelaevski
:
alexsmirnov: do you mean archetypes?
[
12:42pm
]
alexsmirnov
:
sure -Archetypes for development projects were not updated for M3 build structure.
[
12:42pm
]
balunasj_mtg
:
nbelaevski: If the archetypes - I know they are broken   Have jira's in there already.
[
12:43pm
]
alexsmirnov
:
nbelaevski:Yes, I saw that
[
12:44pm
]
balunasj_mtg
:
ok so big items I see:
[
12:44pm
]
balunasj_mtg
:
1) Planning, how to make it earilier and more accurate
[
12:44pm
]
balunasj_mtg
:
2) Component development time - suggestions, and changes to speed and improve quality
[
12:45pm
]
balunasj_mtg
:
3) Dev branch and git migration as a possible solution
[
12:45pm
]
balunasj_mtg
:
any others at a high level?
[
12:47pm
]
nbelaevski
:
QE feedback is important so I'd suggest to make this 4th point we should keep in mind it'll have to wait by Thu, but anyway)
[
12:47pm
]
balunasj_mtg
:
nbelaevski: agree
[
12:49pm
]
balunasj_mtg
:
so the question now is - do we continue to talk about these for anyoher 10 min
[
12:49pm
]
balunasj_mtg
:
or should I just write up minutes and create tasks/meeting to discuss in more detail?  or perhaps forum posts?
[
12:50pm
]
balunasj_mtg
:
My vote is for minutes, and new meeting - this is hour 4 for meetings for me today.
[
12:51pm
]
•
nbelaevski
 
casts vote for minutes too
[
12:52pm
]
balunasj_mtg
:
ok - lets do that unless alexsmirnov or ishaikovsky object severely
[
12:52pm
]
alexsmirnov
:
balunasj_mtg: me too for minutes and discussion on mailing list or forum.
[
12:53pm
]
balunasj_mtg
:
ok so I think that is it for now
[
12:53pm
]
balunasj_mtg
:
Thanks to all of those that participated 1
[
12:53pm
]
balunasj_mtg
:
!
[
12:53pm
]
ishaikovsky
:
yup.. also gtg
[
12:53pm
]
ishaikovsky
:
Thanks guys!!!
[
12:54pm
]
wesleyhales joined the chat room.
[
12:58pm
]
nbelaevski
:
thanks all