Hi,
> Personally, I'd prefer to start consolidating MATE 1.16 now and I would love
> to see it long term supported by upstream.
I'm afraid we won't be able to add LTS support... our team is too small for
that.
I'll try to submit patches for most important bugs (for example, I have a list
for
Hi,
>>> Or does something else count as transition? E.g. if some of MATE
>>> packages would change dependency from libmateweather to libgweather.
>>
>> No. This should be fine.
>
> That's fine indeed. Porting your apps (or even libraries, as long as you don't
> break the ABI) from a library to
On 09/10/16 00:22, Mike Gabriel wrote:
> Hi Vlad,
>
> thanks for taking this initiative of communication. Much appreciated.
>
> I try to give some answers, Niels may jump in and correct me, if necessary.
>
> On Fr 07 Okt 2016 14:51:47 CEST, Vlad Orlov wrote:
>
>> Hi,
>>
>>> It depends on what
Hi Vlad,
thanks for taking this initiative of communication. Much appreciated.
I try to give some answers, Niels may jump in and correct me, if necessary.
On Fr 07 Okt 2016 14:51:47 CEST, Vlad Orlov wrote:
Hi,
It depends on what the MATE release includes. If it involves a
transition (e.g.
Hi,
> It depends on what the MATE release includes. If it involves a
> transition (e.g. ABI / API bumps), then you are looking at 5th of
> November as deadline.
Hmm... does it mean changes in soname of some library from MATE
that will cause package name change? E.g. libmate-desktop-2.so ->
Vlad Orlov:
> Hi all,
>
Hi :),
I am moving this to debian-release with the MATE packaging team as CC.
(Also BCC'ed to debian-de...@lists.debian.org)
> I'm one of the upstream developers of MATE desktop environment. Current
> version, 1.16, just reached Unstable and should make it into Testing
6 matches
Mail list logo
