-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Hi Kim,

It's in the "current" branch now. If some submodules lack it, please
create it there!

It would be awesome if you re-applied the vyatta patches to the most
recent kernel as you did for lithium. I started looking, but you
probably remember the procedure better than me.
This is what is blocking Tom from full live testing of his changes.
Since overlayfs is now in the kernel, once patches are there, we can
probably keep pulling updates directly from the kernel, with some
checking if they don't overwrite those patches.

On 01/21/2016 01:29 PM, Kim Hagen wrote:
> Hi Daniil,
>
> I agree with all you points.
>
> I have made some efforts to porting to Jessie twice but I did not know
what way it was going.
> So if there can be made a branch for Jessie and we can agree on the
name (Beryllium, Boron)
> Maybe we can go forward.
>
>
> -----Oorspronkelijk bericht-----
> Van: Daniil Baturin [mailto:dan...@baturin.org]
> Verzonden: donderdag 21 januari 2016 8:19
> Aan: vyos-developers@lists.tuxis.nl
> Onderwerp: [Vyos-developers] End of squeeze-lts support, lithium, and
what to do next
>
>
> Hey everyone,
> This is as much of a technical proposal as a rant, so these two parts
are separated for you convenience. ;)
>
> Squeeze-LTS support ends in February this year. This is our last call.
> Either we drop squeeze, or we are left to build every security update
from source, which we don't have nearly enough hands for.
>
> Proposal:
> 1. Stop working on lithium and release just what we have, all
unimplemented tickets put on hold.
> 2. Close the codebase for any commits not related to porting to jessie
until jessie port if fully functional.
> 3. When it's ready, limit it to security updates and merging patches
from occasional contributors and focus on 2.0 ourselves.
>
> Rant:
> Contribution activity has been very low last year. Myself included.
> Personally, I'm very tired of this aging codebase. Quite often I look
at the ticket list or get an idea, but then I look at the code that is
to be modified and think "no, not this again".
> No matter how we think about it, VyOS is not about making new exciting
things anymore even when we port it to jessie, as there are fewer and
fewer things we can do without hitting the limitations of the old
design. Even porting to jessie, which could have been just rebuilding
packages, is absurdly hard.
>
> I believe I'm not the only one who feels this way, otherwise there
would be a lot more activity.
>
> Paying VyOS 1.x our last respect by porting it to jessie and thus
enabling everyone including ourselves use it in its current state until
jessie support ends is probably best we can do. Meanwhile we can make
new exicting things again without breaking our moral obligations to our
users.
>
> Let me know what you think.
>
>
>
>
> _______________________________________________
> Vyos-developers mailing list
> Vyos-developers@lists.tuxis.nl
> https://lists.tuxis.nl/listinfo/vyos-developers

- -- 
#!/usr/bin/env perl
@a=split(//, "daniil @ baturin  .  org" );# Daniil Baturin
@b=split(//,q/Px%!+o0Q6lh*7dp$.@8#%|y{/);while($i<24){$_.=
chr((ord(@b[$i])-ord(@a[$i])+62)%94+32);$i++};print"$_\n"#
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQIcBAEBCAAGBQJWoIsBAAoJEEcm35UR4K8f3NIQAO8oAtG9ffU+Oy/zU0HVGzJ0
eQ86in5OuKarqpkb24uXZB/w4FSNLCJkeB9m24URUlHHqutclXwaCdBO32te/8dm
bVcrGbaNx2tyapRiWHzatlgPQtAq74sXuFC5M8F7nP3tTzdXT9RCUzTmvPoL/2Nx
4koTqOqaHKE/40gk2azKL7SxJBHjsboTBhm6I8ZjtwslbPR6owMZ2BesCp6hkr+a
9mtgow27k+xku8RMAiOX6t4WYybBh1R9V7oZH1LbyicSZRMIsh15GATecTSPgAHw
G8oDNmD5H+Wbt43/rWb3V591dC01U2V5tRc+gfgJ12wwTETLnRWhnAgzTrfh7UKr
xdGdC4wkMLzbkSUl3m7jzv5RZJxfTAGAqooDmTXT+IYk2ow4OOZkcBkB+WqPfm6U
h9aeAVJsbnkyAvp10u5/qJXl1WNVvyI6xhiXk2T+PzkIE9oQJRXkQkpyGUTmAxcB
w3lLI44t6MWqQraoFmA8NXcC1vcboVBlP4SqZ5xo0CzWAV6EFeiNZ7dbv6XHuNG8
oLAA2FnuRJYp1VNNIHvoARxFo7Q2tZnmzZgCC+MYk796GmluK8mi05XxnTXkGkPH
nInJaqpTJ84g93juMFFR+gPvptSLalMr6f7fxsuJA8aNGUmjkcDxDQy2bU+zhucM
ycx4vpEij/W7I1G3LB0q
=eUcu
-----END PGP SIGNATURE-----


_______________________________________________
Vyos-developers mailing list
Vyos-developers@lists.tuxis.nl
https://lists.tuxis.nl/listinfo/vyos-developers

Reply via email to