devel

devel@lists.apertis.org

1 participants
303 discussions

Apertis 16.09 daily images and release schedule
by Hector Oron 22 Jul '16

22 Jul '16

Hello, Apertis 16.09 is now open for development. Apertis 16.09 is now available via daily builds and from 16.09 repositories: * Images: https://images.apertis.org/daily/16.09/images/ * Repositories: https://repositories.apertis.org/apertis/ The 16.09 release schedule can be found at: * https://wiki.apertis.org/16.09/Release_schedule Best Regards, -- Hector Oron Collabora Ltd Kett House, Station Road, Cambridge CB1 2JH, United Kingdom Telephone: +44 (0)1223 362967 Fax: +44 (0) 1223 351966 ------------------------------------ Visit Collabora on the Web at https://www.collabora.com/ Follow Collabora on Twitter https://twitter.com/collaboraltd ------------------------------------

1 0

Fill in 16.06 release notes!
by Ekaterina Gerasimova 21 Jul '16

21 Jul '16

Hi all, We're coming up to the 16.06 release and it is time to fill in the release notes: https://wiki.apertis.org/16.06/ReleaseNotes Please spend some time this today! Thanks Kat

1 0

Fwd: Debian derivatives census: Apertis: welcome!
by Hector Oron 20 Jun '16

20 Jun '16

FYI -------- Forwarded Message -------- Subject: Debian derivatives census: Apertis: welcome! Date: Sat, 18 Jun 2016 10:23:45 +0800 From: Paul Wise <pabs(a)debian.org> Organization: Debian To: Héctor Orón Martínez <hector.oron(a)collabora.co.uk> CC: debian-derivatives <debian-derivatives(a)lists.debian.org> Hi Hector, I would like to welcome yourself and Apertis to the Debian derivatives census! Would you like to take this opportunity to introduce Apertis to us all? https://wiki.debian.org/Derivatives/Census/Apertis I would encourage you to look at Debian's guidelines for derivatives: https://wiki.debian.org/Derivatives/Guidelines You may want to look at our census QA page, some of the mails from there may apply to Apertis. https://wiki.debian.org/Derivatives/CensusQA You don't appear to be subscribed to the Apertis census page, I've made a few changes to the Apertis census page: https://wiki.debian.org/Derivatives/Census/Apertis?action=info I note that Apertis is based on Ubuntu. Are you planning on a transition to being based on Debian? Some of the Release files in the apt repository for Apertis are missing the Valid-Until header, which allows clients to find out when active network attackers are holding back newer Release files. At minimum, rolling releases and suites containing security updates should have this header. With reprepro you can use the ValidFor config option. https://wiki.debian.org/RepositoryFormat#Date.2CValid-Until There doesn't appear to be a Apertis blog or a blog aggregator for Apertis developers. If these existed they would be syndicated on Planet Debian derivatives and would help the Debian community find out the things that are happening in Apertis. I guess most of the Apertis folks are already Debian developers and have blogs on Planet Debian anyway. http://planet.debian.org/deriv/ I'll see you at DebConf16! I guess we will hear more about Apertis during the derivatives panel or a talk or lightning talk. http://debconf16.debconf.org/ Thanks to Collabora (the Apertis corporate sponsor) for their generous sponsorship of the annual Debian conference. https://debconf16.debconf.org/sponsors/ I would encourage any attendees to volunteer to ensure the continued the success of the annual Debian conference, here are some examples of things that need helpers. https://wiki.debconf.org/wiki/DebConf13/VolunteerCoordination I note there is a Debian pure blend related automotive applications being worked on, have you considered collaborating with them? https://wiki.debian.org/Automotive I note that Apertis uses Xfce, I would encourage you to provide feedback and fixes to the Debian Xfce team. https://wiki.debian.org/Teams/DebianXfceGroup You might want to consider adding DNSSEC and TLSA records to your domains. You might also want to add HSTS headers. Please feel free to circulate this mail within the Apertis team. -- bye, pabs https://wiki.debian.org/PaulWise

1 0

16.06 release changes
by Hector Oron 07 Jun '16

07 Jun '16

Hello, This is a 16.06 release update: - X.org has been dropped from Apertis 16.06 images, Apertis is now using Wayland protocol by default in target and development images. SDK is still using X.org graphic system. < https://wiki.apertis.org/WaylandEvaluation > - Apertis 16.06 release roadmap has slightly changed and we are aiming to release on the following dates: + Soft freeze stage: June 29th, 2016 + Hard freeze stage: July 6th, 2016 + Last day for bug fixes (golden image): July 19th, 2016 + Final release: July 22th, 2016 + Release announcement: July 25th, 2016 < https://wiki.apertis.org/16.06/Release_schedule > - Apertis 16.03 release continues updating for security updates (at least) until 16.06 is released. After that date it is to be evaluated if distro shall be kept therefore continue updating with security updates or dropped from Apertis build infrastructure. - Older releases previous to 16.03 shall be removed from our build infrastructure. Regards, -- Hector Oron Collabora Ltd Kett House, Station Road, Cambridge CB1 2JH, United Kingdom Telephone: +44 (0)1223 362967 Fax: +44 (0) 1223 351966 ------------------------------------ Visit Collabora on the Web at https://www.collabora.com/ Follow Collabora on Twitter https://twitter.com/collaboraltd ------------------------------------

1 0

Apertis infrastructure maintaince window 17:00 - 20:00 CEST today
by Sjoerd Simons 02 May '16

02 May '16

Hey all, The main server on which the Apertis infrastructure is running will be getting some hardware maintaince tonight (central european time). Resulting in some downtime for our various services. As mentioned in the topic, the scheduled window for this maintaince is 17:00 - 20:00 CEST today (May second) however the expected practical downtime should be a lot shorter (expected to be at most 1 hour within that window) -- Sjoerd Simons Collabora Ltd.

1 0

Automated CI checks on patch submissions
by Sjoerd Simons 28 Mar '16

28 Mar '16

Hey all, As some of you may have already noticed, we now have some infrastructure in place to do CI checks on patch submission (not just after patch merging). Currently two CI checks are done for patches to most repositories: * Check commit message: Some simple sanity checks for the commit messages (e.g. valid e-mail addresses used), but mostly to check if the commit either has a signed-off-by or is tagged as RFC (subject starts with RFC:) * build-snapshot: Runs git phab merge of the submitter revision against the current *master* version of the repository and runs a normal build-snapshot build. In both case on success, the build is ticked of in the Build status of the diff details part. On failure a comment with more details on the failure is posted instead. Note that for patches towards 16.03 only we don't do specific builds, but this should be added shortly. -- Sjoerd Simons Collabora Ltd.

1 0

New tags for specific releases
by Sjoerd Simons 25 Mar '16

25 Mar '16

Hey all, As 16.03 is out the door and the development has started for 16.06 a way to differentiate for issues/patches applying to either version is needed. For that two new Tags (also known as projects) in phabricator have been added: * apertis-16.03: For matters concerning 16.03 * apertis-16.06: For matters concerning 16.06 Please tag Tasks/Issues/Patches with the approriate versions as needed using the following guidelines: * No version specific tag: Item is for the current development version (16.06 atm) * apertis-16.03 tag: Item is for 16.03 _only_ * apertis-16.03 and apertis-16.06: Item is for both 16.03 and 16.06 Note that for convenience both are available in short form as #16.03 and #16.06 And ofcourse, as Apertis 16.03 is stable only issues/patches with a high impact should be tagged with that version (smaller issues will only be fixed for 16.06) -- Sjoerd Simons Collabora Ltd.

1 0

Apertis 16.03 available
by Alvaro Soliverez 21 Mar '16

21 Mar '16

Hello All, Apertis 16.03 is now available. You can find a summary of the deliverables at https://wiki.apertis.org/16.03/ReleaseNotes Images are already available for download at https://images.apertis.org/release/16.03/ Best Regards, Alvaro -- Alvaro Soliverez alvaro.soliverez(a)collabora.co.uk Project Manager Collabora Ltd.

1 0

New mailing lists.
by Sjoerd Simons 16 Mar '16

16 Mar '16

Hey all, I've create two new mailinglists (with some initial members): * Packagers - For those respoensible for the debian package of the Apertis distribution, including image building. (Used in the maintainer failed for our various debian packages) * Maintainers - The official maintainers address for the various apertis components. (Used as the maintainer contact address for the apertis components). Apart from these formal usages, these lists will also get the mails from the various jenkins jobs in the near future (e.g. build failures). -- Sjoerd Simons Collabora Ltd.

1 0

Webruntime prototype
by Gustavo Noronha 29 Feb '16

29 Feb '16

Hey, As discussed earlier, I have worked on drafting a design and a prototype for the webruntime. The design is on the wiki: https://wiki.apertis.org/WebRuntime And the prototype, which I named westhall[0], allowed me to already find some weaknesses in the design and also a few issues with seed, the foundation that allows connecting the web engine with GObject. The code is here: https://git.apertis.org/cgit/staging/westhall.git/ There are packages for our customized seed and westhall in OBS already, but the best way to test westhall for the moment is to build your own and run the example (you can install seed from the repository though, libseed-gtk4-dev). This is the example: https://git.apertis.org/cgit/staging/westhall.git/tree/examples/simple.c The example will show a very simple page and has JS code to use native Gio APIs to read your machine's /etc/resolv.conf and show its contents on the page. Next up is prototyping the shared launcher as described in the wiki page. Let me know if you have any questions or criticism! Cheers, [0] not set in stone, of course, the name can be freed for usage in a different module if you wish -- Gustavo Noronha <gustavo.noronha(a)collabora.co.uk> Collabora Ltd.

1 0

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

devel