14
1 Samsung Open Source Group Stefan Schmidt Samsung Open Source Group [email protected] EFL Release Status EFL Developer Day 2014

EFL Release Status

Embed Size (px)

DESCRIPTION

Stefan Schmidt from the Samsung Open Source Group EFL Development team goes over details of the latest Enlightenment for Linux (EFL) release.

Citation preview

Page 1: EFL Release Status

1Samsung Open Source Group

Stefan SchmidtSamsung Open Source Group

[email protected]

EFL Release Status

EFL Developer Day 2014

Page 2: EFL Release Status

2Samsung Open Source Group

Agenda

● Schedule

● High Level Changes

● Tooling

● Last Three Stabilization weeks

● Tweaks to the Schedule

● Announcements

● Miscellaneous

● Future

Page 3: EFL Release Status

3Samsung Open Source Group

Current Schedule and Process

Page 4: EFL Release Status

4Samsung Open Source Group

Schedule

● 3 month release cycle (actually 12 weeks)

– Started with 1.9 in December 2013

– 1.9 was released 1 day late (February 2014)

– 1.10 was released 7 days late (May 2014)

● At that point the change for 3 weeks stabilization started

– 1.11 was released 2 days late (August 2014)

– 1.12 is planned for 10th of November

● In my opinion the 12 weeks release cycle works good.

– Developers start to adjust to it (work in branches)

– Having a few days delay is fine if a showstopper shows up at the end

– For medium level bugs we deliver fixes with an stable update

– Maybe we need to tweak some bits (more on that later)

Page 5: EFL Release Status

5Samsung Open Source Group

High Level Changes

– Release schedule on the wiki and proposal to list

– Release announcement template on the wiki

– Scripted several parts of the release process

– Phab blog and website updates

– Regular stable updates for the last stable series

Page 6: EFL Release Status

6Samsung Open Source Group

Tooling

– To minimize the footwork needed we automated some parts

– Automated NEWS file generation

– For this we introduced the @feature and @fix tags for commit messages

● If we improve the usage of these tags we will get better NEWS files

– Automated building, tarballs generation, uploading, etc

● Scripts are in the release-management git repo

– ABI checker runs to spot ABI/API problems

– Release announcements are still a manual job

● Need to think about a phab template and mail script for these

Page 7: EFL Release Status

7Samsung Open Source Group

Last Three Stabilization weeks

– It is a dull and boring time

– Bug fixing

– Coverity fixes

– Go through the bugtracker and see what you can do

– Review ABI checker results

● It would be good if more people would have a look at these

– Cedric uses this time for performance benchmarking

– The last week should be for fixes of critical issues

Page 8: EFL Release Status

8Samsung Open Source Group

Announcements

● Please add information about bigger changes you made

– The announcements template in the wiki makes it easy

– You know best as you did the work

– It allows you to promote the work you did

● Do folks like the stats I put in the announcement (git, coverity, etc)?

● Anything else that should show up in them?

Page 9: EFL Release Status

9Samsung Open Source Group

Miscellaneous

● Expedite is a handled like a step child

release wise

● Should I do releases for it together with

the rest?

Page 10: EFL Release Status

10Samsung Open Source Group

Future Schedule and Process

Page 11: EFL Release Status

11Samsung Open Source Group

Tweaks to the Schedule

● The first stabilization week seems not to be used at all● Often people keep committing as they did during the merge window

– We already cut of one week as we had better use for it at the end

● Why not merge the two merge windows (pun intended)

– This would allow a clean split in the schedule (8 weeks + 4 weeks)

– Hopefully easier to understand and follow

– Should be more natural (develop -> debug -> fix)

– Four continuous weeks of stabilization should help testing

To me this makes a lot of sense but I want to get opinions on this

before processing it any further.

Page 12: EFL Release Status

12Samsung Open Source Group

Future

Questions for the audience:

– Should we tweak the schedule as proposed?

– Other changes to the schedule or process?

– Anyone want to join and form a release team?

Page 13: EFL Release Status

Thank you.

13Samsung Open Source Group

Page 14: EFL Release Status

14Samsung Open Source Group

We are hiring.

Contact me if you want to hear details.

[email protected]