<div dir="ltr">Hi WebKit/EFL forks,<div><br></div><div>I support Ryuan to release the first official ewebkit2 version within EFL 1.11 release. As ewebkit2 has been developed for a long time along with Tizen webkit development, I think ewebkit2 has necessary features enough to be released.</div>
<div><br></div><div>As the EFL 1.11 will be released at 16th August, we have only 2 weeks to stabilize ewebkit2. So I suggest to do a bug bash until this weekend and make bugs with a prefix. (e.g., [EFL][Release], or please recommend a proper prefix.) This will help us to find a critical bugs in a short time. </div>
<div><br></div><div>BR,</div><div>Jinwoo</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">2014-08-01 6:39 GMT+09:00 ryuan Choi <span dir="ltr"><<a href="mailto:ryuan@enlightenment.org" target="_blank">ryuan@enlightenment.org</a>></span>:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div><div><div>Hi, all<br><br></div><div>I need your opinion about first version of ewebkit.<br><br></div>
ewebkit was always under development without any version.<br></div><div>(always 0.1.0)<br><br></div><div>
Within this state (almost 4 years I joined), we made ewebkit1, made ewebkit2 and dropped ewebkit1.<br></div><div>Because I am still newbie, I don't know the level for stable version.<br></div><div>But, I think that we might not release ewebkit ever if we want more stable version.<br>
About few months, we didn't have any big changes in ewebkit2 interface.<br></div><div>(Only one big news was dropping ewebkit1)<br></div><div>Our almost work was following changes of webkit.org.(build fix or regression)<br>
</div><div><br></div><div>EFL 1.11 will be released after few days later.<br><br></div><div>So, what do you think about releasing first version of ewebkit as 1.11 (or any suggestion?)<br><br></div><div>My simple idea is<br>
</div><div>1. when second merge window of EFL is over, bump the version of ewebkit in the webkit trunk(<a href="http://webkit.org" target="_blank">webkit.org</a>)<br></div><div>2. sync and fork that to the version branch in github.<br>
</div>
<div>3. clear some code if needed.<br></div><div> - disable features which are still unstable or under development.<br></div><div> - cherry-pick patches which are still under review but very important for ewebkit.<br>
</div><div>4. test and fix some critical bugs within last three stabilization phase of EFL.<br></div><div>5. When new version of EFL is released, tag the version like EFL.<br></div><div>6. After released, only hot fix is allowed in the version branch for the minor release.<br>
<br><br></div><div>In a short, <br>- sync the release process with EFL after second merge window is over.<br></div><div>- develop the ewebkit in the trunk(<a href="http://webkit.org" target="_blank">webkit.org</a>) always like current sitation.<br>
</div><div>- maintain the version branch for the hot fix(crash, ...)<br><br></div><div>What do you think about it?<br><br></div><div>Best Regards,<br></div><div>Ryuan Choi<br></div></div></div>
<br>_______________________________________________<br>
webkit-efl mailing list<br>
<a href="mailto:webkit-efl@lists.webkit.org">webkit-efl@lists.webkit.org</a><br>
<a href="https://lists.webkit.org/mailman/listinfo/webkit-efl" target="_blank">https://lists.webkit.org/mailman/listinfo/webkit-efl</a><br>
<br></blockquote></div><br></div>