Hi Dianjin, Welcome to the community — and thank you for raising this! Your recommendation is a perfect starting point.
You’re absolutely right that most of the current work is happening on the madlib2-master branch. Updating the default branch to reflect this would help reduce confusion for new contributors. You’ll also notice that this project predates the use of .asf.yaml. How about we work together to provide an updated .asf.yaml for the MADlib project? That would let us manage the default branch and other settings directly in the repository going forward. -=e -- Ed Espino Apache Cloudberry (Incubating) & MADlib On Tue, Oct 21, 2025 at 12:20 AM Dianjin Wang <[email protected]> wrote: > Hi all, > > I’d like to bring up a small proposal regarding the default branch > setting on MADlib’s GitHub repository: > https://github.com/apache/madlib. > > Currently, the default branch is master, but it seems that this branch > hasn’t been updated for quite a while, while most of the ongoing work > and updates are happening on the madlib2-master branch. > > To avoid confusion for new contributors or users like me, who might > start from the default branch, I’d like to propose setting > madlib2-master as the default branch on GitHub. > > This change would make it easier for contributors to discover the > latest code and documentation, and help align the repository’s default > branch with the current development workflow. > > What do you think about this proposal? I'm just new here. If there are > specific considerations for keeping master as the default, I’d be > happy to learn more. > > Best, > Dianjin Wang >
