You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Migrate the flutter/flutter repository to use main as the primary development branch/channel #95041
@godofredoc@Hixie currently master is part of our public "API" in the flutter tool in the channel command. Would it make sense to start by introducing master as an "alias" for main in flutter channel so that both flutter channel main and flutter channel master would be valid commands for getting primary development channel? That would allow folks to start to use the proper "main" channel verbiage immediately, and would later make it a non-breaking change to update the underlying git branch name.
@godofredoc@Hixie currently master is part of our public "API" in the flutter tool in the channel command. Would it make sense to start by introducing master as an "alias" for main in flutter channel so that both flutter channel main and flutter channel master would be valid commands for getting primary development channel? That would allow folks to start to use the proper "main" channel verbiage immediately, and would later make it a non-breaking change to update the underlying git branch name.
This makes sense. Then we can have a migration phase where we, for example, update documentation.
We are already mirroring master to main adding the alias may be straightforward. @christopherfujino can you please point to the place where we can make the change?
We are already mirroring master to main adding the alias may be straightforward. @christopherfujino can you please point to the place where we can make the change?
It looks like that command does one of two things (depending on whether or not there is a trailing argument): list available channels (with the _listChannels() method) or change the current channel (with the _switchChannel() method).
In #115388 Godofredo added an alias for master called main, and the two branches are always in sync (the have all the same commits, with all the same hashes, etc). Users can use the two branches interchangeably in git operations (pull, fetch, etc.), and they can switch to the "main" channel instead of the "master" channel with flutter channel. We still have master-api.flutter.dev as a site, but not main-api.flutter.dev for the API docs on that channel.
AFAIK, We do still use master in some of the CI scripts, but @godofredoc and @christopherfujino know more about progress there than I do.
This issue is assigned to @godofredoc but has had no recent status updates. Please consider unassigning this issue if it is not going to be addressed in the near future. This allows people to have a clearer picture of what work is actually planned. Thanks!
This issue was assigned to @godofredoc but has had no status updates in a long time. To remove any ambiguity about whether the issue is being worked on, the assignee was removed.
This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of flutter doctor -v and a minimal reproduction of the issue.
Activity
Hixie commentedon Dec 11, 2021
cc @godofredoc
mit-mit commentedon Aug 30, 2022
@godofredoc @Hixie currently
masteris part of our public "API" in thefluttertool in thechannelcommand. Would it make sense to start by introducingmasteras an "alias" formaininflutter channelso that bothflutter channel mainandflutter channel masterwould be valid commands for getting primary development channel? That would allow folks to start to use the proper "main" channel verbiage immediately, and would later make it a non-breaking change to update the underlying git branch name.christopherfujino commentedon Aug 30, 2022
This makes sense. Then we can have a migration phase where we, for example, update documentation.
godofredoc commentedon Aug 30, 2022
We are already mirroring master to main adding the alias may be straightforward. @christopherfujino can you please point to the place where we can make the change?
christopherfujino commentedon Aug 30, 2022
This is the source for the
flutter channelcommand: https://github.com/flutter/flutter/blob/master/packages/flutter_tools/lib/src/commands/channel.dartIt looks like that command does one of two things (depending on whether or not there is a trailing argument): list available channels (with the
_listChannels()method) or change the current channel (with the_switchChannel()method).It looks like _listChannels() depends on https://github.com/flutter/flutter/blob/master/packages/flutter_tools/lib/src/version.dart#L42
kOfficialChannels, which then depends on https://github.com/flutter/flutter/blob/master/packages/flutter_tools/lib/src/globals.dart#L280kDefaultFrameworkChannelHixie commentedon Sep 6, 2022
Making
mainan alias formasterSGTM.mit-mit commentedon Nov 14, 2022
@godofredoc can we assign this to you wrt. the branch aliasing?
Create a main alias for master channel. (#115388)
Create a main alias for master channel. (flutter#115388)
Create a main alias for master channel. (flutter#115388)
1 remaining item
gspencergoog commentedon Feb 23, 2023
In #115388 Godofredo added an alias for master called main, and the two branches are always in sync (the have all the same commits, with all the same hashes, etc). Users can use the two branches interchangeably in git operations (pull, fetch, etc.), and they can switch to the "main" channel instead of the "master" channel with
flutter channel. We still have master-api.flutter.dev as a site, but not main-api.flutter.dev for the API docs on that channel.AFAIK, We do still use master in some of the CI scripts, but @godofredoc and @christopherfujino know more about progress there than I do.
mit-mit commentedon Feb 24, 2023
Cool, I think we can go ahead with changing the website then? https://github.com/flutter/website/pull/7856/files
@timsneath you asked that we waited until after Flutter Forward; is now OK?
flutter-triage-bot commentedon Jul 14, 2023
This issue is assigned to @godofredoc but has had no recent status updates. Please consider unassigning this issue if it is not going to be addressed in the near future. This allows people to have a clearer picture of what work is actually planned. Thanks!
flutter-triage-bot commentedon Sep 22, 2023
This issue was assigned to @godofredoc but has had no status updates in a long time. To remove any ambiguity about whether the issue is being worked on, the assignee was removed.
guidezpl commentedon Apr 10, 2024
This seems to be a duplicate, closing this issue in favor of the more detailed #121564
github-actions commentedon Apr 24, 2024
This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of
flutter doctor -vand a minimal reproduction of the issue.