<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">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">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>