From a2f6a705c99104e8fb4cd80c1d5c3d7d992a447a Mon Sep 17 00:00:00 2001 From: Lars Wirzenius Date: Tue, 16 Jan 2018 18:36:09 +0200 Subject: Change: update roadmap to show remaining stuff --- roadmap.mdwn | 30 ++---------------------------- 1 file changed, 2 insertions(+), 28 deletions(-) (limited to 'roadmap.mdwn') diff --git a/roadmap.mdwn b/roadmap.mdwn index 4f898e3..5d308c6 100644 --- a/roadmap.mdwn +++ b/roadmap.mdwn @@ -8,7 +8,7 @@ Current development goal ============================================================================= The current development goal is to be the first ALPHA version, and is -described in detail in the [architecture document][], and is briefly +described in detail in the [[architecture]] document, and is briefly this: > ALPHA-1 of Ick2 can be deployed and configured easily, and can @@ -23,36 +23,10 @@ this: > sysadmin is not expected to set up the pbuilder base tarball, ick2 > will do that). -[architecture document]: http://code.liw.fi/ick/ick2-arch.html - -Acceptance criteria for ALPHA-1: - -* All Ick2 components and the workers are deployable using Ansible or - similar configuration management tooling. +Remaining acceptance criteria for ALPHA-1: * At least two people (not only Lars) have set up a CI cluster to build at least two different projects on at least two workers. One of the projects should build documentation for ick2 itself, the other should build a .deb packages of ick2. Bonus points for building other projects than ick2 as well. - -* Builds get triggered automatically by a git server on any commit to - the master branch. - -* Build logs can be viewed while builds are running or afterwards via - an HTTP API (perhaps wrapped in a command line tool). Bonus points - if someone builds a web app on top of the API. - -* A modicum of thought has been spent on security and the major - contributors agree the security design is not idiotic. The goal is - to be confident that a future version of Ick2 can be made reasonably - secure, even if that doesn't happen for ALPHA-1. - -* The workspace is constructed from several git repositories, e.g., so - that the debian subdir comes from a different repo than the main - source tree. - -* The pipeline steps are not merely snippets of shell scripts to run. - Instead, steps may name operations that get executed by the workers - without specifying the implementation in the Ick2 project - configuration. -- cgit v1.2.1