software call agenda notes 02/06/2007

[Andres Salomon]

Andres Salomon wrote:
> Christopher Blizzard wrote:
> [...]
>>   - need to tell J5 that a new kernel is available? don't need that.
>>   - What else goes into the build?
>>     - OS components that change
>>     - both stable and unstable?
>>     - master == stable, experimental == unstable
>>     - andres, file trac bug for url for j5 to pull into the tree from
>> master
>>   - any risk here?  need to inform devel at laptop.org that they commit to
>> the right branch
>>
> 
> Here's what I propose:
> 1) Merge master w/ experimental.  Since b2 is done, then we can start
> using 2.6.20 plus misc other patches we've put into experimental.
> 2) Immediately branch 'stable'. The autobuilding scripts will be
> changed, and 'master' will end up in d.l.o/~dilinger/RPMS/experimental,
> and 'stable' will end up in d.l.o/~dilinger/RPMS.

Er, lexdysia.  'master' will end up in d.l.o/~dilinger/experimental/RPMS.