The developers are back from the conference and projects have restarted again! Main focus: the new GIT development environment.
Ton Roosendaal writes:
Hi all,
Here are the notes from today's meeting in irc.freenode.net, #blendercoders.
1) Blender 2.69 release review
- No showstoppers reported. Seems our new Release Candidate scheduling is paying off now. :)
2) Migration to git and upgrade of projects site
- People can see the WIP git server here. Warning!!! This repo and all the hashes may change still, use for testing only.
- New projects website will be here: http://developer.blender.org/. That url will show something in a couple of days). Sneak peek! Full planning is here in wiki.
- The migration team thinks we can have something work within a week! Of course, a nice friendly svn-to-git doc for Blender developers will be in wiki before we migrate officially. (My personal vote is for a git migration video with Campbell Barton!).
3) Current projects
- Sergey Sharybin: works on a switch option to regular Beziers in mask editing
- Still too many bugs in tracker. All BF/BI devs who don't do git migration will keep having focus on managing issues in tracker.
14 Comments
I just used 2.69 for a rushed movie editing job this weekend. It didn't crash on me once. So thanks guys.
That new dev website is looking really good
Right-click vs Left-Click? Ctrl-c vs Shift-d?
Word processors use left-click to set the insertion point. Blender uses it to set the 3D cursor, which is its equivalent of (among other things) the insertion point.
You got a problem with that?
Blender is not word processor.
Go to User Preferences - Input and setup your own hotkey configuration.
@Nomster: it doesn't work that simply. Not all functions are compatible with right click selection.
Hey folks, please don't hijack this post for another UI discussion. The place for that is here:
http://www.blendernation.com/2013/10/17/new-blender-ui-proposal/
Enjoy! :)
Hmm, I understand that commit hashes might not match, but wonder why tree hashes would be different. Compare http://git.blender.org/gitweb/gitweb.cgi/blender.git/commit/b9339d2e42a5d40e825d8a85f2d9c4d65b79d592 with my mirror https://github.com/ldo/blender-main/commit/4c3ba07c8fb6fe991a50a70079d5ea7b4534393d : the before/after file hashes are the same, but the tree hash is not.
Can’t wait for the switchover to Git. Hopefully we should see the following changes:
* More rapid merging of new features into the master branch. Since merging can be done more easily, why not do it more often, so features do not have to be completely nailed down and stable before the first merge.
* Separate stable releases out into their own branches. That way they can continue to receive bugfixes in parallel with master, but not new features. Of course, all bugfixes should also be merged into master.
* I’d like to see some official Blender repo on GitHub, so that I can identify my copy as a fork from that. By all means let the Blender Foundation run its own central Git server as the ultimate authoritative source for the (ahem) source, but I think it’s also worthwhile to maintain a presence on social-coding sites like GitHub and Gitorious.
That looks really nice.
This is looking great. Phabricator is really going to tie all of the disperate areas together nicely.
I wonder if I’ll be able to post links to items here on BlenderNation?
What do you mean, exactly?