<p dir="ltr">I created <a href="https://bugs.webkit.org/show_bug.cgi?id=135487">https://bugs.webkit.org/show_bug.cgi?id=135487</a> to bump ewebkit version.</p>
<p dir="ltr">And, created <a href="https://github.com/ewebkit">https://github.com/ewebkit</a> <br>
If someone want to make changes, please let me know with your github username.<br>
If you also know some patch which is not merged but I should cherry-pick, please let me know.</p>
<p dir="ltr">Thanks for your support.<br>
Ryuan choi<br>
</p>
<div class="gmail_quote">2014. 8. 1. 오전 10:44에 "Cedric BAIL" <<a href="mailto:cedric.bail@free.fr">cedric.bail@free.fr</a>>님이 작성:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hello,<br>
<br>
On Thu, Jul 31, 2014 at 11:39 PM, ryuan Choi <<a href="mailto:ryuan@enlightenment.org">ryuan@enlightenment.org</a>> wrote:<br>
> I need your opinion about first version of ewebkit.<br>
><br>
> ewebkit was always under development without any version.<br>
> (always 0.1.0)<br>
><br>
> Within this state (almost 4 years I joined), we made ewebkit1, made ewebkit2<br>
> and dropped ewebkit1.<br>
> Because I am still newbie, I don't know the level for stable version.<br>
> But, I think that we might not release ewebkit ever if we want more stable<br>
> version.<br>
> About few months, we didn't have any big changes in ewebkit2 interface.<br>
> (Only one big news was dropping ewebkit1)<br>
> Our almost work was following changes of webkit.org.(build fix or<br>
> regression)<br>
><br>
> EFL 1.11 will be released after few days later.<br>
><br>
> So, what do you think about releasing first version of ewebkit as 1.11 (or<br>
> any suggestion?)<br>
><br>
> My simple idea is<br>
> 1. when second merge window of EFL is over, bump the version of ewebkit in<br>
> the webkit trunk(<a href="http://webkit.org" target="_blank">webkit.org</a>)<br>
> 2. sync and fork that to the version branch in github.<br>
> 3. clear some code if needed.<br>
> - disable features which are still unstable or under development.<br>
> - cherry-pick patches which are still under review but very important<br>
> for ewebkit.<br>
> 4. test and fix some critical bugs within last three stabilization phase of<br>
> EFL.<br>
> 5. When new version of EFL is released, tag the version like EFL.<br>
> 6. After released, only hot fix is allowed in the version branch for the<br>
> minor release.<br>
><br>
><br>
> In a short,<br>
> - sync the release process with EFL after second merge window is over.<br>
> - develop the ewebkit in the trunk(<a href="http://webkit.org" target="_blank">webkit.org</a>) always like current sitation.<br>
> - maintain the version branch for the hot fix(crash, ...)<br>
><br>
> What do you think about it?<br>
<br>
You just made my day way better ! It's a very good proposal that I am<br>
all for it. I think we can also all agree here that you are going to<br>
be the release manager for ewebkit. Do you have all the needed access<br>
for doing the release on enlightenment server ?<br>
--<br>
Cedric BAIL<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>
</blockquote></div>