On 04/03/14 14:12, Stefan Schmidt wrote: > Hello. > > On Tue, 2014-03-04 at 14:47, Stefan Schmidt wrote: >> Hello. >> >> On Tue, 2014-02-25 at 15:39, Stefan Schmidt wrote: >>> Hello. >>> >>> It just happened. EFL 1.9 is Out. >>> >>> Time to look forward and decide on how we want to handle 1.10. >>> >>> 1.9 went well enough for me to not burn me out which means I would be >>> willing to do 1.10 as well. Given that nobody better suited stands up >>> for it or you guys decide that I did a bad job. >>> >>> For whomever will manage 1.10 I have a proposed schedule: >>> >>> === Schedule === >>> 2014-02-25 EFL release 1.9 / Merge window for 1.10 opens >>> 2014-03-20 Notice about soon ending first merge window >>> 2014-03-24 First merge window is over. >>> * One week stabilization phase starts >>> 2014-03-31 Second merge window opens >>> 2014-04-24 Notice about soon ending second merge window >>> 2014-04-28 Second merge window is over. >>> * Only bug fixes from this point >>> * Alpha release tarball >>> * Three weeks stabilization phase starts >>> 2014-05-05 Beta1 release tarball >>> * Only critical fixes from this point >>> 2014-05-12 Beta2 release tarball >>> 2014-05-19 EFL 1.10 is Out >>> >>> Two things have changed to what we had with 1.9 before. The first >>> stabilization week was cut down to one week and this gained week was >>> added at the end. Some people, including me, have the feeling that it >>> would help us to iron out the bugs before the release. >>> >>> The second thign is that I'm hopefully clearer with the dates this >>> time. I heard people had trouble with them. :) >> >> I heard no complains so far. Going forward I consider the schedule >> final and will try to handle this release as good as I can. > > As requested I put up timers for the different "deadlines" in phab. > > Have a look an tell me if it is really clear this time: > https://phab.enlightenment.org/w/efl_and_elementary_1_10/ > > The events are aligned. For example does the first stabilization phase > starts once the counter for the first merge is down to zero and it > ends once the counter for the beginning of the second merge window > starts. > > If it needs clarification please let me know.
Looks good. I couldn't see any obvious mention of the git commit message + @feature/@fix things. -- Tom. ------------------------------------------------------------------------------ Subversion Kills Productivity. Get off Subversion & Make the Move to Perforce. With Perforce, you get hassle-free workflows. Merge that actually works. Faster operations. Version large binaries. Built-in WAN optimization and the freedom to use Git, Perforce or both. Make the move to Perforce. http://pubads.g.doubleclick.net/gampad/clk?id=122218951&iu=/4140/ostg.clktrk _______________________________________________ enlightenment-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
