Re: Update Sugar packages

2012/8/20 Lars Vogdt <[email protected]>:
> Hi
>
> On Sat, 18 Aug 2012 15:41:23 +0800 Xin Wang wrote:
>> Because 11.4 will reach its end of life soon, I'd like to disable
>> build for 11.4 by now, so that packages for 11.4 will not affected by
>> updates.
>
> 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.

>
>> In other words, we will only support 12.2, Factory, and partially 12.1
>> for future updates. Is it OK to do that?
>
> Absolutely. ...and thanks a lot for your work on those packages!
>

My pleasure. :)

> With kind regards,
> Lars
>



-- 
Xin Wang (http://dram.me/)
-- 
To unsubscribe, e-mail: [email protected]
To contact the owner, e-mail: [email protected]