• Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Register
  • Login
UBports Robot Logo UBports Forum
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Register
  • Login

Proposal: The Edge channel

Scheduled Pinned Locked Moved OS
16 Posts 12 Posters 2.3k Views 6 Watching
Loading More Posts
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • A Offline
      arubislander @Marathon2422
      last edited by arubislander 13 Aug 2018, 15:25

      @marathon2422
      Well, I can see the need for a channel that is accessible early in the development cycle, which is stable enough to encourage use, gets updated frequently, but is not yet rc grade stable.
      You would want this channel to be tested as extensively as possible, but frequent breakage might scare off testers.

      On the other hand, testers should know what they are getting into.

      πŸ‡¦πŸ‡Ό πŸ‡³πŸ‡± πŸ‡ΊπŸ‡Έ πŸ‡ͺπŸ‡Έ
      Happily running Ubuntu Touch
      Google Pixel 3a (20.04 DEV)
      JingPad (24.04 preview)
      Meizu Pro 5 (16.04 DEV)

      1 Reply Last reply Reply Quote 1
      • S Offline
        Stefano @UniSuperBox
        last edited by 13 Aug 2018, 15:46

        @unisuperbox Oh, yeah, bring it on. I'll happily test a new devices with such a channel.

        1 Reply Last reply Reply Quote 0
        • M Offline
          mariogrip Administrators
          last edited by 13 Aug 2018, 18:29

          @alan_g The biggest major change is that this channel will be decouple from the ota release cycle and will only be cherry picked into devel (and then follow the release cycle) this is done due to our different types of devices where our older devices does not support newer libhybris just yet, and that way we can pull new libhybris and other major changes (unity8, mir, sensorfw, droidmedia, anbox and etc we want to experiment with) into this edge channel and keep it there to freely develop on without interfering with the normal OTA release cycle that happens at devel->rc->stable. Then the question is, why a channel/rootfs. This is because we want to support halium devices with this channel/rootfs and provide them with an option to download a rootfs that supports halium out of the box without needing to update libhybris etc to get it to boot with our rootfs, and for the channel this allows us to provide community channels using newer libhybris.

          So keyword here is libhybris, we simply cannot bring libhybris in to devel->rc->stable cycle at this point, that would break some of the older devices.

          S 1 Reply Last reply 13 Aug 2018, 18:50 Reply Quote 0
          • M Offline
            mariogrip Administrators
            last edited by 13 Aug 2018, 18:34

            The idea of subchannel is something we got already, but using deb packages instead of full rootfs (we call them "branches"). We also got a tool to install/uninstall these branches. (http://docs.ubports.com/en/latest/about/process/ppa.html)

            1 Reply Last reply Reply Quote 0
            • S Offline
              Stefano @mariogrip
              last edited by 13 Aug 2018, 18:50

              @mariogrip come Marius, we're waiting for Edge channel for Oneplus 3 and Oneplus 5. Let me know once is up and running, I'll test it straight away, same for Anbox.

              1 Reply Last reply Reply Quote 0
              • F Offline
                flohack
                last edited by 13 Aug 2018, 21:02

                I sustain the edge channel @alan_g for a variety of reasons:

                • We are a small team, we cannot guarantee that things being pushed will not break the entire image. We lack auto and manual testing a lot, we cannot work with silos etc.
                • For some scenarios its very cumbersome to having install various packages from various branches at the same time to the phone
                • devel has become actually quite a "stable devel" and we want to keep it as described for the changes where we are sure that they will not break the whole image. People should not expect having to reflash their phones after a devel channel update going wrong.
                • This channel will not be on the phone for people to "just switch" to it.
                • I do not see much issues with yet another channel coming for devs, the low-level devs will use it, but middleware/Ui etc can stay on devel probably.

                BR

                My languages: πŸ‡¦πŸ‡Ή πŸ‡©πŸ‡ͺ πŸ‡¬πŸ‡§ πŸ‡ΊπŸ‡Έ

                D 1 Reply Last reply 15 Aug 2018, 10:06 Reply Quote 1
                • D Offline
                  domubpkm @flohack
                  last edited by 15 Aug 2018, 10:06

                  This post is deleted!
                  A 1 Reply Last reply 15 Aug 2018, 10:44 Reply Quote 0
                  • A Offline
                    advocatux @domubpkm
                    last edited by 15 Aug 2018, 10:44

                    This post is deleted!
                    1 Reply Last reply Reply Quote 0
                    • T Offline
                      ThePossessor
                      last edited by 16 Aug 2018, 21:46

                      From what is being said I understand the following:

                      • Differences are too big to just make a new "edge" channel of existing 16.04. It cannot be mixed with existing devices yet.
                      • Also the way this would interconnect with normal 16.04 devel > rc > stable cycle is unclear

                      A different way to handle it would be make it independently coexist like 15.04 and 16.04 do. A third option 16.04.halium with its own devel > rc > stable cycle could be a way.

                      However since this is not only about halium itself but also other related sub projects this does not completely solve the problem. Maybe for this additionally using the "branches" mentioned by @mariogrip could be a way?

                      1 Reply Last reply Reply Quote 0
                      • M Offline
                        mardy
                        last edited by 17 Aug 2018, 20:49

                        This channel would be useless to me and to many other developers, but if it brings benefits to halium developers, then why not. But then, why not call it "halium", "porters" or some other name that makes it clear what its target audience is?

                        "edge" to me means "more ahead than devel", but there's again the assumption that packages from this channel will eventually end up in "devel", "rc" and "stable"; so, I would suggest a different, more specific name.

                        1 Reply Last reply Reply Quote 2
                        16 out of 16
                        • First post
                          16/16
                          Last post