...
- 3.7 Status
- Recent Fedora4 updates
- Fedora4 Beta-phase Planning
Notes
Beta Logistics
- Developer stand-up meetings
- Agreement that daily stand-ups are important
- Due to the spread of timezones, suggestion to schedule two stand-ups per day
- Exact times to be decided on-list (ff-tech@googlegroups.com)
- Development iteration window
- The iteration schedule is posted here
- In order to accommodate European and Australian timezones, sprints will be run for 11 days
- Start on Monday
- End on Thursday of the following week
- Exact times for iteration planning meeting and iteration close meeting to be decided on-list (ff-tech@googlegroups.com)
- Iteration definition and validation
- There is a need to have features of each sprint be driven by institutional use cases
- Representatives of Fedora stakeholder institutions (sponsors, advisors, steering group) will help define and "sponsor" sprint features
- At the sprint conclusion, the feature "sponsor" will validate the delivered feature
- Feature validation may be enabled by any of a number of mechanisms
- Install the iteration release at the institution
- Download the source code and run a given build command with a given configuration at the institution
- Execute HTTP commands against a Fedora hosted on behalf of the institution
- CLAs
- Fedora committers should sign and return an individual CLA
- Fedora committer insitutions should sign and return CCLA
Fedora 3.7 Status
- Ben A. has addressed several recent bugs
- Fedora 3.7 release candidate will likely be ready for system testing this week
Recent Fedora 4 Updates
- Ben A. is working on upgrading to JAX-RS 2.0
- Chris B. and Adam S. have been working on bringing Fedora4 into line with principles of Linked Data Platform
- First official sprint of the Beta phase starts Monday, July 29th