Group Details Private

Infrastructure

The servers aren't down, your frame of reference is incorrect.

  • RE: semantic versioning for UT

    @alan_g Yes that what i meant, sorry a mistake.

    posted in OS
  • semantic versioning for UT

    With the new idea for changing up OTA process, I also want to propose new version system that makes sense.

    I propose to use Semantic Versioning
    https://semver.org/

    0_1539724648267_c4f00cf3-507c-4db6-bbb8-be949563f74f-image.png

    This way we could completely get rid of framework and only rely on the version to describe both version and api/abi compat. It would also give you a lot more info about the version you are on example that a major bump has a much bigger change then for example patch.

    MAJOR: bigger change that Breaks ABI/API
    MINOR: adds backwards-compatible bug fixes, changes and functionality (may break smaller library ABI in really special cases, but this should be notified about!)
    PATCH: adds backwards-compatible bug fixes.

    Additional labels for pre-release and build metadata are available as extensions to the MAJOR.MINOR.PATCH format.

    This would be how our different channels would look
    1.6.2-beta2 -> 1.6.2-rc1 -> 1.6.2
    beta -> rc -> stable

    This way you would know what version becomes what, example you know that 1.6.2-rc will become 1.6.2 stable.

    This fits great in with the "gotta go fast" proposal by dalton, here is an example how that would work

    1 week:

    • 1.5.6-devel0
    • 1.5.6-devel1
    • ----- / ----- Devel continues like this daily
    • Last weeks rc becomes stable: 1.5.5-rc1 -> 1.5.5
    • Last devel build of the week becomes rc: 1.5.6-devel6 -> 1.5.6-rc1

    2 week:

    • New devel version starts: 1.5.7-devel1
    • Last weeks rc becomes stable: 1.5.6-rc1 -> 1.5.6
    • Last devel build of the week becomes rc: 1.5.7-devel6 -> 1.5.7-rc1
    • This continues weekly.

    Then monthly we do a minor bump with more advances feathers.

    We could also do a mix between slow and fast, where we are releasing stable monthly:
    1 week:

    • 1.5.6-devel0
    • 1.5.6-devel1
    • ----- / ----- Devel continues like this daily
    • Last devel build of the week becomes rc: 1.5.6-devel6 -> 1.5.6-rc1

    2 week:

    • Devel continues daily
    • Last devel build of the week becomes rc: 1.5.6-devel12 -> 1.5.6-rc2
    • This continues weekly

    Then after the month is over last weeks rc becomes stable: 1.5.6-rc1 -> 1.5.6

    Examples:

    xenial stable: 1.6.2
    xenial rc: 1.6.2-rc0
    xenial rc: 1.6.2-rc1
    xenial devel: 1.6.2-devel1
    bionic devel: 2.6.2-devel1

    We would also make a clear build date in settings, this way we can know we are on the latest build.

    posted in OS
  • RE: Unity 8 Open Store In desktop design

    This look really nice :D but it look little too much like google play. But i would love to see a similar design but using more suru design instead of material.

    posted in Design
  • RE: Childlock?

    @guru If you solve it on the App level it can be unblocked again by children e.g. There is no reliable way to block it than on the provider level. Whoever has access to the device will find a way to unblock it, if he or she really wants ;)

    posted in Support
  • RE: Childlock?

    @thomas_ww Please ask your service provider how to block "Mehrwertnummern" :)

    BR

    posted in Support
  • RE: Ubuntu Touch OS Development

    @gauge said in Ubuntu Touch OS Development:

    abandoned

    Abandoned is the right word. We also use dropped sometime ;) - Well yes, a ton of things was left behind: unity8, all phone-specific packages (see our Github org https://github.com/ubports), the SDK + emulator (but maybe not worth fixing, was always broken a bit), the UI toolkit, the click store, the update system, the push server, translation service on top of all, god where I stop? Its not a packing aspect, it was a damn we are left with tons of code and dont know where to start aspect.

    Also we had to set up infrastructure as fast as we could, and some things are still not perfect. But improving daily...

    Well our tracker shows all that we know whats not ok: https://github.com/ubports/ubuntu-touch/issues - feel free to lurk around. Plus all core Apps (= apps that we want to maintain) have their own tracker, just search for -app in the repo search for our Org.

    Other than that we got a thriving Telegram community: https://t.me/ubports - from there you will get instructions to different subgroups.

    Welcome, welcome. The rabbit hole runs deep I used to say.

    BR Florian

    posted in General
  • RE: tg app modifies the photos on send

    "As picture" is being uploaded 1:1 but the server then compresses it. 90% of todays pictures are not worth the high resolution, why I can understand Telegram guys that they want so save space in their cloud. The desktop App makes a difference, but unfortunately on the phone this feature was never implemented. Please file a feature request on the tracker, we might consider it for the new version.

    BR

    posted in Support
  • RE: Childlock?

    Normally its better to block those numbers with your provider, as nobody can block taking out the SIM card and putting it into an unblocked phone etc.

    BR

    posted in Support
  • RE: Ubuntu Touch OS Development

    @dobey wants to say that there are a lot of single projects, where again in turn some of them are unmodified from Ubuntu upstream, in fact we are more like a distro (=collection of independent stuff) with a very special twist to support the phone hardware. Sometimes we replace the upstream package with a different version, and sometimes we add new packages. But a lot of code is identical to desktop actually.

    If you talk about middleware layers, are you talking about daemons providing APIs to clients, the shell itself (which is unity8 and consists also of a ton of code :))? Its a wide area of stuff you can work on, yes.

    BR

    posted in General
  • RE: Old PIN/password screen design.

    @dobey said in Old PIN/password screen design.:

    Mir. I'm not sure if the same issue will happen on 16.04 (the x86 builds are still not in

    Summary: its not easy to modify, and so we leave it currently as it is ;)

    posted in Design

Looks like your connection to UBports Forum was lost, please wait while we try to reconnect.