Now I can see the `madlib2-master` has been set as the default branch. 👍


Best,
Dianjin Wang

On Wed, Oct 22, 2025 at 2:52 PM Dianjin Wang <[email protected]> wrote:
>
> The PR on .asf.yaml file is here: https://github.com/apache/madlib/pull/628.
> Love to have your feedback.
>
>
> Best,
> Dianjin Wang
>
> On Tue, Oct 21, 2025 at 5:32 PM Max Yang <[email protected]> wrote:
> >
> > Hi,
> >
> > A PR has been created to support Apache Cloudberry:
> > https://github.com/apache/madlib/pull/627 .
> >
> > Best regards, Max Yang
> >
> >
> > On Tue, Oct 21, 2025 at 4:49 PM Ed Espino <[email protected]> wrote:
> >
> > > Thanks Dianjin,
> > >
> > > I have created Jira: "Change the default branch of the Apache MADlib 
> > > github
> > > repo from master to madlib2-master" (
> > > https://issues.apache.org/jira/browse/INFRA-27348)
> > >
> > > -=e
> > >
> > > On Tue, Oct 21, 2025 at 1:20 AM Dianjin Wang <[email protected]>
> > > wrote:
> > >
> > > > Hi,
> > > >
> > > > We might need to create an Infra Jira ticket to request the Infra team
> > > > to help change the default branch -
> > > >
> > > >
> > > https://github.com/apache/infrastructure-asfyaml/blob/main/README.md#default-branch
> > > > .
> > > >
> > > > For the `.asf.yaml`, I can create a draft PR later for the review.
> > > >
> > > > Best,
> > > > Dianjin Wang
> > > >
> > > > On Tue, Oct 21, 2025 at 3:47 PM Ed Espino <[email protected]> wrote:
> > > > >
> > > > > 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
> > > > > >
> > > >
> > >

Reply via email to