devel April 2024

devel@lists.centos.org

11 participants
11 discussions

Missing openjdk CentOS 7 packages for RHSA-2024:1817
by Chris Schanzle 26 Apr '24

26 Apr '24

With regards to RHSA-2024:1817 <https://access.redhat.com/errata/RHSA-2024:1817>, will there be CentOS 7 packages for the openjdk update released? That is, packages built from java-1.8.0-openjdk-1.8.0.412.b08-1.el7_9.src.rpm I do see https://git.centos.org/rpms/java-1.8.0-openjdk/releases Where it states "import java-1.8.0-openjdk-1.8.0.412.b08-1.el7_9 • 9 days ago". No packages at https://mirror.centos.org/centos-7/7.9.2009/updates/x86_64/Packages/ Thanks, Chris

1 0

RDO Caracal 2024.1 Released
by Amy Marrich 24 Apr '24

24 Apr '24

RDO Caracal 2024.1 Released The RDO community is pleased to announce the general availability of the RDO build for OpenStack 2024.1 Caracal for RPM-based distributions, CentOS Stream and Red Hat Enterprise Linux. RDO is suitable for building private, public, and hybrid clouds. Caracal is the 29th release from the OpenStack project, which is the work of more than 1,000 contributors from around the world. The release is already available for CentOS Stream 9 on the CentOS mirror network in: http://mirror.stream.centos.org/SIGs/9-stream/cloud/x86_64/openstack-caraca… The RDO community project curates, packages, builds, tests and maintains a complete OpenStack component set for RHEL and CentOS Stream and is a member of the CentOS Cloud SIG. The Cloud SIG focuses on delivering a great user experience for CentOS users looking to build and maintain their own on-premise, public or hybrid clouds. All work on RDO and on the downstream release, Red Hat OpenStack Platform, is 100% open source, with all code changes going upstream first. The highlights of the broader upstream OpenStack project may be read via https://releases.openstack.org/caracal/highlights.html but here are some highlights: - Drivers with inactive CI were marked unsupported including Windows iSCSI Driver, Windows SMB Driver, Dell SC Series Storage Driver (iSCSI, FC), Dell VNX Storage Driver (FC, iSCSI) and Dell XtremeIO Storage Driver (iSCSI, FC). - New driver features were added, notably, Fujitsu ETERNUS DX extend volume on RAID group, Pure Storage synchronous replication, NetApp iSCSI LUN space allocation, Dell PowerFlex Active-Active support, Dell PowerMax configurable SRDF snapshots. - Designate now supports Catalog Zones (RFC 9432). This can improve the scalability of Designate pools managing a large number of zones and significantly reduce the provisioning time when adding additional DNS servers to a Designate pool. - Horizon now uses Django 4.2 as default and dropped Django 3.2 support. - Ironic has enabled RBAC support by default by changing the default values of [oslo_policy]enforce_scope and [oslo_policy]enforce_new_defaults to True. Additionally, we added [DEFAULT]rbac_service_project_name to define a project where users in that project are treated as having a service role. Please see Ironic release notes for full details. - Ironic has added the ability to drain active tasks from a conductor before shutdown. Sending a SIGUSR2 signal to an ironic-conductor will now attempt to complete running tasks with a timeout of [DEFAULT]drain_shutdown_timeout. No new tasks will be started on the conductor while it’s draining. - Support was added for the external-gateway-multihoming API extension. The L3 service plugins supporting it can now create multiple gateway ports per router. It is currently limited to the L3 OVN plugin. OpenStack Caracal is marked as Skip Level Upgrade Release Process or SLURP. According to this model ( https://governance.openstack.org/tc/resolutions/20220210-release-cadence-ad…) this means that upgrades will only be supported from the Antelope 2023.1 release. RDO Caracal 2024.1 has been built and tested with the recently released Ceph 18.2.0 Reef version (https://docs.ceph.com/en/latest/releases/reef/) which has been published by the CentOS Storage SIG in the official CentOS repositories. *Note:* Follow the instructions in [RDO documentation]( https://www.rdoproject.org/install/install-with-ceph/) to install OpenStack and Ceph services in the same host. During Caracal cycle, some projects have been retired or declared inactive upstream. As such, the following packages for some projects are not present in the RDO Caracal 2024.1 release: - cinderlib - dib-utils - ec2api-tempest-plugin - ec2api - murano - murano-agent - muranoclient - murano-dashboard - murano-tempest-plugin - sahara - sahara-dashboard - sahara-image-elements - sahara-plugin-ambari - sahara-plugin-cdh - sahara-plugin-mapr - sahara-plugin-spark - sahara-plugin-storm - sahara-plugin-vanilla - sahara-tests - senlin - senlinclient - puppet-ec2api - puppet-etcd - puppet-haproxy - puppet-module-data - puppet-murano - puppet-qdr - puppet-rsyslog - puppet-sahara During the next release we will continue working on retiring inactive packages in order to ensure RDO content quality and security. Contributors: - During the Caracal cycle, we saw the following new RDO contributors: - Marihan Girgis - Balazs Gibizer - Fiorella Yanac Welcome to all of you and Thank You So Much for participating! But we wouldn’t want to overlook anyone. A super massive Thank You to all 47 contributors who participated in producing this release. This list includes commits to rdo-packages, rdo-infra, and rdo-website repositories: - Ade Lee - Alfredo Moralejo Alonso - Amy Marrich (spotz) - Arx Cruz - Balazs Gibizer - Bernard Cafarelli - Bohdan Dobrelia - Chandan Kumar - Cyril Roelandt - Daniel Pawlik - Douglas Viroel - Emma Foley - Fabricio Aguiar - Fiorella Yanac - Gregory Thiemonge - Grzegorz Grasza - Harald Jensås - Jiří Podivín - Joan Francesc Gilabert - Joel Capitao - Karolina Kula - Lewis Denny - Lon Hohberger - Luigi Toscano - Luis Tomas Bolivar - Lukáš Piwowarski - Maor Blaustein - Marihan Girgis - Marios Andreou - Martin Kopec - Martin Magr - Mathieu Bultel - Michael Johnson - Nate Johnston - Pablo Rodríguez Nava - Priscila Gutierres - Rabi Mishra - Roberto Alfieri - Ronelle Landy - Shreshtha Joshi - Soniya Vyas - Szymon Datko - Takashi Kajinami - Tobias Urdin - Tristan De Cacqueray - Yatin Karel - Zane Bitter The Next Release Cycle At the end of one release, focus shifts immediately to the next release i.e Dalmatian. Get Started To spin up a proof of concept cloud, quickly, and on limited hardware, try an All-In-One Packstack installation. You can run RDO on a single node to get a feel for how it works. For those that do not have any hardware or physical resources, there is the OpenStack Global Passport Program. This is a collaborative effort between OpenStack public cloud providers to let you experience the freedom, performance and interoperability of open source infrastructure. You can quickly and easily gain access to OpenStack infrastructure via trial programs from participating OpenStack public cloud providers around the world. Get Help The RDO Project has our users(a)lists.rdoproject.org for RDO-specific users and operators. For more developer-oriented content we recommend joining the dev(a)lists.rdoproject.org mailing list. Remember to post a brief introduction about yourself and your RDO story. The mailing lists archives are all available at https://mail.rdoproject.org. You can also find extensive documentation on RDOproject.org. The #rdo channel on OFTC IRC is also an excellent place to find and give help. We also welcome comments and requests on the CentOS devel mailing list and the CentOS IRC channels (#centos, #centos-cloud, #centos-devel in Libera.Chat network), however we have a more focused audience within the RDO venues. Get Involved To get involved in the OpenStack RPM packaging effort, check out the RDO contribute pages, peruse the CentOS Cloud SIG page, and inhale the RDO packaging documentation. Join us in #rdo and on the OFTC IRC network and follow us on Twitter @RDOCommunity. You can also find us on Facebook and YouTube. *Amy Marrich* She/Her/Hers Principal Technical Marketing Manager - Cloud Platforms Red Hat, Inc <https://www.redhat.com/> amy(a)redhat.com Mobile: 954-818-0514 Slack: amarrich IRC: spotz

1 0

CentOS Stream 8 - end of life plan - end of May 2024
by Adam Samalik 23 Apr '24

23 Apr '24

Hey everyone, I'd like to share our (CentOS Stream Team at Red Hat & CentOS Infrastructure SIG) plan for the CentOS Stream 8 end of life at the end of May 2024. [1] This is the first time a CentOS Stream release reaches its end of life. So this is new to us. But we'll follow some of the established practices from previous CentOS Linux releases where we can. Timeline: The end of life is at the end of May. We'll give all builds time to finish and get to the last release. So everything I'm describing below will happen at the beginning of June. There are five major parts: 1. Released content — repositories, images, etc. 2. Builds in Koji 3. Websites 4. Buildroots in CBS 5. Sources - this part is weird, because sources will keep being updated for the life of RHEL 8, that means even after the CentOS Stream 8 end of life. Released content will get moved to vault.centos.org. Builds in Koji will remain accessible the same way. We'll just internally move them to a less highly available storage as we won't need that anymore for c8s. We'll disable c8s builds entirely in Koji. However, since only RHEL engineers can build CentOS Stream, this will be invisible from a CentOS perspective. Websites will get updated to no longer reference CentOS Stream 8 as available for download, etc. CentOS Stream 8 buildroots in CBS will be disabled. However, SIGs are able to build against RHEL 8 instead. Sources will keep being updated as mentioned. And that's it. That will be the end of CentOS Stream 8. The first CentOS Stream that reaches its end. And from its ashes CentOS Stream 10 is gonna rise. Except it's software, so hopefully no ashes, and the timing might be a little out of sync on those as well. Anyway! Thanks to everyone who used or even contributed to CentOS Stream 8! Cheers, Adam Samalik [1] Original announcement: https://blog.centos.org/2023/04/end-dates-are-coming-for-centos-stream-8-an… -- Adam Samalik --------------------------- Principal Software Engineer Red Hat

2 1

CentOS 7/8s EOL : infrastructure impacts (please read)
by Fabian Arrotin 16 Apr '24

16 Apr '24

Hi all, As you're all aware (we sent multiple mails in the last year about this), CentOS 7 and Stream 8 will go EOL soon : https://blog.centos.org/2023/04/end-dates-are-coming-for-centos-stream-8-an… Let's lists some things that will happen on the CentOS Infrastructure as we'll be approching (or passed) these dates : # CentOS 7/8s content itself Usual process : content will be archived to https://vault.centos.org and removed from mirror.centos.org completely, with just a simple readme file dropped here (for example http://mirror.centos.org/centos/8/readme for already EOL'ed version). Worth knowing that some SIGs are still building for RHEL8, still supported for SIGs through https://cbs.centos.org so such kind of content will continue to be available there as long as SIGs can build against/for it # CBS/koji (https://cbs.centos.org) No impact on CBS env itself ( not running centos 7 nor 8s for a long time now) but the various build tag reflecting centos 7 and 8s will be locked so that nobody would be able to build content anymore : that would even be impossible as content itself will have been removed from mirror.centos.org (internally used for cbs build tags) # CentOS Forums (https://forums.centos.org) : still running on centos 7 and even if that's easy to migrate to newer/supported EL version, it was decided to just shutdown the service (based on discussion with the actual moderation team). An option (to be announced on forums.centos.org ?) is to eventually start moving thread/discussions on Fedora discourse (There is already a CentOS category there : https://discussion.fedoraproject.org/c/neighbors/centos/71) So the plan is just to shutdown forums.centos.org and remove A/AAAA records from DNS # mirrorlist.centos.org service : Starting from Stream 9 (and above), deployed CentOS instance ares using Fedora infra mirrormanager instance for metalink= instead of mirrorlist= in .repo files. We'll just decommission our mirror crawler (also running with a mix of perl/python2 code), so not validating any mirror for legacy/EOL releases. mirrorlist.centos.org A/AAAA records will be removed in the following weeks after c7 will be EOL'ed. That means that people still running CentOS 7 or 8-stream will not have functional yum/dnf stack, except if they point to either vault or have internal mirror but at least people would be aware that distro itself is EOL and that they shouldn't expect to receive any update anymore # CentOS mailing-lists Currently running on mailman2 stack, on top of CentOS 7 linux : there is WIP to port everything to up2date mailman3 stack, actually packaged for EPEL9. We have successfully imported archives into mailman3 and same for lists config but let's start a different/separate thread to discuss changes (like renaming lists, see next coming thread) Kind Regards, -- Fabian Arrotin The CentOS Project | https://www.centos.org gpg key: 17F3B7A1 | @arrfab[@fosstodon.org]

2 7

Re: Making the redhat selinux-policy repository publicly available
by Daan De Meyer 15 Apr '24

15 Apr '24

Thanks for implementing this! Daan On Mon, 15 Apr 2024 at 16:39, Zdenek Pytela <zpytela(a)redhat.com> wrote: > > > > On Fri, Jul 14, 2023 at 11:48 AM Daan De Meyer <daan.j.demeyer(a)gmail.com> wrote: >> >> > To get just the latest repository content, steps described by Troy should work. Additionally, most of the upstream work is done in Fedora and anyway every new commit should go to Fedora first, RHEL content is mostly a subset of Fedora, there are very few differences. >> >> Yes, but the differences might be crucial so it'd be great if we could >> look at the repository containing the actual policy used in centos as >> well. > > I did not oppose the arguments, just commented on the current state and what was possible that time. > > Anyway, the change eventually happened and there is the c9s branch in the fedora-selinux/selinux-policy repository now. > Thanks everybody for your patience. > > https://github.com/fedora-selinux/selinux-policy/tree/c9s > > >> >> >> Cheers, >> >> Daan >> >> On Wed, 12 Jul 2023 at 16:16, Zdenek Pytela <zpytela(a)redhat.com> wrote: >> > >> > >> > >> > On Tue, Jul 11, 2023 at 10:37 PM Troy Dawson <tdawson(a)redhat.com> wrote: >> >> >> >> On Tue, Jul 11, 2023 at 12:50 PM Neal Gompa <ngompa13(a)gmail.com> wrote: >> >>> >> >>> On Tue, Jul 11, 2023 at 9:31 AM Troy Dawson <tdawson(a)redhat.com> wrote: >> >>> > >> >>> > On Tue, Jul 11, 2023 at 4:28 AM Daan De Meyer <daan.j.demeyer(a)gmail.com> wrote: >> >>> >> >> >>> >> Hi, >> >>> >> >> >>> >> It seems that the selinux-policy rpm is built from >> >>> >> git@gitlab.cee.redhat.com:SELinux/selinux-policy.git which seems to be >> >>> >> a redhat internal repository. More specifically, if I try to checkout >> >>> >> the commit listed in the selinux-policy spec >> >>> >> (https://gitlab.com/redhat/centos-stream/rpms/selinux-policy/-/blob/c9s/seli…) >> >>> >> in the fedora-selinux repository cloned from github, I get an error >> >>> >> saying that the commit does not exist. It would be great if the >> >>> >> repository containing this commit was publicly available and open for >> >>> >> external contributors just like all the other packages in CentOS >> >>> >> Stream. Is it possible to make this happen? >> >>> > >> >>> > >> >>> > I'm not the selinux-policy maintainer, so I can't comment on where they work on the selinux-policy source code. >> >>> > >> >>> > But this is how I get the sources, if that is what you are ultimately looking for. >> >>> > >> >>> > centpkg clone selinux-policy >> >>> > cd selinux-policy >> >>> > centpkg sources >> >>> > or if you want to know where they really are >> >>> > centpkg -v sources >> >>> > This shows it to be coming from >> >>> > https://sources.stream.centos.org/sources/rpms/selinux-policy/selinux-polic… >> >>> > >> >>> > The sources information is found in the sources file >> >>> > https://gitlab.com/redhat/centos-stream/rpms/selinux-policy/-/blob/c9s/sour… >> >>> > >> >>> > I know this isn't exactly what you asked for, but I hope it still helps. >> >>> > >> >>> >> >>> I think the idea is that having the Git repository in a public >> >>> location would allow the CentOS Hyperscale SIG to contribute to the >> >>> SELinux policy in a meaningful way. >> >> >> >> >> >> Ah, ok. That makes sense. >> >> As I said, I'm not the maintainer so I don't know why it's where it is. So I'll step out of the conversation. >> > >> > >> > Hi, >> > >> > I am one of the selinux-policy maintainers. Currently, repository for Fedora is at github.com and RHEL sources are in an internal repo. We have already discussed moving centos stream sources to some of the public repositories, but it did not happen. Currently we are discussing it again, there are a few options how to do so. >> > >> > To get just the latest repository content, steps described by Troy should work. Additionally, most of the upstream work is done in Fedora and anyway every new commit should go to Fedora first, RHEL content is mostly a subset of Fedora, there are very few differences. >> > >> > -- >> > >> > Zdenek Pytela >> > Security SELinux team >> > _______________________________________________ >> > selinux mailing list -- selinux(a)lists.fedoraproject.org >> > To unsubscribe send an email to selinux-leave(a)lists.fedoraproject.org >> > Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ >> > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines >> > List Archives: https://lists.fedoraproject.org/archives/list/selinux@lists.fedoraproject.o… >> > Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue >> > > > -- > > Zdenek Pytela > Security SELinux team

1 0

Retiring Config Management SIG
by Shaun McCance 12 Apr '24

12 Apr '24

Hi all, The CentOS Board periodically reviews SIGs to ensure they're active. The Config Management SIG is no longer active, and so we intend to retire this SIG unless somebody from the community wants to revive it. The Config Management SIG was responsible for packaging open source configuration management tools like Ansible, Puppet, and Chef. Thanks, Shaun

1 0

CentOS Cloud SIG meeting minutes (2024-04-11)
by Joel Capitao 11 Apr '24

11 Apr '24

====================================================== #centos-meeting: CentOS Cloud SIG meeting (2024-04-11) ====================================================== Meeting started by jcapitao at 15:01:03 UTC. The full logs are available athttps://www.centos.org/minutes/2024/April/centos-meeting.2024-04-11-15.01… . Meeting summary --------------- * roll call (jcapitao, 15:01:29) * RDO/OpenStack Update (jcapitao, 15:08:43) * RDO is about to release RDO Caracal/2024.1 in a week or so (jcapitao, 15:09:36) * CentOS Stream 8 repos for RDO Releases up to Yoga will be removed and archived in vault.centos.org (jcapitao, 15:44:30) * LINK: https://lists.rdoproject.org/archives/list/dev@lists.rdoproject.org/thread/… (jcapitao, 15:44:51) Meeting ended at 15:52:26 UTC. Action Items ------------ Action Items, by person ----------------------- * **UNASSIGNED** * (none) People Present (lines said) --------------------------- * jcapitao (28) * amoralej (15) * spotz (10) * centguard (5) Generated by `MeetBot`_ 0.4 .. _`MeetBot`: http://wiki.debian.org/MeetBot

1 0

2024-04-10 - CentOS Public Board Meeting
by Thomas Oulevey 09 Apr '24

09 Apr '24

Hi Everyone, Our next board meeting will take place at 20:00 UTC tomorrow `date -d "2024-04-10 20:00 UTC"` If you would like to attend please send me an email to alphacc(a)centosproject.org ( please do not reply to @centos-devel or use another email address) and you will receive a link to a meeting room with a passcode, 1 hour before the meeting takes place. The agenda can be checked at (work in progress) : https://hackmd.io/@centosboard/r1hmwXxe0 As a reminder we will enforce few rules : * Wait to be recognized by the Chair before speaking * Respect the Chair when told your time to speak is over - this will allow us to remain on agenda, and complete the meetings in the allotted time * In the event that there are Board-confidential topics, these will be put at the end of the meeting, in Executive Session, and guests will be asked to leave. We hope to minimize these items, but they do sometimes happen. The most common scenarios in which this may happen are personnel issues, or information that Red Hat wishes to share with the Board, but is not yet public. * Muting of participants, or, in extreme situations, ejection from the meeting, is at the sole discretion of the Chair. * Meetings will be recorded, and published to YouTube (possibly with edits/redaction, as approved by the Directors). Thus, by joining the meeting you consent to have your presence at the meeting, and anything you say during the meeting, made public. I hope some of you can join. thanks, -- Thomas 'alphacc' Oulevey CentOS Board of Directors Secretary alphacc(a)centosproject.org

1 0

[Infra] - Planned outage : lists.centos.org (migration to mailman3) : please read
by Fabian Arrotin 08 Apr '24

08 Apr '24

Due to a needed upgrade , we'll have to move the existing CentOS mailman instance (aka https://lists.centos.org) to a new server/host. Migration is scheduled for """"Tuesday April 8th, 7:00 am UTC time"""". You can convert to local time with $(date -d '2024-04-08 07:00 UTC') The expected "downtime" is estimated to ~60 minutes , time needed to : - take last mailman2 backup - reimport / convert mailman2 archives to mailman3 DB - DNS propagation for A/AAAA/MX records Here are also some important information about the mailman2 => mailman3 migration : # Renamed lists Worth knowing that, based on open discussion on the centos-devel list (see whole thread at https://lists.centos.org/pipermail/centos-devel/2024-March/165576.html), existing lists will be *renamed* , so while we'll put aliases for incoming mails, each list member will start receiving list mails from new list name. So start updating your filters if you filter on email address instead of "subject:" Here is the overview of the new lists names : arm-dev at centos.org => arm-dev at lists.centos.org centos at centos.org => discuss at lists.centos.org centos-devel at centos.org => devel at lists.centos.org centos-announce at centos.org => announce at lists.centos.org centos-automotive-sig at centos.org => automotive-sig at lists.centos.org centos-{cz,de,es,fr,nl,pt-br,zh}(a)centos.org => discuss-{cz,de,es,fr,nl,pt-br,zh}(a)lists.centos.org ci-users at centos.org => ci-users at lists.centos.org centos-gsoc: => gsoc at lists.centos.org centos-mirror at centos.org => mirror at lists.centos.org centos-mirror-announce at centos.org => mirror-announce at lists.centos.org centos-newsletter at centos.org => newsletter at lists.centos.org centos-promo at centos.org => promo at lists.centos.org centos-virt at centos.org => virt at lists.centos.org # Authentication Mailman2 had no real concept of authentication so you could just subscribe to one or more lists, and have a password associated with your email address for that/these subscription(s). Mailman3 itself is split into "core" and "webui" components, so when we'll import mailman2 lists/config into mailman3, your existing subscriptions will continue to work *but* not your password. Mailman3 will be configured to support SSO, and so if you already have a FAS/ACO account (https://accounts.centos.org) you'll be able to login directly into new webui and manage your settings/subscriptions *if* your ACO email address of course matches the one you initially subscribed with for lists.centos.org. If that's not the case, either create an ACO/FAS account that will match and you'll be then able to "link" your mailman3 account with FAS and so manage your settings/subscriptions. If you don't want to, there is always the documented process : https://docs.mailman3.org/en/latest/userguide.html#making-a-mailman-account Thanks for your understanding and patience. on behalf of the Infra team, -- Fabian Arrotin The CentOS Project | https://www.centos.org gpg key: 17F3B7A1 | @arrfab[@fosstodon.org]

3 5

Newer/faster aarch64 koji builders for cbs.centos.org
by Fabian Arrotin 08 Apr '24

08 Apr '24

Just to announce that last week, I replaced (one by one so no downtime from a rpm builds perspective) the older aarch64 builders we had for cbs.centos.org pool , with newer ones/faster ones. In the past, we had a mix of ThunderX/ThunderX2 machines, and these were replaced by newer Ampere Altra machines (Thanks to Ampere for having sponsored one machine and Red Hat sponsored the other ones !) As it was replaced last week, I had a look at some SIGs builds involving aarch64 architectures and compared needed time builds between older platform and newer builders #kernel / kmod SIG before: https://cbs.centos.org/koji/taskinfo?taskID=3900620 => 30min now: https://cbs.centos.org/koji/taskinfo?taskID=3901748 => 17min #samba / storage SIG before: https://cbs.centos.org/koji/taskinfo?taskID=3836506 => 59min now: https://cbs.centos.org/koji/taskinfo?taskID=3900306 => 13min #kernel-automotive / automotive SIG before: https://cbs.centos.org/koji/taskinfo?taskID=3894668 => 41min now: https://cbs.centos.org/koji/taskinfo?taskID=3901722 => 13min Of course, don't take these metrics as "granted" for your future builds (as it depends on number of other concurrently builds, etc) but at least it should be faster than before (including also for the Image tasks) I hope that all SIGs building also for aarch64 will enjoy the new aarch64 builders ! -- Fabian Arrotin The CentOS Project | https://www.centos.org gpg key: 17F3B7A1 | @arrfab[@fosstodon.org]

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

devel April 2024