shoefoki.blogg.se - Adblock plus waiting for traffic on port 2020

#Adblock plus waiting for traffic on port 2020 code
#Adblock plus waiting for traffic on port 2020 windows

The Windows builder has been updated to VS2019 16.6.1.Build time is now about 30% faster because of this. The Windows builder now uses 4 Xeon cores and 16 GB ram.Builder performance was enhanced by using reserved instances.We will be able to use the Mozilla crash-stats till Q2 2021.įixed Infrastructure Stuff Since Last Meeting The date we need to switch has been postponed by Mozilla.Thunderbird is also also affected and must set up their own server. We need a breakpad server for submitting crash reports.We are waiting on some more info from Mozilla about subdomains before we progress with others. Domain transfer from Mozilla is now underway.We are waiting for Mozilla to transfer the SeaMonkey domains to SeaMonkey e.V.Other than azure hosting options because of price are also evaluated.Some Capacity planning to find the best price/performance ratio is carried out.Even buildbot had some version specific files outside the tree. Discussion for later when setting up jenkins.So currently no plans to do this for SeaMonkey. This would need backports but is not 100% native (needs Wine).Mozilla switched Windows builds to cross compile on Linux.

IanN remarked that they are tied to the version in the tree.frg thinks we should move the config files for building out of the source tree as much as possible.ewong waits for info from mhoye to be able to work out traffic requirements.Incremental updates need to be done whenever possible later.Cloning the mozilla- repos is problematic.Also evaluation of Ansible and Terraform going together with it is done.ewong is making progress setting up automated build jobs.Jenkins is being set up on the builders.

#Adblock plus waiting for traffic on port 2020 code

ewong has been looking at Kallithea, RhodeCode and other similar tools which are needed later to automate source code management for non mozilla repos (tools, website and others).

We are building up a new infrastructure using Azure.

We want to create a gitlab patch/fixes repo for classic XUL extensions.

The project areas on the website need further updates to reflect the current responsibilities after some long time developers and maintainers left the project.

We should assign people to the open items. (who needs to do what that hasn't been recorded in a bug) 1.9 Roundtable - Personal Status Updates.1.7.2 2.57.x next esr release branch (future).1.6 Extensions and Plugins Compatibility Tracking.1.4 Fixed Source Tree Stuff Since Last Meeting.1.3 Status of the SeaMonkey Source Tree.1.2.1 Fixed Infrastructure Stuff Since Last Meeting.1.2 Status of the SeaMonkey Infrastructure.