You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Nightlies get published around 11am pacific time, judging by the publication timestamps in npm, which is a little odd because it can capture a small part of a day's work for most of the team (most of the team is in the pacific time zone, so most PRs get merged between 9am and 5pm, pacific). IMO, it would make more sense to actually snapshot and publish the nightlies overnight, when contributions are much less likely - between midnight and 1am pacific time, perhaps.
For example, #12259 and #12258 I think made the cutoff for the previous nightly (they were merged around 11am on the dot, so it's iffy), but everything else merged during that day's work day (#12274, #12276, #12280, #12251, #12248) did not, and is waiting for the next nightly.
The text was updated successfully, but these errors were encountered:
Nightlies get published around 11am pacific time, judging by the publication timestamps in npm, which is a little odd because it can capture a small part of a day's work for most of the team (most of the team is in the pacific time zone, so most PRs get merged between 9am and 5pm, pacific). IMO, it would make more sense to actually snapshot and publish the nightlies overnight, when contributions are much less likely - between midnight and 1am pacific time, perhaps.
For example, #12259 and #12258 I think made the cutoff for the previous nightly (they were merged around 11am on the dot, so it's iffy), but everything else merged during that day's work day (#12274, #12276, #12280, #12251, #12248) did not, and is waiting for the next nightly.
The text was updated successfully, but these errors were encountered: