bashburn-info

[Bashburn-info] 3.0 Beta 1

[Anders L. <and...@gm...>]

So guys, I'm thinking I'll release 3.0 beta1 tonight or tomorrow. If anyone 
feels that's a bad idea let me know, otherwise I'll do it. I'll include the 
English, Swedish and German translation because as far as I know those 
are the ones updated. 
We've tested this thing pretty good so I feel good releasing a beta to 
hunt down any hard to find bugs that might still be there.
-- 
Anders Lindén
http://bashburn.dose.se

Re: [Bashburn-info] 3.0 Beta 1

[Nick W. <ni...@uk...>]

On Tue, 7 Oct 2008 00:03:25 +0200
Anders Lindén <and...@gm...> wrote:

> So guys, I'm thinking I'll release 3.0 beta1 tonight or tomorrow. If
> anyone feels that's a bad idea let me know, otherwise I'll do it.
> I'll include the English, Swedish and German translation because as
> far as I know those are the ones updated. 
> We've tested this thing pretty good so I feel good releasing a beta
> to hunt down any hard to find bugs that might still be there.

Agreed.

As far as I am concerned, I have learnt a lot lately on CD/DVD burning,
and BashBurn *just* works and is damn good.

Of course, that is why years ago I found it, as it just done what I
needed without the bollocks GUI apps try to do.

Nick
-- 
Free Software Foundation Associate Member 5508

Re: [Bashburn-info] 3.0 Beta 1

[Markus K. <mar...@on...>]

Anders Lindén schrieb:
> So guys, I'm thinking I'll release 3.0 beta1 tonight or tomorrow. If anyone 
> feels that's a bad idea let me know, otherwise I'll do it. I'll include the 
> English, Swedish and German translation because as far as I know those 
> are the ones updated. 
> We've tested this thing pretty good so I feel good releasing a beta to 
> hunt down any hard to find bugs that might still be there.
>   

Ok, Anders. Big marking as beta I think would be ok. So we could get 
more people for testing - and since there is a "rule" to release often 
in open source development, this may also a point.

Ahh - Anders you can look to the Swedish translation. I have added the 
variable

bb_main_menu=MAIN

in file "BashBurn.lang" for main-menue header text printing. Translate it to swedish if necessary.


Markus

Re: [Bashburn-info] 3.0 Beta 1

[Markus K. <mar...@on...>]

Anders Lindén schrieb:
> So guys, I'm thinking I'll release 3.0 beta1 tonight or tomorrow. If anyone 
> feels that's a bad idea let me know, otherwise I'll do it. I'll include the 
> English, Swedish and German translation because as far as I know those 
> are the ones updated. 
> We've tested this thing pretty good so I feel good releasing a beta to 
> hunt down any hard to find bugs that might still be there.
>   

Ok, Anders. Big marking as beta I think would be ok. So we could get 
more people for testing - and since there is a "rule" to release often 
in open source development, this may also a point.

Ahh - Anders you can look to the Swedish translation. I have added the 
variable

bb_main_menu=MAIN

in file "BashBurn.lang" for main-menue header text printing. Translate it to swedish if necessary.



By the way - did you removed the link to the svn web-interface on the bashburn website? I cna't find it anymore.
I think it would be nice to have it there, or don' t think so?

Markus

Re: [Bashburn-info] 3.0 Beta 1

[Nick W. <ni...@uk...>]

On Tue, 07 Oct 2008 02:10:43 +0200
Markus Kollmar <mar...@on...> wrote:

> By the way - did you removed the link to the svn web-interface on the
> bashburn website? I cna't find it anymore. I think it would be nice
> to have it there, or don' t think so?

It is still there, Markus.  Got to 'downloads' page - at the very
bottom is the link to the web SVN.

Nick
-- 
Free Software Foundation Associate Member 5508

Re: [Bashburn-info] 3.0 Beta 1

[Steven W. O. <st...@sy...>]

On Monday, Oct 6th 2008 at 18:03 -0000, quoth Anders Lind?n:

=>So guys, I'm thinking I'll release 3.0 beta1 tonight or tomorrow. If anyone 
=>feels that's a bad idea let me know, otherwise I'll do it. I'll include the 
=>English, Swedish and German translation because as far as I know those 
=>are the ones updated. 
=>We've tested this thing pretty good so I feel good releasing a beta to 
=>hunt down any hard to find bugs that might still be there.

Sounds delovely :-)


-- 
Time flies like the wind. Fruit flies like a banana. Stranger things have  .0.
happened but none stranger than this. Does your driver's license say Organ ..0
Donor?Black holes are where God divided by zero. Listen to me! We are all- 000
individuals! What if this weren't a hypothetical question?
steveo at syslang.net

Re: [Bashburn-info] 3.0 Beta 1

[Markus K. <mar...@on...>]

Anders Lindén wrote:
> On Tuesday 07 October 2008 02:10:43 you wrote:
>   
>> Anders Lindén schrieb:
>>     
>>> So guys, I'm thinking I'll release 3.0 beta1 tonight or tomorrow. If
>>> anyone feels that's a bad idea let me know, otherwise I'll do it. I'll
>>> include the English, Swedish and German translation because as 
>>>       
> far as I
>   
>>> know those are the ones updated.
>>> We've tested this thing pretty good so I feel good releasing a 
>>>       
> beta to
>   
>>> hunt down any hard to find bugs that might still be there.
>>>       
>> Ok, Anders. Big marking as beta I think would be ok. So we could 
>>     
> get
>   
>> more people for testing - and since there is a "rule" to release often
>> in open source development, this may also a point.
>>
>> Ahh - Anders you can look to the Swedish translation. I have added 
>>     
> the
>   
>> variable
>>
>> bb_main_menu=MAIN
>>
>> in file "BashBurn.lang" for main-menue header text printing. 
>>     
> Translate it
>   
>> to swedish if necessary.
>>
>>
>>
>> By the way - did you removed the link to the svn web-interface on 
>>     
> the
>   
>> bashburn website? I cna't find it anymore. I think it would be nice to 
>>     
> have
>   
>> it there, or don' t think so?
>>
>> Markus
>>     
>
> Alright Markus, I'll add and translate that.
> No I haven't removed that link from the web page. It's located under 
> downloads -> webSVN
>
>   

Anders, we have a small problem with Beta 1!

I have done yesterday some changes in the trunk (also the mentioned 
swedish language updating).
Now I saw you have not moved all files for the release 3.0 from 'trunk' 
to 'release' shortly before you created the release-package.

I should had tell you this - so you thought that there was no major 
changes in the trunk since you created the release branch.
In my humble opinion I think it would be good if we use following 
process to make a release and to avoid such things in future:


1. Like you did - tell others per mailing list shortly before release 
whether it is ok to create a release for the main developers, and tell 
the short time period in which the creation is planned.

2. Then lock the trunk branch (via "svn lock") and move ALL files from 
trunk to release.

3. Create package from release tree.

4. Unlock trunk branch.


Is this a way?
However, Anders now we can maybe in near future release beta 2.
Hehe - before we got installed beta 1, it is already outdated.
If we would be a company we could make much money and users would be 
impressed about the dynamic of improvements.  ;-)


Markus

Re: [Bashburn-info] 3.0 Beta 1

[Nick W. <ni...@uk...>]

On Tue, 07 Oct 2008 15:11:50 +0200
Markus Kollmar <mar...@on...> wrote:

> Anders Lindén wrote:
> > On Tuesday 07 October 2008 02:10:43 you wrote:
> >   
> >> Anders Lindén schrieb:
> >>     
> >>> So guys, I'm thinking I'll release 3.0 beta1 tonight or tomorrow.
> >>> If anyone feels that's a bad idea let me know, otherwise I'll do
> >>> it. I'll include the English, Swedish and German translation
> >>> because as 
> > far as I
> >   
> >>> know those are the ones updated.
> >>> We've tested this thing pretty good so I feel good releasing a 
> >>>       
> > beta to
> >   
> >>> hunt down any hard to find bugs that might still be there.
> >>>       
> >> Ok, Anders. Big marking as beta I think would be ok. So we could 
> >>     
> > get
> >   
> >> more people for testing - and since there is a "rule" to release
> >> often in open source development, this may also a point.
> >>
> >> Ahh - Anders you can look to the Swedish translation. I have added 
> >>     
> > the
> >   
> >> variable
> >>
> >> bb_main_menu=MAIN
> >>
> >> in file "BashBurn.lang" for main-menue header text printing. 
> >>     
> > Translate it
> >   
> >> to swedish if necessary.
> >>
> >>
> >>
> >> By the way - did you removed the link to the svn web-interface on 
> >>     
> > the
> >   
> >> bashburn website? I cna't find it anymore. I think it would be
> >> nice to 
> > have
> >   
> >> it there, or don' t think so?
> >>
> >> Markus
> >>     
> >
> > Alright Markus, I'll add and translate that.
> > No I haven't removed that link from the web page. It's located
> > under downloads -> webSVN
> >
> >   
> 
> Anders, we have a small problem with Beta 1!
> 
> I have done yesterday some changes in the trunk (also the mentioned 
> swedish language updating).
> Now I saw you have not moved all files for the release 3.0 from
> 'trunk' to 'release' shortly before you created the release-package.
> 
> I should had tell you this - so you thought that there was no major 
> changes in the trunk since you created the release branch.
> In my humble opinion I think it would be good if we use following 
> process to make a release and to avoid such things in future:
> 
> 
> 1. Like you did - tell others per mailing list shortly before release 
> whether it is ok to create a release for the main developers, and
> tell the short time period in which the creation is planned.
> 
> 2. Then lock the trunk branch (via "svn lock") and move ALL files
> from trunk to release.
> 
> 3. Create package from release tree.
> 
> 4. Unlock trunk branch.
> 
> 
> Is this a way?
> However, Anders now we can maybe in near future release beta 2.
> Hehe - before we got installed beta 1, it is already outdated.
> If we would be a company we could make much money and users would be 
> impressed about the dynamic of improvements.  ;-)

Also I see somebody is only updating RELEASE tree?  I thought TRUNK
would be moved to RELEASE for beta 1?

Nick
-- 
Free Software Foundation Associate Member 5508

Re: [Bashburn-info] 3.0 Beta 1

[Nick W. <ni...@uk...>]

On Tue, 7 Oct 2008 14:23:28 +0100
Nick Warne <ni...@uk...> wrote:

> On Tue, 07 Oct 2008 15:11:50 +0200
> Markus Kollmar <mar...@on...> wrote:
> 
> > Anders Lindén wrote:
> > > On Tuesday 07 October 2008 02:10:43 you wrote:
> > >   
> > >> Anders Lindén schrieb:
> > >>     
> > >>> So guys, I'm thinking I'll release 3.0 beta1 tonight or
> > >>> tomorrow. If anyone feels that's a bad idea let me know,
> > >>> otherwise I'll do it. I'll include the English, Swedish and
> > >>> German translation because as 
> > > far as I
> > >   
> > >>> know those are the ones updated.
> > >>> We've tested this thing pretty good so I feel good releasing a 
> > >>>       
> > > beta to
> > >   
> > >>> hunt down any hard to find bugs that might still be there.
> > >>>       
> > >> Ok, Anders. Big marking as beta I think would be ok. So we could 
> > >>     
> > > get
> > >   
> > >> more people for testing - and since there is a "rule" to release
> > >> often in open source development, this may also a point.
> > >>
> > >> Ahh - Anders you can look to the Swedish translation. I have
> > >> added 
> > > the
> > >   
> > >> variable
> > >>
> > >> bb_main_menu=MAIN
> > >>
> > >> in file "BashBurn.lang" for main-menue header text printing. 
> > >>     
> > > Translate it
> > >   
> > >> to swedish if necessary.
> > >>
> > >>
> > >>
> > >> By the way - did you removed the link to the svn web-interface
> > >> on 
> > > the
> > >   
> > >> bashburn website? I cna't find it anymore. I think it would be
> > >> nice to 
> > > have
> > >   
> > >> it there, or don' t think so?
> > >>
> > >> Markus
> > >>     
> > >
> > > Alright Markus, I'll add and translate that.
> > > No I haven't removed that link from the web page. It's located
> > > under downloads -> webSVN
> > >
> > >   
> > 
> > Anders, we have a small problem with Beta 1!
> > 
> > I have done yesterday some changes in the trunk (also the mentioned 
> > swedish language updating).
> > Now I saw you have not moved all files for the release 3.0 from
> > 'trunk' to 'release' shortly before you created the release-package.
> > 
> > I should had tell you this - so you thought that there was no major 
> > changes in the trunk since you created the release branch.
> > In my humble opinion I think it would be good if we use following 
> > process to make a release and to avoid such things in future:
> > 
> > 
> > 1. Like you did - tell others per mailing list shortly before
> > release whether it is ok to create a release for the main
> > developers, and tell the short time period in which the creation is
> > planned.
> > 
> > 2. Then lock the trunk branch (via "svn lock") and move ALL files
> > from trunk to release.
> > 
> > 3. Create package from release tree.
> > 
> > 4. Unlock trunk branch.
> > 
> > 
> > Is this a way?
> > However, Anders now we can maybe in near future release beta 2.
> > Hehe - before we got installed beta 1, it is already outdated.
> > If we would be a company we could make much money and users would
> > be impressed about the dynamic of improvements.  ;-)
> 
> Also I see somebody is only updating RELEASE tree?  I thought TRUNK
> would be moved to RELEASE for beta 1?

Forgot - reason is there are a ton of fixes in TRUNK that are not in
RELEASE tree...

Nick
-- 
Free Software Foundation Associate Member 5508

Re: [Bashburn-info] 3.0 Beta 1

[Anders L. <and...@gm...>]

On Tuesday 07 October 2008 15:23:28 you wrote:
> On Tue, 07 Oct 2008 15:11:50 +0200
>
> Markus Kollmar <mar...@on...> wrote:
> > Anders Lindén wrote:
> > > On Tuesday 07 October 2008 02:10:43 you wrote:
> > >> Anders Lindén schrieb:
> > >>> So guys, I'm thinking I'll release 3.0 beta1 tonight or 
tomorrow.
> > >>> If anyone feels that's a bad idea let me know, otherwise I'll 
do
> > >>> it. I'll include the English, Swedish and German translation
> > >>> because as
> > >
> > > far as I
> > >
> > >>> know those are the ones updated.
> > >>> We've tested this thing pretty good so I feel good releasing 
a
> > >
> > > beta to
> > >
> > >>> hunt down any hard to find bugs that might still be there.
> > >>
> > >> Ok, Anders. Big marking as beta I think would be ok. So we 
could
> > >
> > > get
> > >
> > >> more people for testing - and since there is a "rule" to release
> > >> often in open source development, this may also a point.
> > >>
> > >> Ahh - Anders you can look to the Swedish translation. I have 
added
> > >
> > > the
> > >
> > >> variable
> > >>
> > >> bb_main_menu=MAIN
> > >>
> > >> in file "BashBurn.lang" for main-menue header text printing.
> > >
> > > Translate it
> > >
> > >> to swedish if necessary.
> > >>
> > >>
> > >>
> > >> By the way - did you removed the link to the svn web-interface 
on
> > >
> > > the
> > >
> > >> bashburn website? I cna't find it anymore. I think it would be
> > >> nice to
> > >
> > > have
> > >
> > >> it there, or don' t think so?
> > >>
> > >> Markus
> > >
> > > Alright Markus, I'll add and translate that.
> > > No I haven't removed that link from the web page. It's located
> > > under downloads -> webSVN
> >
> > Anders, we have a small problem with Beta 1!
> >
> > I have done yesterday some changes in the trunk (also the 
mentioned
> > swedish language updating).
> > Now I saw you have not moved all files for the release 3.0 from
> > 'trunk' to 'release' shortly before you created the release-
package.
> >
> > I should had tell you this - so you thought that there was no major
> > changes in the trunk since you created the release branch.
> > In my humble opinion I think it would be good if we use following
> > process to make a release and to avoid such things in future:
> >
> >
> > 1. Like you did - tell others per mailing list shortly before release
> > whether it is ok to create a release for the main developers, and
> > tell the short time period in which the creation is planned.
> >
> > 2. Then lock the trunk branch (via "svn lock") and move ALL files
> > from trunk to release.
> >
> > 3. Create package from release tree.
> >
> > 4. Unlock trunk branch.
> >
> >
> > Is this a way?
> > However, Anders now we can maybe in near future release beta 
2.
> > Hehe - before we got installed beta 1, it is already outdated.
> > If we would be a company we could make much money and users 
would be
> > impressed about the dynamic of improvements.  ;-)
>
> Also I see somebody is only updating RELEASE tree?  I thought 
TRUNK
> would be moved to RELEASE for beta 1?
>
> Nick

That was me just doing a quick little fix for beta 1. I forgot to update 
the installation script to not try to install the translations that were 
not included. 

I agree we should release a beta 2 soon. I should have checked more 
carefully that the latest trunk was copied to release. Sorry about that.

-- 
Anders Lindén
http://bashburn.dose.se

Re: [Bashburn-info] 3.0 Beta 1

[Markus K. <mar...@on...>]

Anders Lindén wrote:
> On Tuesday 07 October 2008 15:11:50 you wrote:
>   
>> Anders, we have a small problem with Beta 1!
>>
>> I have done yesterday some changes in the trunk (also the 
>>     
> mentioned
>   
>> swedish language updating).
>> Now I saw you have not moved all files for the release 3.0 from 
>>     
> 'trunk'
>   
>> to 'release' shortly before you created the release-package.
>>
>>     
>
> Ouch! Which files are we talking about? I could add the missing files 
> and do a quick re-release.
>
>   

Anders, I think that is not the best idea (it are some files like 
"BashBurn.sh" and lang. files - and maybe I think Nick and maybe others 
also did improvements since then).
So in such cases we should always take the whole thing to avoid 
dependency-problems - if we can be shure nothing is broken - and i think 
in this short time the trunk is relatively usable.


>> I should had tell you this - so you thought that there was no major
>> changes in the trunk since you created the release branch.
>> In my humble opinion I think it would be good if we use following
>> process to make a release and to avoid such things in future:
>>
>>
>> 1. Like you did - tell others per mailing list shortly before release
>> whether it is ok to create a release for the main developers, and tell
>> the short time period in which the creation is planned.
>>
>> 2. Then lock the trunk branch (via "svn lock") and move ALL files 
>>     
> from
>   
>> trunk to release.
>>
>> 3. Create package from release tree.
>>
>> 4. Unlock trunk branch.
>>
>>
>> Is this a way?
>>     
>
> Sounds like a good idea to me. 
>
>
>   
ok :-)


Markus

Re: [Bashburn-info] 3.0 Beta 1

[Nick W. <ni...@uk...>]

On Tue, 07 Oct 2008 15:44:31 +0200
Markus Kollmar <mar...@on...> wrote:

> Anders Lindén wrote:
> > On Tuesday 07 October 2008 15:11:50 you wrote:
> >   
> >> Anders, we have a small problem with Beta 1!
> >>
> >> I have done yesterday some changes in the trunk (also the 
> >>     
> > mentioned
> >   
> >> swedish language updating).
> >> Now I saw you have not moved all files for the release 3.0 from 
> >>     
> > 'trunk'
> >   
> >> to 'release' shortly before you created the release-package.
> >>
> >>     
> >
> > Ouch! Which files are we talking about? I could add the missing
> > files and do a quick re-release.
> >
> >   
> 
> Anders, I think that is not the best idea (it are some files like 
> "BashBurn.sh" and lang. files - and maybe I think Nick and maybe
> others also did improvements since then).
> So in such cases we should always take the whole thing to avoid 
> dependency-problems - if we can be shure nothing is broken - and i
> think in this short time the trunk is relatively usable.
> 
> 
> >> I should had tell you this - so you thought that there was no major
> >> changes in the trunk since you created the release branch.
> >> In my humble opinion I think it would be good if we use following
> >> process to make a release and to avoid such things in future:
> >>
> >>
> >> 1. Like you did - tell others per mailing list shortly before
> >> release whether it is ok to create a release for the main
> >> developers, and tell the short time period in which the creation
> >> is planned.
> >>
> >> 2. Then lock the trunk branch (via "svn lock") and move ALL files 
> >>     
> > from
> >   
> >> trunk to release.
> >>
> >> 3. Create package from release tree.
> >>
> >> 4. Unlock trunk branch.
> >>
> >>
> >> Is this a way?
> >>     
> >
> > Sounds like a good idea to me. 

Also what I meant was all changes go to TRUNK.  Then and if tested etc.
export that particular fix to RELEASE.

As it is, I think the whole trunk can be cp'ed to RELEASE (i.e. trash
RELEASE tree and start from this working version).

Then all new development starts again on TRUNK.

Nick
-- 
Free Software Foundation Associate Member 5508

Re: [Bashburn-info] 3.0 Beta 1

[Anders L. <and...@gm...>]

On Tuesday 07 October 2008 18:28:45 you wrote:
> On Tue, 07 Oct 2008 15:44:31 +0200
>
> Markus Kollmar <mar...@on...> wrote:
> > Anders Lindén wrote:
> > > On Tuesday 07 October 2008 15:11:50 you wrote:
> > >> Anders, we have a small problem with Beta 1!
> > >>
> > >> I have done yesterday some changes in the trunk (also the
> > >
> > > mentioned
> > >
> > >> swedish language updating).
> > >> Now I saw you have not moved all files for the release 3.0 from
> > >
> > > 'trunk'
> > >
> > >> to 'release' shortly before you created the release-package.
> > >
> > > Ouch! Which files are we talking about? I could add the missing
> > > files and do a quick re-release.
> >
> > Anders, I think that is not the best idea (it are some files like
> > "BashBurn.sh" and lang. files - and maybe I think Nick and maybe
> > others also did improvements since then).
> > So in such cases we should always take the whole thing to avoid
> > dependency-problems - if we can be shure nothing is broken - 
and i
> > think in this short time the trunk is relatively usable.
> >
> > >> I should had tell you this - so you thought that there was no 
major
> > >> changes in the trunk since you created the release branch.
> > >> In my humble opinion I think it would be good if we use 
following
> > >> process to make a release and to avoid such things in future:
> > >>
> > >>
> > >> 1. Like you did - tell others per mailing list shortly before
> > >> release whether it is ok to create a release for the main
> > >> developers, and tell the short time period in which the 
creation
> > >> is planned.
> > >>
> > >> 2. Then lock the trunk branch (via "svn lock") and move ALL 
files
> > >
> > > from
> > >
> > >> trunk to release.
> > >>
> > >> 3. Create package from release tree.
> > >>
> > >> 4. Unlock trunk branch.
> > >>
> > >>
> > >> Is this a way?
> > >
> > > Sounds like a good idea to me.
>
> Also what I meant was all changes go to TRUNK.  Then and if tested 
etc.
> export that particular fix to RELEASE.
>
> As it is, I think the whole trunk can be cp'ed to RELEASE (i.e. trash
> RELEASE tree and start from this working version).
>
> Then all new development starts again on TRUNK.
>
> Nick

I don't think we really have to nuke the release tree for each release, 
just create a new sub directory under it. One mistake we might have 
done with this release is that we just called it 3.0, even for beta 
releases. I think in the future we should create releases/3.1-beta1, 
beta2 and so on and then simply create release packages from those 
directories. 

Nothing new from trunk will go into those. What should be allowed to 
change in release is just release specific things like editing the 
installation script (Like I did with 3.0-beta1) or changing the version 
number.

What I think we should do now is to rename releases/3.0 to 
releases/3.0-beta1. After we get some bug reports and/or fix some 
things ourselves in trunk and we feel things are done, I'll create a 
releases/3.0-final (Or beta2 should we think it's necessary) from trunk 
and leave the beta1 directory alone. 

-- 
Anders Lindén
http://bashburn.dose.se

Re: [Bashburn-info] 3.0 Beta 1

[Nick W. <ni...@uk...>]

On Tue, 7 Oct 2008 18:45:38 +0200
Anders Lindén <and...@gm...> wrote:

> On Tuesday 07 October 2008 18:28:45 you wrote:
> > On Tue, 07 Oct 2008 15:44:31 +0200
> >
> > Markus Kollmar <mar...@on...> wrote:
> > > Anders Lindén wrote:
> > > > On Tuesday 07 October 2008 15:11:50 you wrote:
> > > >> Anders, we have a small problem with Beta 1!
> > > >>
> > > >> I have done yesterday some changes in the trunk (also the
> > > >
> > > > mentioned
> > > >
> > > >> swedish language updating).
> > > >> Now I saw you have not moved all files for the release 3.0 from
> > > >
> > > > 'trunk'
> > > >
> > > >> to 'release' shortly before you created the release-package.
> > > >
> > > > Ouch! Which files are we talking about? I could add the missing
> > > > files and do a quick re-release.
> > >
> > > Anders, I think that is not the best idea (it are some files like
> > > "BashBurn.sh" and lang. files - and maybe I think Nick and maybe
> > > others also did improvements since then).
> > > So in such cases we should always take the whole thing to avoid
> > > dependency-problems - if we can be shure nothing is broken - 
> and i
> > > think in this short time the trunk is relatively usable.
> > >
> > > >> I should had tell you this - so you thought that there was no 
> major
> > > >> changes in the trunk since you created the release branch.
> > > >> In my humble opinion I think it would be good if we use 
> following
> > > >> process to make a release and to avoid such things in future:
> > > >>
> > > >>
> > > >> 1. Like you did - tell others per mailing list shortly before
> > > >> release whether it is ok to create a release for the main
> > > >> developers, and tell the short time period in which the 
> creation
> > > >> is planned.
> > > >>
> > > >> 2. Then lock the trunk branch (via "svn lock") and move ALL 
> files
> > > >
> > > > from
> > > >
> > > >> trunk to release.
> > > >>
> > > >> 3. Create package from release tree.
> > > >>
> > > >> 4. Unlock trunk branch.
> > > >>
> > > >>
> > > >> Is this a way?
> > > >
> > > > Sounds like a good idea to me.
> >
> > Also what I meant was all changes go to TRUNK.  Then and if tested 
> etc.
> > export that particular fix to RELEASE.
> >
> > As it is, I think the whole trunk can be cp'ed to RELEASE (i.e.
> > trash RELEASE tree and start from this working version).
> >
> > Then all new development starts again on TRUNK.
> >
> > Nick
> 
> I don't think we really have to nuke the release tree for each
> release, just create a new sub directory under it. One mistake we
> might have done with this release is that we just called it 3.0, even
> for beta releases. I think in the future we should create
> releases/3.1-beta1, beta2 and so on and then simply create release
> packages from those directories. 
> 
> Nothing new from trunk will go into those. What should be allowed to 
> change in release is just release specific things like editing the 
> installation script (Like I did with 3.0-beta1) or changing the
> version number.
> 
> What I think we should do now is to rename releases/3.0 to 
> releases/3.0-beta1. After we get some bug reports and/or fix some 
> things ourselves in trunk and we feel things are done, I'll create a 
> releases/3.0-final (Or beta2 should we think it's necessary) from
> trunk and leave the beta1 directory alone. 

OK, but what I meant was that TRUCK (as it is) is tested upto NOW.  So
I thought that would become the beta1/2 or whatever.

But anyway, we are there :-)

Nick
-- 
Free Software Foundation Associate Member 5508

Re: [Bashburn-info] 3.0 Beta 1

[Anders L. <and...@gm...>]

On Tuesday 07 October 2008 18:54:48 you wrote:

> OK, but what I meant was that TRUCK (as it is) is tested upto NOW.  
So
> I thought that would become the beta1/2 or whatever.
>
> But anyway, we are there :-)
>
> Nick

Yes, that was the way it was supposed to work :-)
Oh well, we all learn from our mistakes (I'll try to, I promise).

From now on when trunk has been tested and deemed stable, I'll do a 
simple 'svn copy https://svn.inf.sgsp.edu.pl/svn/bashburn/trunk 
https://svn.inf.sgsp.edu.pl/svn/bashburn/releases/<version> -m 
"Release <version> is a go" and create a release package from the 
created directory. Hopefully this should work and we can avoid any 
crazyness like now.

(We can all be happy about that we're not designing control software 
for a nuclear plant. It's just a CD/DVD burner app after all :-) )

-- 
Anders Lindén
http://bashburn.dose.se

Re: [Bashburn-info] 3.0 Beta 1

[Nick W. <ni...@uk...>]

On Tue, 7 Oct 2008 19:00:11 +0200
Anders Lindén <and...@gm...> wrote:

> (We can all be happy about that we're not designing control software 
> for a nuclear plant. It's just a CD/DVD burner app after all :-) )

Melt down!  Burn baby, burn :-)

Nick
-- 
Free Software Foundation Associate Member 5508