1
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
3
<!--Converted with LaTeX2HTML 2008 (1.71)
4
original version by: Nikos Drakos, CBLU, University of Leeds
5
* revised and updated by: Marcus Hennecke, Ross Moore, Herb Swan
6
* with significant contributions from:
7
Jens Lippmann, Marek Rouchal, Martin Wilck and others -->
10
<TITLE>The Development Cycle</TITLE>
11
<META NAME="description" CONTENT="The Development Cycle">
12
<META NAME="keywords" CONTENT="developers">
13
<META NAME="resource-type" CONTENT="document">
14
<META NAME="distribution" CONTENT="global">
16
<META NAME="Generator" CONTENT="LaTeX2HTML v2008">
17
<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
19
<LINK REL="STYLESHEET" HREF="developers.css">
21
<LINK REL="next" HREF="Bacula_Code_Submissions_Pro.html">
22
<LINK REL="previous" HREF="Bacula_Developer_Notes.html">
23
<LINK REL="up" HREF="Bacula_Developer_Notes.html">
24
<LINK REL="next" HREF="Bacula_Code_Submissions_Pro.html">
28
<!--Navigation Panel-->
30
HREF="Bacula_Code_Submissions_Pro.html">
31
<IMG WIDTH="37" HEIGHT="24" ALIGN="BOTTOM" BORDER="0" ALT="next" SRC="next.png"></A>
33
HREF="Bacula_Developer_Notes.html">
34
<IMG WIDTH="26" HEIGHT="24" ALIGN="BOTTOM" BORDER="0" ALT="up" SRC="up.png"></A>
36
HREF="Bacula_Developer_Notes.html">
37
<IMG WIDTH="63" HEIGHT="24" ALIGN="BOTTOM" BORDER="0" ALT="previous" SRC="prev.png"></A>
40
<IMG WIDTH="65" HEIGHT="24" ALIGN="BOTTOM" BORDER="0" ALT="contents" SRC="contents.png"></A>
42
HREF="GNU_Free_Documentation_Lice.html">
43
<IMG WIDTH="43" HEIGHT="24" ALIGN="BOTTOM" BORDER="0" ALT="index" SRC="index.png"></A>
45
<B> Next:</B> <A NAME="tex2html466"
46
HREF="Bacula_Code_Submissions_Pro.html">Bacula Code Submissions and</A>
47
<B> Up:</B> <A NAME="tex2html460"
48
HREF="Bacula_Developer_Notes.html">Bacula Developer Notes</A>
49
<B> Previous:</B> <A NAME="tex2html454"
50
HREF="Bacula_Developer_Notes.html">Bacula Developer Notes</A>
51
<B> <A NAME="tex2html462"
52
HREF="Contents.html">Contents</A></B>
53
<B> <A NAME="tex2html464"
54
HREF="GNU_Free_Documentation_Lice.html">Index</A></B>
57
<!--End of Navigation Panel-->
59
<H1><A NAME="SECTION00210000000000000000"></A>
67
As discussed on the email lists, the number of contributions are
68
increasing significantly. We expect this positive trend
69
will continue. As a consequence, we have modified how we do
70
development, and instead of making a list of all the features that we will
71
implement in the next version, each developer signs up for one (maybe
72
two) projects at a time, and when they are complete, and the code
73
is stable, we will release a new version. The release cycle will probably
74
be roughly six months.
77
The difference is that with a shorter release cycle and fewer released
78
feature, we will have more time to review the new code that is being
79
contributed, and will be able to devote more time to a smaller number of
80
projects (some prior versions had too many new features for us to handle
84
Future release schedules will be much the same, and the
85
number of new features will also be much the same providing that the
86
contributions continue to come - and they show no signs of let up :-)
90
<B>Feature Requests:</B>
92
In addition, we have "formalizee" the feature requests a bit.
95
Instead of me maintaining an informal list of everything I run into
96
(kernstodo), we now maintain a "formal" list of projects. This
97
means that all new feature requests, including those recently discussed on
98
the email lists, must be formally submitted and approved.
101
Formal submission of feature requests will take two forms:
103
1. non-mandatory, but highly recommended is to discuss proposed new features
106
2. Formal submission of an Feature Request in a special format. We'll
107
give an example of this below, but you can also find it on the web site
108
under "Support - Feature Requests". Since it takes a bit of time to
109
properly fill out a Feature Request form, you probably should check on the
113
Once the Feature Request is received by the keeper of the projects list, it
114
will be sent to the Bacula project manager (Kern), and he will either
115
accept it (90the time), send it to the email list asking for opinions, or reject it
119
If it is accepted, it will go in the "projects" file (a simple ASCII file)
120
maintained in the main Bacula source directory.
123
<B>Implementation of Feature Requests:</B>
125
Any qualified developer can sign up for a project. The project must have
126
an entry in the projects file, and the developer's name will appear in the
130
<B>How Feature Requests are accepted:</B>
132
Acceptance of Feature Requests depends on several things:
134
1. feedback from users. If it is negative, the Feature Request will probably not be
137
2. the difficulty of the project. A project that is so
138
difficult that we cannot imagine finding someone to implement probably won't
139
be accepted. Obviously if you know how to implement it, don't hesitate
140
to put it in your Feature Request
142
3. whether or not the Feature Request fits within the current strategy of
143
Bacula (for example an Feature Request that requests changing the tape to
144
tar format probably would not be accepted, ...).
147
<B>How Feature Requests are prioritized:</B>
149
Once an Feature Request is accepted, it needs to be implemented. If you
150
can find a developer for it, or one signs up for implementing it, then the
151
Feature Request becomes top priority (at least for that developer).
154
Between releases of Bacula, we will generally solicit Feature Request input
155
for the next version, and by way of this email, we suggest that you send
156
discuss and send in your Feature Requests for the next release. Please
157
verify that the Feature Request is not in the current list (attached to this email).
160
Once users have had several weeks to submit Feature Requests, the keeper of
161
the projects list will organize them, and request users to vote on them.
162
This will allow fixing prioritizing the Feature Requests. Having a
163
priority is one thing, but getting it implement is another thing - we are
164
hoping that the Bacula community will take more responsibility for assuring
165
the implementation of accepted Feature Requests.
168
Feature Request format:
170
============= Empty Feature Request form ===========
171
Item n: One line summary ...
173
Origin: Name and email of originator.
176
What: More detailed explanation ...
178
Why: Why it is important ...
180
Notes: Additional notes or features (omit if not used)
181
============== End Feature Request form ==============
186
============= Example Completed Feature Request form ===========
187
Item 1: Implement a Migration job type that will move the job
188
data from one device to another.
189
Origin: Sponsored by Riege Sofware International GmbH. Contact:
190
Daniel Holtkamp <holtkamp at riege dot com>
191
Date: 28 October 2005
192
Status: Partially coded in 1.37 -- much more to do. Assigned to
195
What: The ability to copy, move, or archive data that is on a
196
device to another device is very important.
198
Why: An ISP might want to backup to disk, but after 30 days
199
migrate the data to tape backup and delete it from
200
disk. Bacula should be able to handle this
201
automatically. It needs to know what was put where,
202
and when, and what to migrate -- it is a bit like
203
retention periods. Doing so would allow space to be
204
freed up for current backups while maintaining older
207
Notes: Migration could be triggered by:
211
Highwater size (keep total size)
213
=================================================
218
<!--Navigation Panel-->
219
<A NAME="tex2html465"
220
HREF="Bacula_Code_Submissions_Pro.html">
221
<IMG WIDTH="37" HEIGHT="24" ALIGN="BOTTOM" BORDER="0" ALT="next" SRC="next.png"></A>
222
<A NAME="tex2html459"
223
HREF="Bacula_Developer_Notes.html">
224
<IMG WIDTH="26" HEIGHT="24" ALIGN="BOTTOM" BORDER="0" ALT="up" SRC="up.png"></A>
225
<A NAME="tex2html453"
226
HREF="Bacula_Developer_Notes.html">
227
<IMG WIDTH="63" HEIGHT="24" ALIGN="BOTTOM" BORDER="0" ALT="previous" SRC="prev.png"></A>
228
<A NAME="tex2html461"
229
HREF="Contents.html">
230
<IMG WIDTH="65" HEIGHT="24" ALIGN="BOTTOM" BORDER="0" ALT="contents" SRC="contents.png"></A>
231
<A NAME="tex2html463"
232
HREF="GNU_Free_Documentation_Lice.html">
233
<IMG WIDTH="43" HEIGHT="24" ALIGN="BOTTOM" BORDER="0" ALT="index" SRC="index.png"></A>
235
<B> Next:</B> <A NAME="tex2html466"
236
HREF="Bacula_Code_Submissions_Pro.html">Bacula Code Submissions and</A>
237
<B> Up:</B> <A NAME="tex2html460"
238
HREF="Bacula_Developer_Notes.html">Bacula Developer Notes</A>
239
<B> Previous:</B> <A NAME="tex2html454"
240
HREF="Bacula_Developer_Notes.html">Bacula Developer Notes</A>
241
<B> <A NAME="tex2html462"
242
HREF="Contents.html">Contents</A></B>
243
<B> <A NAME="tex2html464"
244
HREF="GNU_Free_Documentation_Lice.html">Index</A></B>
245
<!--End of Navigation Panel-->
added
removed
manuals/en/developers/developers/Development_Cycle.html
