Developer forums (C::B DEVELOPMENT STRICTLY!) > Development

It's year 2026, so I think some text like: 2024-2025 can be updated to 2026

(1/1)

ollydbg:
Besides that, I think we need to find a way to switch to git.
I think
1, svn is not suitable to maintain many patches locally.
2, I need to synchonize some code between different PCs, and all PCs are using git.

Currently I use arnholm/codeblocks_sfmirror: Unofficial auto-updated GIT mirror of C::B repo in SourceForge. Does NOT accept patches nor pull requests., but that repo only update once per day, so sometimes, I need to wait one day to re-base my local git. :(

cppuser:
I don't understand the title to be honest.  :-[
But I vote for git, even I am not  a developer for codeblocks yet, I will be one day I hope, I am reading the code to see how it is organized.
I have some ideas to try on codeblocks which I use daily  for my personal development on my projects.
I have used svn older time at work, but I prefer git.

ollydbg:
I mean some text in our code base, such as "copy right 2004 - 2025 Code::Blocks team" like text should be updated to "2004 - 2026".

christo:
I agree that migration to git is a great idea. It  could be a game changer.  svn is not used widely. Git is superior for collaboration by design as well as tools like github or gitlab.

I think moving to github/gitlab could bring in more developers as well, hence more features/ bug fixes. Also it allows us  to upstream local changes easily by creating a pull request instead of creating a patch against an svn trunk version and uploading it to sourceforge via ticket. Now developers are not much familiar with the svn workflow.

 Hi c::b developers, could you please consider moving codeblocks to github/gitlab?

Also it is a nice idea to move to a later version of c++.

Please let me know if I can do any help with these as I would like to help as code::blocks has helped me a lot.

Navigation

[0] Message Index