Hi Galen,
For my part, I think 6 months is reasonable and the dates are sane. To the
extent I assist with back-porting patches, etc. I'm happy to commit to
continued support for 3.1.
Thanks,
-b
On Mon, Oct 15, 2018 at 5:00 PM Galen Charlton
wrote:
> Hi,
>
> We've discussed [1][2] the notion
Hi,
It's now time to decide who will be Release Manager for the spring
2019 release of Evergreen, Evergreen 3.3.
The Release Manager does not have to be a core committer, but does
need to be familiar with Git and have already contributed
substantially to the Evergreen project whether it be code
Hi,
We've discussed [1][2] the notion of extending the community support
period for Evergreen 3.1 as part of easing the transition away from
the XUL staff cilent, but I cannot find anywhere that we set a date on
that extension. I think we should do so so that we can update the EOL
page [3].
So,