Thanks very much for all the feedback.
*As a conclusion, based on the above discussions, eagle community
agree consistently to rename "develop" branch to "master" branch as the
main development branch. The action will happen in one or two days.*
- Hao
On Tue, Aug 9, 2016 at 11:43 AM, Liangfei.Su
+1 for master, trunk looks more legacy svn naming.. :)
On Mon, Aug 8, 2016 at 2:29 PM, Edward Zhang
wrote:
> Today master branch is only used for mirroring latest stable release branch
> because in the first impression, people will use master to build and run.
>
> To avoid too many breaks in ma
Today master branch is only used for mirroring latest stable release branch
because in the first impression, people will use master to build and run.
To avoid too many breaks in master branch, Eagle community starts to use
develop branch for bleeding development work.
But that is redundant for mi
+1 to move it to master.
On Sun, Aug 7, 2016 at 8:09 PM, Julian Hyde wrote:
> +1 moving to “trunk” or “master”.
>
> Regarding the name. These days more projects use the name “master” rather
> than “trunk”. (At least, that’s my impression. Hive, for instance, used
> “trunk” when it was primarily
+1 moving to “trunk” or “master”.
Regarding the name. These days more projects use the name “master” rather than
“trunk”. (At least, that’s my impression. Hive, for instance, used “trunk” when
it was primarily svn, and switched to “master” now it’s based on git.) But
frankly either would be fin
I also feel that moving development to “trunk” will be a good thing. Right now,
synchronizing the final release branch to the “trunk” seems to be a redundant
activity. In the release notes, we can always ask the users to use the release
branch and also when we create sub releases, they would be
Sounds good to me, as long as it benefits the project.
On Fri, Aug 5, 2016 at 3:22 PM, Hao Chen wrote:
> Currently we are faced a problem that we can't close the pull request from
> contributors automatically.
>
> When a pull request is merged in develop branch, github could not close the
> pull
Currently we are faced a problem that we can't close the pull request from
contributors automatically.
When a pull request is merged in develop branch, github could not close the
pull request automatically and committers don't have permission to close
the pull request manually on github page, so t
