Re: [Bacula-users] [Bacula-devel] Bacula release strategy.

2007-03-19 Thread Kern Sibbald
On Tuesday 20 March 2007 00:49, Steen wrote: > Mandag 19 marts 2007 19:34 skrev Kern Sibbald: > > After receiving somewhat conflicting input (some pro quick releases, some > > against), I've decided roughly to follow the following strategy: > > > > For the immediate future: > > 1. Observe the progr

Re: [Bacula-users] [Bacula-devel] Bacula release strategy.

2007-03-19 Thread Steen
Mandag 19 marts 2007 19:34 skrev Kern Sibbald: > After receiving somewhat conflicting input (some pro quick releases, some > against), I've decided roughly to follow the following strategy: > > For the immediate future: > 1. Observe the progress of our current development work over the next week >

Re: [Bacula-users] [Bacula-devel] Bacula release strategy.

2007-03-19 Thread Kern Sibbald
After receiving somewhat conflicting input (some pro quick releases, some against), I've decided roughly to follow the following strategy: For the immediate future: 1. Observe the progress of our current development work over the next week or two. 2. As far as I can tell, all the code is stabl

Re: [Bacula-users] [Bacula-devel] Bacula release strategy.

2007-03-18 Thread Kern Sibbald
On Sunday 18 March 2007 20:27, David Boyes wrote: > > > I'm a fan of frequent releases. Smaller changes each time is a good > > > thing. Both from a user and a sysadmin point of view. > > In principle this is a great idea. Can I suggest a minor variant? > > Frequent releases benefit sites that

Re: [Bacula-users] [Bacula-devel] Bacula release strategy.

2007-03-18 Thread David Boyes
> > I'm a fan of frequent releases. Smaller changes each time is a good > > thing. Both from a user and a sysadmin point of view. In principle this is a great idea. Can I suggest a minor variant? Frequent releases benefit sites that are capable of experimentation. Enterprise deployments don't

Re: [Bacula-users] [Bacula-devel] Bacula release strategy.

2007-03-18 Thread Kern Sibbald
On Sunday 18 March 2007 18:22, Dan Langille wrote: > On 18 Mar 2007 at 16:27, Kern Sibbald wrote: > > > Hello, > > > > I'm considering the following ideas for the next couple of Bacula releases, > > and would like your ideas. > > > > 1. Release version 2.0.4 in the next week or two with a coup

Re: [Bacula-users] [Bacula-devel] Bacula release strategy.

2007-03-18 Thread Kern Sibbald
Hello, Please don't hijack an email message. Your subject is titled "Bacula release strategy", but the contents has nothing to do with that subject. Concerning your question: I cannot answer your question because you have supplied insufficient information, because the text you show for disk_c

Re: [Bacula-users] [Bacula-devel] Bacula release strategy.

2007-03-18 Thread Dan Langille
On 18 Mar 2007 at 16:27, Kern Sibbald wrote: > Hello, > > I'm considering the following ideas for the next couple of Bacula releases, > and would like your ideas. > > 1. Release version 2.0.4 in the next week or two with a couple more bug fixes. > > 2. Release either version 2.0.5 or more like

Re: [Bacula-users] [Bacula-devel] Bacula release strategy.

2007-03-18 Thread Ondrej PLANKA
Hi Kern and lists, I discover problem with RunScript directive in version 2.0.2 and now in 2.0.3 too. I have next directive in Job resource: RunScript { RunsWhen = After RunsOnSuccess = yes Command = "/etc/bacula/scripts/disk_check.sh %j" } and the script disk_check.sh is following: siz

Re: [Bacula-users] [Bacula-devel] Bacula release strategy.

2007-03-18 Thread Kern Sibbald
On Sunday 18 March 2007 17:28, Eric Bollengier wrote: > Hi, > > > I'm considering the following ideas for the next couple of Bacula releases, > > and would like your ideas. > > > > 1. Release version 2.0.4 in the next week or two with a couple more bug > > fixes. > > > > 2. Release either version

Re: [Bacula-users] [Bacula-devel] Bacula release strategy.

2007-03-18 Thread Eric Bollengier
Hi, > I'm considering the following ideas for the next couple of Bacula releases, > and would like your ideas. > > 1. Release version 2.0.4 in the next week or two with a couple more bug > fixes. > > 2. Release either version 2.0.5 or more likely version 2.2.0 within 4-8 > weeks, targeting 6 weeks