1) What went well in the release?

• A lot of bugs were fixed
• Lots of community involvement!!
  • Good feedback, and even assistance to other groups

2) What did not?

• CSV was not ready, and delayed the release 1 week
  • Still not fully functional in M5
• Build stability was still a problem sometimes
• Missing base functionality, and tag lib completion still a big problem
• Showcase/push hosting is a big problem
• GAE work needs to be finalized

3) How did jira work for you?

• Worked fine, especially after post_4.F release created, and could organize jira's better

4) Build messages?

• Sometimes, but not often, and I suspect many others felt the same
  • I believe this is part of the disconnect discussed below with QE and docs. 
  • We need to review results of the selenium tests posted, and make that easier for Dev
  • Dev needs to act on them, and sync up with QE.

5) What to change?

• CSV needs to be functionally complete for CR1
  • Already discussed with team, and Alex and Pavel are focused on this.

• Get showcase hosted on GAE asap, and load tested by QE.
  • This should be targeted for mid CR2 in my opinion.
  • I like the idea of weekly refreshed of this
    • Perhaps Fridays starting next Friday
  • Remaining tasks
    • SessionCleaningServlet
    • Optimization steps & wiki page
    • Final load testing round

• Development needs to focus on fixing base functionality, and getting tag lib files accurate, and up to date.
  • This is mostly captured in jira already
    • Tag lib : https://issues.jboss.org/browse/RF-9936
    • Base Functionality component: http://bit.ly/ei8WQf
  • QE & dev should use it where appropriate
  • Dev needs to prioritize it

• Define release criteria and plans for 4.0.F
  • This we need to discuss as a team and it is related to QE/Dev sync up items below.
  • For CR1 this communication did not effectively happen, and QE is concerned about the # of enhancements and features added to a CR release.
  • For CR2 we need to define what is acceptable, and what makes in "ready" for both QE and dev. 

• QE and Dev Sync up
  • QE has many selenium tests setup and the builds are running.  However there are many failing tests - many already have jira's associated with them.  QE would like to use these tests and the % or # failing as release criteria.  I think that is a good idea as long as failures are published with accessible links for minsk team.  Iirc nearly every selenium test has a jira - but is there a way from jira to track that back?  i.e.  Identify what jira's are from what test, and failed?

• We need to agree on some release criteria ( not just the passing selenium tests ), and focus our energies there.  I know that Prabhat has outlined some in the test plan, but I think we as a group need to determine what is acceptable.

• Solving broken builds is just down to developer discipline at this point.  Development branches really did not help, especially given the how difficult they are with SVN.  That said we need to be more careful about breaking the builds.  It leaves everyone paralyzed.

Pavol Pitonak wrote:

 

Hi, here are my comments:

 

* devs don't notify QE about big changes - components, facets, attributes renamed (only Anton B wrote an email about d-n-d)

I agree with this, it was good to see Anton do this.  Post CR1 we should not see any/many "big changes".  The only one that might be is if there are significant issues found in client api review.

* CDK is hasn't been buildable with OpenJDK for almost 3 months RF-9538 - probably requires a one-line fix

Lets talk to Alex and see if we can get this resolved.

* RF-9926 and RF-9933 resolved without being fixed

These were resolved as "done", but should have been resolved as "Unable to Reproduce".  When you reopened it appears Alex K then resolved these.

* devs are not online on IRC, makes me use email = slow

The dev team typically uses yahoo IM, but agree we should all try to be on IRC more often, myself included.

* there was again confusion which version of Mojarra and Myfaces use for testing

This was resolved prior to freeze iirc.  There were some changes required because of AS 6 release.

* atm we have 1500+ Selenium tests from which 105 fails - imho it should be possible to have max. 60 failures for CR1, 30 for CR2 and 15 for Final

Agree we need to sync on this, and reference it in my section.

3. What should we change in the CR phases?

• It's really hard in short time.. But we have to review as much as possible to get all the architectural/naming changes prior to final. example - JS API, facets lists. attributes namings. After final - there will be no possibility to refactor things we will be able only to deprecate somthing and add new things. And that's will be harder to maintain.

Agree, and glad you are leading the client api review!  These need to be completed and reviewed.  If there are minor corrections for CR2 I'm ok with that, but if something comes up and it is a major changes across multiple components we'll all need to plan out.

• In the same time we should see difference between existent features RFCs and new feature requests. And second ones should not be considered in CR. We should concentrate on stability and consistency.
• Should provide online demo asap in order to see how things going with GAE before final. If all the guys will visit it first time in Final day and it will be crashed for some reasons - It will looks too bad.
• Should deploy Push demo asap in order the community to start checking it and provide feedback.

Agree to all above, as for push demo, where to host will be tricky.  Lets discuss this offline.

Nick Belaevski wrote:

 

1) What worked well in the release?

 

• Community reports real issues - much thanks to everyone helping in making RF milestones better!
• Peer code reviews revealed some problems in source code - they were fixed

Both excellent and agree!