blob: 0949e7034dc2900be50757f4ecedc4914983aa00 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
|
[[!meta title="Road map"]]
This is the road map for Ick development. It does not stretch very far,
because predicting the future is difficult. This road map also doesn't
give any dates, this is a hobby project.
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
this:
> ALPHA-1 of Ick can be deployed and configured easily, and can
> concurrently build multiple projects using multiple workers. Builds
> may be traditional builds from source code, may involve running unit
> tests or other build-time tests, may involve building Debian
> packages, and build artefacts are published in a suitable location.
> Builds may also be builds of static web sites or documentation, and
> those build artefacts may be published on suitable web servers.
> Builds happen on workers in reasonably well isolated, automatically
> maintained environments akin to pbuilder or schroot (meaning the
> sysadmin is not expected to set up the pbuilder base tarball, ick
> will do that).
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 ick itself, the
other should build a .deb packages of ick. Bonus points for
building other projects than ick as well.
|
