<HTML><HEAD><META content="text/html; charset=UTF-8" http-equiv="Content-Type"></HEAD><BODY>Awesome.<BR>
<BR>
Could be a good opportunity to revive "Icons for Add-ons" development. Here it is: https://developer.blender.org/D645<BR>
<BR>
Julian Eisel wrote:<BR>
<blockquote type="cite"><BR>
Hey guys!<BR>
<BR>
Today I set up a new branch 'UI-experiments'<BR>
(https://developer.blender.org/diffusion/B/browse/UI-experiments/) so<BR>
we finally have a place where we can test and develop features without<BR>
having to worry about anything (well almost), it's our personal<BR>
playground. I talked about it with Pablo last week and we decided to<BR>
give it a go.<BR>
<BR>
The only three rules I propose:<BR>
- No features from which we know they won't end up in master (rather<BR>
soonish). The purpose of this branch is to develop features towards<BR>
master (this also includes testing). If we don't see someone working<BR>
on a feature for a some months, and we can't see the will to do s
o, we<BR>
simply kick the feature out<BR>
- Features that go in must have an own up-to-date branch (local or<BR>
remote) to make the final merge with master easier. This is in the<BR>
hands of the developer of the feature - he has to prepare the feature<BR>
for final merge, which can be difficult and annoying if you need to do<BR>
it from a branch that is really diverged from master<BR>
- All added features and the people involved must be listed somewhere<BR>
so we can keep track of them easily (wiki page?)<BR>
<BR>
I can take care of the branch by making sure it stays up-to-date with<BR>
master and builds fine (and maybe we can create testbuilds on and<BR>
off).<BR>
<BR>
Curious to hear feedback and to get this running. If we got everything<BR>
organized we can start bombing the branch with features :)<BR>
<BR>
Cheers,<BR>
- Julian -<BR>
_______________________________________________<BR>
Bf-interface mailing list<BR>
Bf-interface@blender.org<BR>
http://lists.blender.org/mai
lman/listinfo/bf-interface<BR>
</BODY></HTML>