bashburn-info

[Bashburn-info] BashBurn branches

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

Ok, I created branches on the svn repo. The branch trunk is where
anything goes. Things are allowed to break there.

In the releases directory we will create a branch when it's time to
stabilize for a release. I added a 3.0 directory there now which is
where we will just make sure things work. No new features are allowed to
be added in releases, only bugfixes.

So, the gettextification will take place in trunk, and just
stabilization and bug fixing in releases/3.0. When we think things are
stable enough, I'll create a release from the release/3.0 branch and
post it to the webpage.

Oh, and if I messed something up let me know. I'm no master of svn.
-- 
Anders Lindén
http://bashburn.sf.net

Re: [Bashburn-info] BashBurn branches

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

On Fri, 12 Sep 2008 01:28:31 +0200
Anders Lindén <and...@gm...> wrote:

> Ok, I created branches on the svn repo. The branch trunk is where
> anything goes. Things are allowed to break there.
> 
> In the releases directory we will create a branch when it's time to
> stabilize for a release. I added a 3.0 directory there now which is
> where we will just make sure things work. No new features are allowed
> to be added in releases, only bugfixes.
> 
> So, the gettextification will take place in trunk, and just
> stabilization and bug fixing in releases/3.0. When we think things are
> stable enough, I'll create a release from the release/3.0 branch and
> post it to the webpage.
> 
> Oh, and if I messed something up let me know. I'm no master of svn.

Good stuff - all appears to work fine.

Anders, I guess you are the one that decides what goes into the releases
tree[s], and the rest of us just use the trunk?

Nick
-- 
Free Software Foundation Associate Member 5508

Re: [Bashburn-info] BashBurn branches

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

fre 2008-09-12 klockan 15:09 +0100 skrev Nick Warne:
> On Fri, 12 Sep 2008 01:28:31 +0200
> Anders Lindén <and...@gm...> wrote:
> 
> > Ok, I created branches on the svn repo. The branch trunk is where
> > anything goes. Things are allowed to break there.
> > 
> > In the releases directory we will create a branch when it's time to
> > stabilize for a release. I added a 3.0 directory there now which is
> > where we will just make sure things work. No new features are allowed
> > to be added in releases, only bugfixes.
> > 
> > So, the gettextification will take place in trunk, and just
> > stabilization and bug fixing in releases/3.0. When we think things are
> > stable enough, I'll create a release from the release/3.0 branch and
> > post it to the webpage.
> > 
> > Oh, and if I messed something up let me know. I'm no master of svn.
> 
> Good stuff - all appears to work fine.
> 
> Anders, I guess you are the one that decides what goes into the releases
> tree[s], and the rest of us just use the trunk?
> 
> Nick

I think that when we all think it's time for a release I'll create a
branch with that name. What goes in there is up to all of us but I
suggest that only bugfixes and things like translation updates are
allowed in there. Nothing new should go in there unless you can give a
really good reason why it should.
Sounds good to you guys?

-- 
Anders Lindén
http://bashburn.sf.net

Re: [Bashburn-info] BashBurn branches

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

On Friday, Sep 12th 2008 at 10:34 -0000, quoth Anders Lind?n:

=>fre 2008-09-12 klockan 15:09 +0100 skrev Nick Warne:
=>> On Fri, 12 Sep 2008 01:28:31 +0200
=>> Anders Lind?n <and...@gm...> wrote:
=>> 
=>> > Ok, I created branches on the svn repo. The branch trunk is where
=>> > anything goes. Things are allowed to break there.
=>> > 
=>> > In the releases directory we will create a branch when it's time to
=>> > stabilize for a release. I added a 3.0 directory there now which is
=>> > where we will just make sure things work. No new features are allowed
=>> > to be added in releases, only bugfixes.
=>> > 
=>> > So, the gettextification will take place in trunk, and just
=>> > stabilization and bug fixing in releases/3.0. When we think things are
=>> > stable enough, I'll create a release from the release/3.0 branch and
=>> > post it to the webpage.
=>> > 
=>> > Oh, and if I messed something up let me know. I'm no master of svn.
=>> 
=>> Good stuff - all appears to work fine.
=>> 
=>> Anders, I guess you are the one that decides what goes into the releases
=>> tree[s], and the rest of us just use the trunk?
=>> 
=>> Nick
=>
=>I think that when we all think it's time for a release I'll create a
=>branch with that name. What goes in there is up to all of us but I
=>suggest that only bugfixes and things like translation updates are
=>allowed in there. Nothing new should go in there unless you can give a
=>really good reason why it should.
=>Sounds good to you guys?

Sounds good to me. But since I haven't read the book yet, how do I access 
the branch?

-- 
steveo at syslang dot net TMMP1 http://frambors.syslang.net/
Do you have neighbors who are not frambors? Steve Orr
Who should we vote for? http://steveo.syslang.net/electionrec-2008.5/

Re: [Bashburn-info] BashBurn branches

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

Anders Lindén wrote:
> fre 2008-09-12 klockan 15:09 +0100 skrev Nick Warne:
>   
>> On Fri, 12 Sep 2008 01:28:31 +0200
>> Anders Lindén <and...@gm...> wrote:
>>
>>     
>>> Ok, I created branches on the svn repo. The branch trunk is where
>>> anything goes. Things are allowed to break there.
>>>
>>> In the releases directory we will create a branch when it's time to
>>> stabilize for a release. I added a 3.0 directory there now which is
>>> where we will just make sure things work. No new features are allowed
>>> to be added in releases, only bugfixes.
>>>
>>> So, the gettextification will take place in trunk, and just
>>> stabilization and bug fixing in releases/3.0. When we think things are
>>> stable enough, I'll create a release from the release/3.0 branch and
>>> post it to the webpage.
>>>
>>> Oh, and if I messed something up let me know. I'm no master of svn.
>>>       
>> Good stuff - all appears to work fine.
>>
>> Anders, I guess you are the one that decides what goes into the releases
>> tree[s], and the rest of us just use the trunk?
>>
>> Nick
>>     
>
> I think that when we all think it's time for a release I'll create a
> branch with that name. What goes in there is up to all of us but I
> suggest that only bugfixes and things like translation updates are
> allowed in there. Nothing new should go in there unless you can give a
> really good reason why it should.
> Sounds good to you guys?
>
>   
Sounds good, Anders.
;-)