Thomas Klausner <wiz%NetBSD.org@localhost> writes: > On Wed, Jun 27, 2018 at 12:23:39PM +0900, Ryo ONODERA wrote: >> Hi, >> >> From: maya%netbsd.org@localhost, Date: Wed, 27 Jun 2018 01:51:43 +0000 >> >> > On Wed, Jun 27, 2018 at 09:45:57AM +0900, Ryo ONODERA wrote: >> >> Hi, >> >> >> >> From: maya%netbsd.org@localhost, Date: Wed, 27 Jun 2018 00:36:14 +0000 >> >> >> >> > On Wed, Jun 27, 2018 at 08:55:23AM +0900, Ryo ONODERA wrote: >> >> >> Hi, >> >> >> >> >> >> Latest Firefox web browsers are released on June 26, 2018. >> >> >> I would like to update www/firefox to 61.0 for security and new features. >> >> >> 60 release branch is ESR and I would like to create www/firefox60 package >> >> >> for 60.1.0 release. >> >> >> >> >> >> Can I update and create the packages of Firefox web browsers >> >> >> during freeze? >> >> >> >> >> >> Thank you. >> >> >> >> >> >> -- >> >> >> Ryo ONODERA // ryo%tetera.org@localhost >> >> >> PGP fingerprint = 82A2 DC91 76E0 A10A 8ABB FD1B F404 27FA C7D1 15F3 >> >> > >> >> > Please do, thanks! >> >> >> >> I have no idea about current pkgsrc-pmc members. >> >> Your message is the approval from pkgsrc-pmc? >> >> >> >> Thank you. >> > >> > it's not, but it saves me either the work for pulling it up to stable >> > immediately after the freeze or the guilt for not doing the work. >> > >> > firefox release notes for ESR is usually 'list of 10 vulnerabilities we >> > fixed' and nothing else. >> >> Package creation is prohibited by default during freeze. >> And update of www/firefox is closely related to creation of >> www/firefox60. >> >> I want pkgsrc-pmc approval. > > Please go ahead. Agreed. In particular the real concern is breaking a working firefox 60 on any platform, and moving the current package to firefox60 basically ensures that anybody who would have had working 60 still will, even if there are problems in 61.
Attachment:
signature.asc
Description: PGP signature