Release is planned on February 24th 2014:
With the 1.9 release cycle the Enlightenment project is switching to a time based release schedule. This is a big step for us that involves many changes to our workflows so please bear with us if not everything is perfect in this cycle.
We aim for a 12 weeks release cycle which is a little under three months. The schedule is divided into 4 distinct parts: a 4 weeks development period which allows for features and fixes to get commit followed by a 2 weeks stabilization period which allows only fixes to be committed into the master branch. These two elements are repeated a second time to complete our schedule.
2013-12-02 EFL release 1.8 / Merge window for 1.9 opens
2013-12-26 Notice about soon ending first merge window
2013-12-30 First merge window is over.
- Cut a technology preview tarball (different name?)
2013-12-31 Stabilization phase starts
2014-01-13 Second merge window opens
2014-02-06 Notice about soon ending second merge window
2014-02-10 Second merge window is over.
- Only bug fixes from this point
- Alpha release tarball
2014-02-11 Stabilization phase starts
2014-02-17 Beta release tarball
- Only critical fixes from this point
2014-02-24 EFL 1.9
With this release we will also change the way we handle our NEWS and ChangeLog files.
We see the value they provide. Giving users and packagers an overview of what happened in this release. On the other hand they cause us major pain with merge conflicts when working in branches or backporting. It also results in quite an overhead to update them all the time. We are going to try get you this information somehow different this cycle.
Please don't update NEWS or ChangeLog but instead you have two options for providing this information.
- Put bugfix or feature into the summary line of your commit message (This is the way Mike will handle it for E19 onwards)
- Put description on the release announcement wiki page.
For bugfixes always put the phab bug number into the commit message. For bigger features don't spare characters on the commit message to descriptive what it aims for and what it will provide to us. I will read through the commit log at the end of each merge window and try to summarise whats in there on our release announcement page which will be the base for the release announcement mails, etc. Please help me with that by having good commit messages or filling in sections about your changes.
- Work on a bigger feature in a branch and once its ready bring it over in one go to master in one of the merge windows.
- For bigger features please have some description for me to put into the release notes. If you also want to provide screenshots or a video be my guest.
- Have descriptive and in general good commit messages. I will read through them for the release notes and yell at you if they are bad.
- If you fix a bug from phab always put in the phab bug number
- If you have something big and disruptive please bring it in at the first merge window to allow enough time for testing and fixing
- We are also doing 1.8.x point releases during the 1.9 development cycle. Please keep in mind to backport them to the 1.8 stable branch. This is way esier for efl now as we had the first release with the merged tree now.
This section lists features planned for the 1.9 cycle. Please keep in mind that any of these can get skipped depending on maturity in time for the release. We will not wait on them for the release. The only valid list will be in the final release announcement. This will most likely not cover all new things as we rely on the developers to fill it up.