MayaTheShy/Opus
1
0
Fork 0
Code Issues 4 Pull Requests Actions Packages Projects Releases Wiki Activity

Develop 1.8 #20

Merged
Kan18 merged 242 commits from develop-1.8 into master-1.8 2019-11-10 20:52:08 -05:00
Conversation 4 Commits 242 Files Changed 193 +14776 -11770
Kan18 commented 2019-09-10 19:41:08 -04:00 (Migrated from github.com)
Copy Link

develop 1.8

develop 1.8
Kan18 commented 2019-09-10 19:46:25 -04:00 (Migrated from github.com)
Copy Link

Whoops, I created this PR accidentally. I'll leave it open because I think we need to fix the issue of all the development happening on develop-1.8. Maybe we could have a system where master-1.8 is the recommended version, new features get added to develop-1.8 , and every 10 days we make a pull request from develop-1.8 to master-1.8 with a version number. While we're at it, we might want to add some more configuration to the installer, such as whether to boot into opus shell or Overview the first time, and whether to include UI applications. For this we could create a CLI version of the welcome app, or include the welcome app in the installer. Also, some things shouldn't be installed on every computer, such as 6.tl3.lua, we could have special cases to make the installer detect if the system is a turtle, to save space.

Whoops, I created this PR accidentally. I'll leave it open because I think we need to fix the issue of all the development happening on develop-1.8. Maybe we could have a system where master-1.8 is the recommended version, new features get added to develop-1.8 , and every 10 days we make a pull request from develop-1.8 to master-1.8 with a version number. While we're at it, we might want to add some more configuration to the installer, such as whether to boot into opus shell or Overview the first time, and whether to include UI applications. For this we could create a CLI version of the welcome app, or include the welcome app in the installer. Also, some things shouldn't be installed on every computer, such as 6.tl3.lua, we could have special cases to make the installer detect if the system is a turtle, to save space.
Kan18 commented 2019-09-10 19:47:40 -04:00 (Migrated from github.com)
Copy Link

We could also have a installer that customizes for the user's needs, like early versions of the Mac operating system:
image

We could also have a installer that customizes for the user's needs, like early versions of the Mac operating system: ![image](https://user-images.githubusercontent.com/24967425/64658002-d7155280-d403-11e9-8ed6-c9929e516236.png)
hugeblank commented 2019-09-10 20:14:02 -04:00 (Migrated from github.com)
Copy Link

I disagree with the whole every 10 days we should push to master, I don't think any element of this project should have a time limit to it.

I disagree with the whole every 10 days we should push to master, I don't think any element of this project should have a time limit to it.
Kan18 commented 2019-09-11 19:26:46 -04:00 (Migrated from github.com)
Copy Link

I disagree with the whole every 10 days we should push to master, I don't think any element of this project should have a time limit to it.

The "every 10 days" was just as an example, but what I'm saying is that we should have a "bleeding edge" and "stable" branch where features are first tested in the bleeding-edge branch then moved to stable soon. The accepted standard of using develop-1.8 instead of master-1.8 is very confusing for people.

> I disagree with the whole every 10 days we should push to master, I don't think any element of this project should have a time limit to it. The "every 10 days" was just as an example, but what I'm saying is that we should have a "bleeding edge" and "stable" branch where features are first tested in the bleeding-edge branch then moved to stable soon. The accepted standard of using develop-1.8 instead of master-1.8 is very confusing for people.
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
Clear labels
bug
duplicate
enhancement
help wanted
invalid
question
wontfix
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
MayaTheShy
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: MayaTheShy/Opus#20
Delete Branch "develop-1.8"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?