Re: Update Sugar packages

On Di 21 Aug 2012 00:31:10 CEST Xin Wang <[email protected]> wrote:
>> Jip: we do the same for old releases (means: the OBS repo is in a
>> "build disabled" state). So users who have added the repo to their list
>> would only get new packages once some packager enabled build for that
>> repository explizitely.
>>
>> That is the fact in Education for 11.4 already - and I like to do it
>> also for 12.1 and maybe even 12.2 once 12.2 is released (objections?).
>>
>> That way, packagers can concentrate on the upcoming release and just
>> need to touch a package for old releases once a user requests an update
>> or the packager wants to maintain it for old releases.
>>
>> That would drastically reduce the "refresh time" of the Education repo
>> for endusers as the repo metadata will only change if an important
>> update is released for their distribution.
>>
>
> What about branching a subproject based on each Education release?
> That way further development will not affect it, and we can easily
> apply patches in that branch when some bug is encountered.

Well, this was not necessary until now. I'm just aware of a handful  
packages (from > 400) that were reported via Bugzilla and needed a fix  
for an old release. Patching them and re-enabling build in the  
Education project itself was much easier than providing a branch of  
the whole Education project. Further development was also not affected  
as those packages were broken on younger releases, too.

But I won't prevent a branch if someone else really likes it - I'm  
just curious what would be better than now for the Education project:  
currently nobody has to take care of any branch or sub-project.  
Everything is in the plain Education project and development takes  
also place there: just for the upcoming releases only.

With kind regards,
Lars

-- 
To unsubscribe, e-mail: [email protected]
To contact the owner, e-mail: [email protected]