http://wiki.cucumberlinux.com/wiki/ 2026-04-07T09:22:54+0000 http://wiki.cucumberlinux.com/wiki/ http://wiki.cucumberlinux.com/wiki/lib/tpl/dokuwiki/images/favicon.ico text/html 2018-08-30T20:04:55+0000 Anonymous (anonymous@undisclosed.example.com) http://wiki.cucumberlinux.com/wiki/devdocs:1_1_roadmap?rev=1535659495&do=diff Roadmap for the Cucumber Linux 1.1 Release Here are some key events that will be happening in the near future with approximate dates. Note that we don't like force any releases or milestones to happen before we're ready, so these dates are just approximate and may be subject to some change: text/html 2018-09-15T15:52:11+0000 Anonymous (anonymous@undisclosed.example.com) http://wiki.cucumberlinux.com/wiki/devdocs:2_0_roadmap?rev=1537026731&do=diff Cucumber Linux 2.0 Roadmap Task Status Key For simplicity and cleanliness sake, please use the following abbreviations for the status of tasks: * NS = Not Started * HW = Help Wanted * WIP = Work in Progress * DONE = Done/Completed If the status is 'HW', that means we are seeking developers to help with it. If you would like to help with a task that is not listed as HW (Help Wanted) or already has a developer assigned, please contact that developer directly (see text/html 2018-11-17T16:35:02+0000 Anonymous (anonymous@undisclosed.example.com) http://wiki.cucumberlinux.com/wiki/devdocs:build_system_infrastructure?rev=1542472502&do=diff Cucumber Linux Build & Distribution Infrastructure Types of Systems Any system that is part of the build/distribution infrastructure can be classified as one of the following types of systems. Bootstrap Server A bootstrap server is a server that is used to bootstrap a new build of text/html 2018-08-30T20:04:55+0000 Anonymous (anonymous@undisclosed.example.com) http://wiki.cucumberlinux.com/wiki/devdocs:core_packages?rev=1535659495&do=diff Core Packages Definition The core packages include the packages that are absolutely essential to the system’s functionality (such as the Linux Kernel, Binutils, Coreutils, GCC, etc) and any packages where upgrading to a new version has a high potential of breaking existing packages, configurations and other stuff (such as Apache, OpenSSL, PHP, Python, Perl, etc). text/html 2019-01-07T17:12:52+0000 Anonymous (anonymous@undisclosed.example.com) http://wiki.cucumberlinux.com/wiki/devdocs:deploy_new_build_server?rev=1546881172&do=diff Deploying a New Build Server The following is the process for deploying a new build server. * Edit the /etc/pickle.conf file and set MIRROR variable to point to the staging server. * Install the the build server buildtools (substitute the version number of Cucumber Linux you are building in for text/html 2018-12-03T16:52:51+0000 Anonymous (anonymous@undisclosed.example.com) http://wiki.cucumberlinux.com/wiki/devdocs:finalize_release_process?rev=1543855971&do=diff Release Process Updated November 17, 2018 The following is the process for finalizing a new release of Cucumber Linux. The first part of the release process differs depending on whether you are releasing from a build server of a bootstrap server. If you are completing a Cucumber Linux from Scratch build, then you are releasing from a bootstrap server. Otherwise, you are releasing from a build server. text/html 2018-10-18T22:21:16+0000 Anonymous (anonymous@undisclosed.example.com) http://wiki.cucumberlinux.com/wiki/devdocs:hardening_ideas?rev=1539901276&do=diff If any developers have ideas for hardening the distribution, feel free to post them here :-). Keep in mind that these are just ideas, not necessarily stuff we have committed to doing. Rescue Environment Create a rescue environment in /opt/rescue. This environment will contain backup versions of essential binaries (similar to BSD's /rescue or /altroot directory). It will reside on a separate read only filesystem. It will use Busybox with static linking so it is not dependent on any other part o… text/html 2018-08-30T20:04:55+0000 Anonymous (anonymous@undisclosed.example.com) http://wiki.cucumberlinux.com/wiki/devdocs:packages_to_add?rev=1535659495&do=diff Packages to Add to Future Releases This page contains a list of packages we are planning to add to future releases of Cucumber Linux. If a packager or package status is listed as 'HELP WANTED' for a package, that means we are looking for someone to package that package. text/html 2019-01-24T17:06:12+0000 Anonymous (anonymous@undisclosed.example.com) http://wiki.cucumberlinux.com/wiki/devdocs:start?rev=1548349572&do=diff Development Documents This section is where the Cucumber Linux development documents and plans are outlined. If you are new to contributing to Cucumber Linux or would like to start contributing, looking at the To Do List is a great place to start. Active Subpages text/html 2018-11-18T14:05:06+0000 Anonymous (anonymous@undisclosed.example.com) http://wiki.cucumberlinux.com/wiki/devdocs:sysbuild_numbers?rev=1542549906&do=diff Build Numbers Every time Cucumber Linux is rebuilt from scratch, a new system build number (called sysbuild number) is assigned to that build. This is done due to the fact that each new build has the potential to break ABI compatibility. Using these build numbers makes it easy to keep track which ABI revision a system is on. text/html 2018-08-30T20:04:55+0000 Anonymous (anonymous@undisclosed.example.com) http://wiki.cucumberlinux.com/wiki/devdocs:todo?rev=1535659495&do=diff This is the development to do list for Cucumber Linux. If no developer is listed for a task or the task's status is 'HELP WANTED', that means we are looking for a developer to do that task. If you are interested in doing one of these tasks, please follow the instructions on the text/html 2019-01-24T21:02:47+0000 Anonymous (anonymous@undisclosed.example.com) http://wiki.cucumberlinux.com/wiki/devdocs:update_package?rev=1548363767&do=diff The following is the process for building and releasing an updated package using the build infrastructure. Throughout this guide, substitute the version of Cucumber Linux you are building in for x.y. On the staging server: * Update the ports tree: