<font face="trebuchet ms,sans-serif">Yes, my idea is to package the new fork ( </font><a href="https://github.com/canek-pelaez/gnome-shell-extension-weather">https://github.com/canek-pelaez/gnome-shell-extension-weather</a> , <font face="trebuchet ms,sans-serif">compatible only with Gnome 3.6) into the "F-18" and "devel" branches and keep the old one ( </font><a href="https://github.com/Neroth/gnome-shell-extension-weather">https://github.com/Neroth/gnome-shell-extension-weather</a> ,<font face="trebuchet ms,sans-serif"> compatible with Gnome up to 3.4) into the "F-16" and "F-17".</font><div>
<font face="trebuchet ms,sans-serif">By the way, which problems are you talking about? <br></font><br><div class="gmail_quote">2012/10/23 Nicolas Chauvet <span dir="ltr"><<a href="mailto:kwizart@gmail.com" target="_blank">kwizart@gmail.com</a>></span><br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi Mattia,<br>
<br>
You can only package the new fork in F-18 and later.<br>
But it will lead to a problem if you cannot maintain this fork for the<br>
whole F-18 lifetime.<br>
<br>
But F-16 and F-17 are still supposed to be maintained, and if the<br>
software doesn't work well, it is expected that it is fix.<br>
I can also be a previous fork on the software.<br>
<br>
Thx<br>
<br>
Nicolas (kwizart)<br>
<br>
2012/10/21 M.M. <<a href="mailto:hal8600@hotmail.it">hal8600@hotmail.it</a>>:<br>
<div class="HOEnZb"><div class="h5">> Thanks, but my question is: is it enough to just package the new fork into<br>
> the F-18 and devel branches and leave the previous ones unchanged and out-of<br>
> date?<br>
><br>
> 2012/10/20 Ken Dreyer <<a href="mailto:ktdreyer@ktdreyer.com">ktdreyer@ktdreyer.com</a>><br>
>><br>
>> On Sat, Oct 20, 2012 at 1:59 PM, M.M. <<a href="mailto:hal8600@hotmail.it">hal8600@hotmail.it</a>> wrote:<br>
>> > branches only and simply leaving the F-16 and F-17 branches unchanged.<br>
>> > Is this the right approach? If not, how should I behave?<br>
>><br>
>> Has Neroth given up development on his version forever? If so, it<br>
>> sounds sensible to me to switch in RPM Fusion.<br>
>><br>
>> - Ken<br>
>><br>
><br>
<br>
</div></div></blockquote></div><br></div>