Attendees
...
Time | Topic | Presenters | Notes | |
|---|---|---|---|---|
| 5 min |
| Added a request to make shanges changes to the Moselle schedule. We have quorum Minutes from last week accepted. | ||
| 5 min |
|
| ||
| 2 min |
| No Updates. Beth Cohendid not wear her Anuket Ambassador T-Shirt again. | ||
| 10 min | Release Updates
| Per Karine Sevilla During RM and RA1 last meetings, we discussed about the release milestones M3 (content freeze), M4 (proofreading) and M5 (release readiness). The time period to reach M3 is too short and the time periods between M3-M4 and M4–M5 are too long and useless for us. We would like to modify the milestones to adapt to the specification production needs. Our proposal is the following: M3 May 17 (instead of April 19) M4 May 31 (instead of May 17) M5 June 7 (unchanged) M6 June 14th (unchanged) This proposal is validated by RA1 contributors and supported by Walter for RM. The software workstreams would not change. This proposal is only for the specification tasks. David McBridenotes that this would require two additional milestones that would need to be tracked. TSC supports this proposal. David McBridewill add the two additional milestones and update the process docs. David McBride RC is still outstanding in the release schedule. Cédric Ollivier The process for testing RC2 is on Jenkins/Gerrit/Github - there is a clear veasibility what's selected by RC2, and then tested/covered via Jenkins automatically. RC2 is updated as soon as K8s releases a new version. Any new test cases must follow this RC's best practices before being integrated in RC2. | ||
| 5 min |
| All the information on the progress is on the Wikipage. | ||
| 10 min |
|
| ||
| 5 min |
| |||
| 5 min | LFN TAC | |||
| 2 min |
| |||
| 2 min |
| Sub-project Leaders | ||
| 5 min |
|
| ||
| 1 min | AOB |
...