Re: [Synfig-devl] time to 1.0.3 + community call ?

2016-02-12 Thread d . j . a . y 
Yop,

>Hello, Djay!
>
>Thanks for taking bringing this up. ^__^
>
>2016-02-10 14:52 GMT+06:00  :
>> 1) What do you think about engage the process of a bug fix release for the 
>> 1.0.x series ?
>>
>> bug fix :
>> * current file version
>> * guide crash (merge pending)
>> * guide rulers remove
>>
>> enhancement:
>> * appdata
>> * hide all handles alt+0
>> * select param from handle
>> * split tangent indicator
>
>In the current situation I feel reasonable to release 1.2.0, based on
>current master branch.
>I think that master branch is stable enough, so instead of doing two
>releases (1.0.3 and 1.2.0) we can save our time and release only one.
>^__^

>From my side, i don't think master branch is stable enough ... 

We definitively need more test and more fixes (and you know, it's mainly what i 
try to do ... )
Too much new features are not stable/tested enough (brush / bones / several 
dead lock with mutex)
I report some... i miss to report others (i suspect problems with linking / 
export -Parabolic Shoot- with optimized rendering)

I have the regret to say that Synfig (from the dev version point of view) is 
losting the stability it just kept in the previous releases.

>
>In 1.2.0 we will have:
>* Testing version of Cobra (as experimental feature)
>* Lipsync / Papagayo integration
>* New preferences dialogue
>* C++11 compatibility
>* anything else I forgot ^__^

>I believe those features are highly demanded by users and can help
>bring attention to the project.

I believe a very stable synfig with all the feature polished (bones:yes but IK 
? / brush:yes but crash and slow /  ) it already have will kept the 
attention to the project... 

My best ... 

--
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=272487151=/4140
___
Synfig-devl mailing list
Synfig-devl@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/synfig-devl

Re: [Synfig-devl] time to 1.0.3 + community call ?

2016-02-12 Thread Yu Chen 
Hi,

>From a user's perspective, a bug-fixed release 1.0.3 will be very
appreciated. But if there is no one would like to do the job, I can fully
understand it, we have been facing the limited development resources for a
long time. A new release even it is not stable enough is better than no
release.


Cheers!

~ yu

On Fri, Feb 12, 2016 at 8:20 PM,  wrote:

> Yop,
>
> >Hello, Djay!
> >
> >Thanks for taking bringing this up. ^__^
> >
> >2016-02-10 14:52 GMT+06:00  :
> >> 1) What do you think about engage the process of a bug fix release for
> the 1.0.x series ?
> >>
> >> bug fix :
> >> * current file version
> >> * guide crash (merge pending)
> >> * guide rulers remove
> >>
> >> enhancement:
> >> * appdata
> >> * hide all handles alt+0
> >> * select param from handle
> >> * split tangent indicator
> >
> >In the current situation I feel reasonable to release 1.2.0, based on
> >current master branch.
> >I think that master branch is stable enough, so instead of doing two
> >releases (1.0.3 and 1.2.0) we can save our time and release only one.
> >^__^
>
> >From my side, i don't think master branch is stable enough ...
>
> We definitively need more test and more fixes (and you know, it's mainly
> what i try to do ... )
> Too much new features are not stable/tested enough (brush / bones /
> several dead lock with mutex)
> I report some... i miss to report others (i suspect problems with linking
> / export -Parabolic Shoot- with optimized rendering)
>
> I have the regret to say that Synfig (from the dev version point of view)
> is losting the stability it just kept in the previous releases.
>
> >
> >In 1.2.0 we will have:
> >* Testing version of Cobra (as experimental feature)
> >* Lipsync / Papagayo integration
> >* New preferences dialogue
> >* C++11 compatibility
> >* anything else I forgot ^__^
>
> >I believe those features are highly demanded by users and can help
> >bring attention to the project.
>
> I believe a very stable synfig with all the feature polished (bones:yes
> but IK ? / brush:yes but crash and slow /  ) it already have will kept
> the attention to the project...
>
> My best ...
>
>
> --
> Site24x7 APM Insight: Get Deep Visibility into Application Performance
> APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
> Monitor end-to-end web transactions and take corrective actions now
> Troubleshoot faster and improve end-user experience. Signup Now!
> http://pubads.g.doubleclick.net/gampad/clk?id=272487151=/4140
> ___
> Synfig-devl mailing list
> Synfig-devl@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/synfig-devl
>
--
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=272487151=/4140___
Synfig-devl mailing list
Synfig-devl@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/synfig-devl

Re: [Synfig-devl] time to 1.0.3 + community call ?

2016-02-12 Thread Konstantin Dmitriev 
2016-02-12 18:20 GMT+06:00  :
> Yop,
>
>>Hello, Djay!
>>
>>Thanks for taking bringing this up. ^__^
>>
>>2016-02-10 14:52 GMT+06:00  :
>>> 1) What do you think about engage the process of a bug fix release for the 
>>> 1.0.x series ?
>>>
>>> bug fix :
>>> * current file version
>>> * guide crash (merge pending)
>>> * guide rulers remove
>>>
>>> enhancement:
>>> * appdata
>>> * hide all handles alt+0
>>> * select param from handle
>>> * split tangent indicator
>>
>>In the current situation I feel reasonable to release 1.2.0, based on
>>current master branch.
>>I think that master branch is stable enough, so instead of doing two
>>releases (1.0.3 and 1.2.0) we can save our time and release only one.
>>^__^
>
> >From my side, i don't think master branch is stable enough ...
>
> We definitively need more test and more fixes (and you know, it's mainly what 
> i try to do ... )
Yes, your testing work is much appreciated.

> Too much new features are not stable/tested enough (brush / bones / several 
> dead lock with mutex)

Brush functionality is the same as in 1.0.2. In any case, Brus
functionality is still at experimental status. i doubt someone using
it seriously at its current state.

Bones functionality is the same as in 1.0.2.

Whats with mutex?

> I report some... i miss to report others (i suspect problems with linking / 
> export -Parabolic Shoot- with optimized rendering)

Optimized rendering engine (Cobra) is surely unstable. But we don't
force people to use it. They can stick with Legacy.

> I have the regret to say that Synfig (from the dev version point of view) is 
> losting the stability it just kept in the previous releases.

I don't see serious regressions in master. Quite opposite, there are
lot problems resolved, comparing to 1.0.2 or even 1.0.3.

>>In 1.2.0 we will have:
>>* Testing version of Cobra (as experimental feature)
>>* Lipsync / Papagayo integration
>>* New preferences dialogue
>>* C++11 compatibility
>>* anything else I forgot ^__^
>
>>I believe those features are highly demanded by users and can help
>>bring attention to the project.
>
> I believe a very stable synfig with all the feature polished (bones:yes but 
> IK ? / brush:yes but crash and slow /  ) it already have will kept the 
> attention to the project...

Polishing Bones and Brushes will take several months. We don't have
money for that right now.  In fact, even Cobra development is on the
edge And, in any case I prefer to polish those features in master, not
in 1.0,x branch, because otherwise we will have pain with merge.

P.S. BTW, we can't resolve brush speed issues without optimized
rendering engine.

On the other hand, I understand your points. At the moment I am busy
with mentoring Cobra development and managing production of Morevna
Episode 3 (which is a testing ground for Cobra and other software). If
I have time for 1.0.3, then I surely will do. But at the moment I see
that releasing "most what we have now" is a better way to go.

Best Regards,
K.

--
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=272487151=/4140
___
Synfig-devl mailing list
Synfig-devl@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/synfig-devl

Re: [Synfig-devl] time to 1.0.3 + community call ?

2016-02-10 Thread Konstantin Dmitriev 
Hello, Djay!

Thanks for taking bringing this up. ^__^

2016-02-10 14:52 GMT+06:00  :
> 1) What do you think about engage the process of a bug fix release for the 
> 1.0.x series ?
>
> bug fix :
> * current file version
> * guide crash (merge pending)
> * guide rulers remove
>
> enhancement:
> * appdata
> * hide all handles alt+0
> * select param from handle
> * split tangent indicator

In the current situation I feel reasonable to release 1.2.0, based on
current master branch.
I think that master branch is stable enough, so instead of doing two
releases (1.0.3 and 1.2.0) we can save our time and release only one.
^__^

In 1.2.0 we will have:
* Testing version of Cobra (as experimental feature)
* Lipsync / Papagayo integration
* New preferences dialogue
* C++11 compatibility
* anything else I forgot ^__^

I believe those features are highly demanded by users and can help
bring attention to the project.

What would be nice to get finished before release of 1.2.0:
* The choice of rendering engine should be saved in SIF file, not in
preferences of application. I think it's fine to store chosen
rendering engine in file metadata.
* Problem with opening files generated by Inkscape -
http://www.synfig.org/issues/thebuggenie/synfig/issues/883 (the
generated files are ok, but Synfig interprets them in a wrong way).

> 2) What do think to make a community call for helping us ?
>
> * writers and translators for the wiki.
> * a template/style for the forums, and someone who masterize mediawiki for 
> the little update here and there...
> * coders
> * other things i forgot...

Please feel free to write a text for the call and I will be happy to
publish it on the blog. ^__^

Please consider, that the community call would mean that we have
someone who have a time to manage responses to the call. Unfortunately
at this moment I can't afford this. So, it probably would be nice to
make a forum thread for the call, so others can manage responses.


One more thing regarding the 1.2.0 release - we can have a splash
screen challenge, if someone is willing to organize it.

What's needed:
* Write a clear announcement about the splash.
* Make a forum thread and put announcement there.
* Define start and end date.
* Close the call on end date (notify everyone in the forum thread).

Challenge rules:
* Duration - one month.
* I would like to take responsibility for choosing the winner.
* No requirement for particular theme, but it would be nice is splash
will include Parrots (Papagayos) or Cobras. ^__^
* Challenge entry should provided under the following license:
CC-BY-SA (CC-BY or Public Domain or CC-0 also allowed)

Best Regards,
K.

--
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=272487151=/4140
___
Synfig-devl mailing list
Synfig-devl@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/synfig-devl