Today Blender development is moving to a new platform, hosted on projects.blender.org. The move has been announced and documented in several articles and documents, so here we will focus on the expected results of the move.
projects.blender.org is the new platform for bug reporting, task management and code review.
- Bug reports and design tasks have been migrated to projects.blender.org. This includes task status, priority, labels and subscribers.
- User accounts have been migrated to Blender ID. If you had a Blender ID account, the username is now set to the one from the profile there. If you did not, a new Blender ID account was created. Please contact Blender ID support in case of any problems, or reach out through the dedicated chat channel.
- Code reviews and pastes have not been migrated but archived. Pending code reviews need to be resubmitted as pull requests.
- Workboards and project descriptions will be manually recreated by the modules.
New URLs
The Git repositories have changed location. If you have an existing Blender checkout, point to the new location as follows:
git remote set-url origin https://projects.blender.org/blender/blender.gitgit fetch origin maingit submodule syncThe development branch is now named main instead of master. To get the latest changes, switch as follows:
git checkout mainmake updateFor developers:
- For push access to repositories, set the remote url to SSH and re-upload your SSH key.
- Follow the pull request instructions to create a fork.
- Find additional information for developers and module members on devtalk.
The developer.blender.org website is now archived.
- Code reviews and pastes will remain permanently available as static web pages at the same location as before.
- Tasks links are redirected to projects.blender.org. A static archive of tasks is also available on archive.blender.org/developer.
- The developer.blender.org website will remain available as read-only for a few weeks to help in migration, in particular for workboards.
Given the scope of the migration, some data might not have been correctly migrated. If you see an issue, please report it in the comments below.
Congratulations to the migration task force: Arnd, Brecht, Danny, Sergey, and Sybren, with support from Dalai, Thomas, Pablo, and Philipp.
Special thanks to the Gitea project and all the blender.org developers community!
Support the Future of Blender
Donate and support Blender Foundation to work on core Blender development.
I’m no developer, merely an artist and a humble contributor in the realm of UI translation in different languages. And this move was quite confusing. For one because it crept right under my admittedly poor radar. My SVN’s sudden refusals to accept my credentials and commit changes to the repository took me by surprise.
Has anyone already come up with step-by-step instructions for what the translators should do and how to proceed with submitting/committing new translations? And by that I mean a version that a non developer can comprehend and follow? Finding a suitable guide for SVN when I just started out was difficult enough, now this has me scratching my head all over again.
Can anyone help?
Please see here:
https://devtalk.blender.org/t/help-a-translator-with-gitea/27787
The code blocks are broken:
https://projects.blender.org/blender/blender/issues/71420#issuecomment-381259
https://projects.blender.org/blender/blender/issues/81421#issuecomment-281263
Blender made by you on developer.blender.org ?
It’s a pity that on developer.blender.org there is no possibility to send links to
right-click select blender ideas for which the blender developers would consider implementation.
A few issues I have found so far:
I prefer to use the Gitea theme which is light as I prefer it over dark themes, but this leaves the projects.blender.org page looking un-styled.
There is also an area in the bottom right hand corner of the page which contains what looks like a blank version of the Gitea repository page, with functioning tabs and buttons, but no content (I would attach an image if there was a way).
On the mobile version of the site the repository page is still dark despite having selected the Gitea theme and the only way I’ve found a link to sign in was to try and create a new issue. Once I get to the sign-in page the proper white theme is used.
The favicon for the website, a white version of the blender logo, is virtually invisible if you are using a light theme for your web browser.
I also see that the labels for issues were probably only coloured with the dark theme in mind as they look very dull on the light Gitea theme.
Congrates! Look forward to the new bug ticket opening experience :)
Hey All and congrats on the migration! That’s a Big Deal!
Thanks for all your hard work!
In order to prevent spam, comments are closed 15 days after the post is published. Feel free to continue the conversation on the forums.