Hi Dimitri, Thank you for the detailed reply!
If I understand correctly, if a CVE issue is found after 2022 in Upstart (very unlikely I guess), it won't get fixed, right? Best, John Lin Dimitri John Ledkov <x...@ubuntu.com> 於 2017年9月7日 週四 下午11:34寫道： > On 7 September 2017 at 07:52, 林自均 <johnl...@gmail.com> wrote: > > Hi folks, > > > > From the mailing list activities, I can see the development of Upstart is > > getting slower. I would like to know if Upstart developers are planning > to > > stop maintaining it, i.e. claiming that none of the bugs will be fixed? > > > Upstart project is stable, and users/products may continue to use it as is. > > Out of major upstart users all of them have moved on. Commercial and > security support for upstart will seize to be provided by canonical > once the last Ubuntu release shipping upstart lapses. > In practical terms it means: > - for system init (pid 1) end of life / end of extended security > maintainance of the 14.04 LTS expected in 2019/2020 timeframe > - for user init (session init) end of life / end of extended security > maintaince of the 16.04 LTS expected in 2021/2022 timeframe > > All products and users are encouraged to move to other init systems, > either smaller/minimalistic init implementations or general purpose > init systems like systemd. > > upstart has been removed from Ubuntu Artful, and thus will not be part > of Ubuntu 17.10 or 18.04 LTS releases. > upstart is also no longer available in Debian. > > -- > Regards, > > Dimitri. >
-- upstart-devel mailing list upstart-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/upstart-devel
