On 20/04/15 13:15, Stefan Schmidt wrote: > Hello. > > 1.14 is one a good way now an it is about time to discuss the schedule for > 1.15 > > Tom approached me with a suggestion to ease the predictability of our release > dates. > Instead of doing a schedule being aligned with the 12 weeks he suggested that > we use the first Monday of a month every three month. For us that would mean: > > First Monday of August: 1.15 > First Monday of November: 1.16 > First Monday of February: 1.17 > First Monday of Mai: 1.18 > First Monday of August: 1.19
Yup, and the freeze starting the first Monday the month before. This way, we don't have to think and look up when freeze starts/ends and when the release is at, we just know (at least the ballpark). This also lets projects that have more long term planning than what we do, reliably be able to predict our releases way ahead. > ... > > This means we are no longer having the fixed 8+4 weeks schedule instead the > merge window would grow or shrink based on the months lengths. I would keep > the stabilization phase at the last 4 weeks as we are doing now. The variation in length is not that significant. > > Based on this a proposal looks like this: (9+4 weeks) > > 2015-05-04 Merge window for 1.15 opens > 2015-06-22 Notice about soon ending merge window > 2015-07-06 Merge window is over. > > * Only bug fixes from this point > * Alpha release tarball > * Four weeks stabilization phase starts > > 2015-07-13 Beta1 release tarball > > * Only critical fixes from this point > > 2015-07-20 Beta2 release tarball > 2015-07-27 Beta3 release tarball > 2015-08-03 EFL 1.15 is Out (First Monday in August) > > What do you folks think about the idea? > > The second topic which makes 1.15 different from other releases is that July > will be a problematic time for 1.15 as I will be offline for 3 weeks in July. > This raises the question how we are going to handle this. It will be the > first three weeks in July which means I would be back for the final release > but would miss most of the stabilization phase. > > Options I see for this: > 1) Extend the merge window for 1.15 about three weeks so we would start > stabilization once I'm back > 2) Count down 1.5 so we finish by end of June > 3) Find someone who is willing to handle merge window close, alpha and beta > stuff. The last one for sure. You shouldn't be pressured to change your life according to E releases, and e releases shouldn't change according to your life. -- Tom. > > > I do not think 1 or 2 are really feasible but I wanted to offer it here for > discussion. My personal preference would be option 3. If someone has the > motivation to do this there is plenty time for me to explain my workflow to > him. > > Any other problems you folks see time wise? > > If I hear nothing else I will consider it fixed towards the end of the week. > > regards > Stefan Schmidt > > > > ------------------------------------------------------------------------------ > BPM Camp - Free Virtual Workshop May 6th at 10am PDT/1PM EDT > Develop your own process in accordance with the BPMN 2 standard > Learn Process modeling best practices with Bonita BPM through live exercises > http://www.bonitasoft.com/be-part-of-it/events/bpm-camp-virtual- event?utm_ > source=Sourceforge_BPM_Camp_5_6_15&utm_medium=email&utm_campaign=VA_SF > _______________________________________________ > enlightenment-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/enlightenment-devel > ------------------------------------------------------------------------------ BPM Camp - Free Virtual Workshop May 6th at 10am PDT/1PM EDT Develop your own process in accordance with the BPMN 2 standard Learn Process modeling best practices with Bonita BPM through live exercises http://www.bonitasoft.com/be-part-of-it/events/bpm-camp-virtual- event?utm_ source=Sourceforge_BPM_Camp_5_6_15&utm_medium=email&utm_campaign=VA_SF _______________________________________________ enlightenment-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
