Re: LTSP 5.3 will be tagged tomorrow at 19:00 UTC

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

On 02/15/2012 02:01 PM, Michael Shigorin wrote:
> On Wed, Feb 15, 2012 at 01:28:36PM -0500, Stephane Graber wrote:
>> For these who aren't in #ltsp (you should), a lot of work has 
>> been done in trunk lately, to get rid of a lot of old code
> 
> Yay!
> 
>> and move most ltsp-build-client plugins into init scripts running
>> at boot time on the client.
> 
> Should have a look, what's the boot time impact like if it got
> measured already?

It's mostly removing files and moving some others, so if it takes more
than a second, I'd be worried (as in, we're doing something wrong).

The main advantage of this is that you can in theory install the LTSP
packages on a regular desktop machine and they won't do anything,
unless you reboot it with init=/sbin/init-ltsp, then it turns into a
thin client but without actually touching anything on the disk.

The goal for Ubuntu 12.10 is to basically have the ltsp-client
packages installed by default on Edubuntu, allowing to simply export
our install media as a fat chroot, so no more shipping chroots and
building chroots (for the most common cases).

I'm not sure we're there yet in the current trunk, but we're pretty
close and Alkis, Vagrant, Gadi and Marc have been doing quite a bit of
work to make that happen in 5.3.

> 
>> The current time line for tomorrow looks like: - 19:00 UTC => Tag
>> and release LTSP 5.3
> 
> ack
> 
>> After that, at least for Ubuntu, we'll be in bugfix only mode, so
>> as long as only bugfixes are being pushed to the trunk, I'll 
>> simply upload new versions. When we start getting new features in
>> the trunk, I'll instead start cherry-picking fixes one by one as
>> they are relevant for Ubuntu.
> 
> I postponed further forward-porting and merging of ALT-specific 
> things back in December but that definitely isn't something that is
> done right before someone's freeze; hope that Ubuntu isn't going to
> turn trunk into a maintenance branch though.

No, it won't, what I'm hoping for is to only see bugfixes to the
shared code for the next 20 days to a month after 5.3 is released,
essentially making 5.3.1 and 5.3.2 bugfix only releases.
Any change affecting just a single distro are definitely welcome as
they won't impact Ubuntu in any way.

I obviously don't have any authority to impose that to the other LTSP
developers, so at this point, I'm just hoping other contributors will
see a 20 days to a month period after 5.3 is released as a good idea
and as something beneficial for LTSP upstream as a whole.

I know Alkis, Marc and I won't do any feature change during these few
days, I think I can convince Vagrant pretty easily and Wim said he's
planning some distro changes but nothing in the common code.


>> Maintainers of other distributions, it'd be great if you could 
>> spend some time testing the current trunk on your distro and make
>> sure it works for you.
> 
> Indeed, if only my swappiness would decrease...
> 
> Thanks for your hard work, guys!
> 


- -- 
Stéphane Graber
Ubuntu developer
http://www.ubuntu.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQIcBAEBCgAGBQJPPATRAAoJEMY4l01keS1nSdkP/iPKvCmoBxVy7iG1UAwgT0w8
Av6ODchCoFHHgizyMtgZ5Cu0zrEVYmO9sbQt7P8FH7ATlk1jKPtDQM9HQl4kSodJ
aegcQWIS5+eKy1MJ4jrTuKPNerf149vYfdnRSOVIr5JRNcrVmA4IetjafZOoslhu
GvQnOmnuFFZBHh6PmFfCC2OpBzgw02Z7bZ2MzPxonlzqF4h+A32YF77xGqeu5QFR
ltsahZ2bH8lV0T93O+GFEmUW+es2Hvm2VLPNlrKg1KnE1POTyqmqup+3AVSNbG/U
3Z5k2sXwoND2cQKHs1j67O4t1cenehzbKtDkn8g90cEG0eV7ZJhGTcPLmXx2/Sig
QEcb1z2qtnYqx2aqn8rv8s4Qa23dEhkGgfGglpKK3K4jxx79J7dslHZqIpuuE44B
CBT5wZ0UYqrfPff0kvxolEWQbh+odU8jWiJo++Sw3pPs8D4r5jitlKikGxazBWHO
w3u9R1TsOgr2ZgJEW3uzAyiHQXXL6JxjkwHsbtCqIKijn601LoMg9EcoC7YkPQKX
gw5ZXwS8n3D1cK+X0yK5EsNhYg9Dicm2A6k+QACV4ijEBASM1QpLuVzPnc0oGxzh
jH+kcVkNfyjQp7x9sIfxccU6D8OBEgLZ0NfrtAGzFoFSkFzdYeTdhDZ5MKoz4EUO
OA/9OFDQe9NVPCcpGZVT
=z2Ia
-----END PGP SIGNATURE-----

------------------------------------------------------------------------------
Virtualization & Cloud Management Using Capacity Planning
Cloud computing makes use of virtualization - but cloud computing 
also focuses on allowing computing to be delivered as a service.
http://www.accelacomm.com/jaw/sfnl/114/51521223/
_____________________________________________________________________
Ltsp-developer mailing list.   To un-subscribe, or change prefs, goto:
      https://lists.sourceforge.net/lists/listinfo/ltsp-developer
For additional LTSP help,   try #ltsp channel on irc.freenode.net