Hi! 2012/12/28 Carlos López González <[email protected]>: > Hi! > I think it is time to collect the current modifications of the code and > gather all together with a new release. > Unless someone thinks differently I believe that again, this time will be a > minor release (no new splash) > . > This is what I remember from memory that should be put on the new release: > > Jcome's new renaming modifications. > Diego's tool revamp with Boost libraries. > A small patch form mine that allows to render last frame as user option, > plus two other killed bugs already on master. > Plugins pull request from morevnaproject. > Fix of crash when tree view is selected, currently worked by Zelgadis. > Anything else?
There is also "Disable keyframe" feature from morevnaproject. It needs to be worked out to resolve crash for packaged version. I hope to find time to fix it. > The Cairo render is not ready yet to use. If someone is interested on play > with it just clone the branch and build your own. I won't provide universal > binaries for the moment. > > For this release I would like to delegate the responsibility of lead the > release procedure to someone else. I would have find time to tests the > branches and the pull requests and request back modifications if something > is not working properly or the proposed patch doesn't fit reasonably well. > The rest of release tasks would be driven from some of you. > Meanwhile I will continue working on Cairo render until it is somehow > usable. I hope to find time for making release procedure. Though, I'm not competent to do a code review - so I will need your help here. > In other terms of things, considering that the new bug tracker is running, I > think that it is time to migrate to github too. It would allow us to start > using the commit language to link bugs to the tracker. > For that I would like to know if it is possible to enable the issue tracker > VCS integration to be used in conjunction with github. I would like to be > able to do some test with real fire (add some dummy bugs and file dummy > code commits for them to test that feature). The VCS integration for github is already enabled. More information here: http://issues.thebuggenie.com/wiki/VCSIntegration#article_131_toc_8 ("Using the module" section). > Any other precaution before migrate to github? (I currently maintain the two > repositories but we should start to use github as official one instead of as > mirror of the SF one) > > Also, related to github repository and the new bug tracker I propose to > develop a code managing rules using their facilities: > 1) All code patches should be sent using github pull request. > 2) The Synfig project staff would review the code using github and the code > specific communication > will be hold using github. > 3) Once it is reviewed it can be filed an issue at the new tracker to allow > one responsible to merge it to master branch when possible. > > Does anyone have other ideas for that? I would make step (3) an optional. If the issue is already fixed then filing a new one in the tracker is not needed. We creating issues in bugtracker to not forget them. Why filing the new issue when it's already fixed? Considering our limited manpower I would like to avoid extra bureaucracy here. K. -- http://morevnaproject.org/ ------------------------------------------------------------------------------ Master HTML5, CSS3, ASP.NET, MVC, AJAX, Knockout.js, Web API and much more. Get web development skills now with LearnDevNow - 350+ hours of step-by-step video tutorials by Microsoft MVPs and experts. SALE $99.99 this month only -- learn more at: http://p.sf.net/sfu/learnmore_122812 _______________________________________________ Synfig-devl mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/synfig-devl
