Language Selection

English French German Italian Portuguese Spanish

Public beta release planned for 2008.0 release cycle

Filed under
Gentoo

Public beta releases play a major role in the Release Engineering team's revamped plans for 2008.0. Releng lead Chris Gianelloni said he hoped beta releases would increase community participation as well as the quality of the final release. These feature-complete public betas will require the earlier development of release materials, another component of the 2008.0 changes. To ensure sufficient time for beta testing, a mandatory 2-week testing period will follow the beta release.

A comprehensive testing checklist will be developed on the gentoo-releng mailing list, as will a list of which details of testers' machines and environments they should turn in to developers. In the past, testers often provided insufficient information to releng developers because of vague instructions. Now, a new form will include all of the required questions and details. "Sadly you almost want a beta that phones home as to what it was successfully run on," said Tom Gall. Christian Faulhammer suggested using a hardware reporting tool such as app-admin/hwreport.

More news on the 2008.0 release will appear over the next few days.

Tentative schedule (dates may change):
Feb. 1 Snapshot of the tree taken
Feb. 25 Docs due to GDP from release coordinators
Feb. 25 Snapshot frozen for beta
Feb. 29 Docs finalized
Mar. 3 Beta1 released
Mar. 14 Final upload
Mar. 17 Release

Source




More in Tux Machines

Security Leftovers

  • Someone is putting lots of work into hacking Github developers [Ed: Dan Goodin doesn't know that everything is under attack and cracking attempts just about all the time?]
    Open-source developers who use Github are in the cross-hairs of advanced malware that has steal passwords, download sensitive files, take screenshots, and self-destruct when necessary.
  • Security Orchestration and Incident Response
    Technology continues to advance, and this is all a changing target. Eventually, computers will become intelligent enough to replace people at real-time incident response. My guess, though, is that computers are not going to get there by collecting enough data to be certain. More likely, they'll develop the ability to exhibit understanding and operate in a world of uncertainty. That's a much harder goal. Yes, today, this is all science fiction. But it's not stupid science fiction, and it might become reality during the lifetimes of our children. Until then, we need people in the loop. Orchestration is a way to achieve that.

Leftover: Development (Linux)

  • Swan: Better Linux on Windows
    If you are a Linux user that has to use Windows — or even a Windows user that needs some Linux support — Cygwin has long been a great tool for getting things done. It provides a nearly complete Linux toolset. It also provides almost the entire Linux API, so that anything it doesn’t supply can probably be built from source. You can even write code on Windows, compile and test it and (usually) port it over to Linux painlessly.
  • Lint for Shell Scripters
    It used to be one of the joys of writing embedded software was never having to deploy shell scripts. But now with platforms like the Raspberry Pi becoming very common, Linux shell scripts can be a big part of a system–even the whole system, in some cases. How do you know your shell script is error-free before you deploy it? Of course, nothing can catch all errors, but you might try ShellCheck.
  • Android: Enabling mainline graphics
    Android uses the HWC API to communicate with graphics hardware. This API is not supported on the mainline Linux graphics stack, but by using drm_hwcomposer as a shim it now is. The HWC (Hardware Composer) API is used by SurfaceFlinger for compositing layers to the screen. The HWC abstracts objects such as overlays and 2D blitters and helps offload some work that would normally be done with OpenGL. SurfaceFlinger on the other hand accepts buffers from multiple sources, composites them, and sends them to the display.
  • Collabora's Devs Make Android's HWC API Work in Mainline Linux Graphics Stack
    Collabora's Mark Filion informs Softpedia today about the latest work done by various Collabora developers in collaboration with Google's ChromeOS team to enable mainline graphics on Android. The latest blog post published by Collabora's Robert Foss reveals the fact that both team managed to develop a shim called drm_hwcomposer, which should enable Android's HWC (Hardware Composer) API to communicate with the graphics hardware, including Android 7.0's version 2 HWC API.

today's howtos

Reports From and About Cloud Native Computing Foundation (CNCF)