Closed luislucena16 closed 7 months ago
hey @0xneves please assign this to me, thanks in advance!
Hey @luislucena16
We discussed finishing the current incentives round before a release, which would then split into the development branch. Active issues on top of the main branch will soon cease. Let's leave this chore on standby from now. We scheduled this release for January.
@0xneves
why not use develop
for development in general?
main
should not be used much...
Active issues on top of the main branch will soon cease. We discussed finishing the current incentives round before the release of the development branch. I agree that mature projects should not use the main much. Our project is still a baby, it's not an issue.
right! understood! :)
Hey @luislucena16, now it's time to rise from the ashes and submit the develop branch as you proposed.
okay, I'm going to do it!
I upload a PR and leave it for you to configure the policies?
There is no need for policies, just submit a copy of the main branch named develop. We will move forward on the develop but will keep the main as the default.
yes @0xneves, but remember that I have a fork and I have my develop branch there, I don't have permissions to do it from here
It's okey, I will create the branch them!
Issues will be directed to the develop
branch now.
@0xneves nice!!
develop
branch and assigning it asdefault
for changes, is a best practice and helps to protectmain
branch which would only be used for prod.