[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-i18n-doc
Subject:    Re: 4.6.5 tagging date and scripty branches
From:       "G.Sora" <g.sora () tiscali ! it>
Date:       2011-06-25 15:18:14
Message-ID: 4E05FC36.5050507 () tiscali ! it
[Download RAW message or body]

On 25/06/2011 17:07, Albert Astals Cid wrote:
> A Saturday, June 25, 2011, G.Sora va escriure:
>    
>> On 25/06/2011 16:26, Albert Astals Cid wrote:
>>      
>>> Are we sticking to
>>> http://techbase.kde.org/Schedules/KDE4/4.6_Release_Schedule
>>>
>>> June 30, 2011: KDE 4.6.5 tagging
>>>
>>> I'm asking because at the moment regarding scripty l10n branch processing
>>>
>>>    trunk is disabled
>>>    stable is targetting 4.6
>>>
>>> Given that the 4.6.5 tag date is June 30 and the 4.7.0 tag date is July
>>> 20 i was wondering if we can live from now to 30 June with scripty in
>>> trunk disabled and the make it
>>>
>>>    trunk targets master
>>>    stable targets 4.7
>>>
>>> And that is because switching trunk to 4.7 "is a non trivial amount of
>>> work" and i would prefer to avoid it for just 5 days. That is of course
>>> assuming 4.6.5 tagging is done on time.
>>>
>>> Comments?
>>>
>>> Albert
>>>        
>> Hi,
>> from a practical point of view, for instance, I am working just on 4.7
>> branch (trunk for now).
>>   From here on, what happens if I work on trunk?
>> Or do I have to switch to stable (maybe after 30 june)?
>> No problem to survive without scripty for those days, I just need to
>> know where to translate for not missing work.
>>      
> Once i switch trunk to be master and stable to be 4.7 (will notify the list
> but hopefully will be around 30 June/1 July) I will copy all the translations
> in master to stable and 4.7.0 will be released from there.
>
> This means that any upload you do to master will only be released with 4.8.0
> so it will probably makes sense for you to switch to stable for a while so
> your translations end up in 4.7.1, 4.7.2, etc.
>
> This is of course only true for "main modules" like kdebase, kdelibs, kdepim,
> kdegraphics, etc. For extragear modules they release on their own so you have
> to keep an eye on the list listening for release mails of each of the software
> maintainers.
>
> Albert
>    
Thank you for your help , now I know what to do on next days,
Giovanni

[prev in list] [next in list] [prev in thread] [next in thread]