On Thu, Jun 29, 2017 at 01:34:05PM +0800, ChangBo Guo wrote:
> Thanks tony for raising up this, better document this in some place :-)
For the record this was just added to the queens schedule [1]. The
deadline is this week but in reality early nest week would probably also
be accepted.
Yours T
Thanks tony for raising up this, better document this in some place :-)
2017-06-28 16:51 GMT+08:00 Thierry Carrez :
> Sean McGinnis wrote:
> > On Tue, Jun 27, 2017 at 02:47:30PM -0400, Doug Hellmann wrote:
> >> Excerpts from Tony Breeds's message of 2017-06-27 16:51:37 +1000:
> >>> Hi all,
> >>>
Sean McGinnis wrote:
> On Tue, Jun 27, 2017 at 02:47:30PM -0400, Doug Hellmann wrote:
>> Excerpts from Tony Breeds's message of 2017-06-27 16:51:37 +1000:
>>> Hi all,
>>> Up 'til now we haven't set a last release date for a stable branch
>>> approaching end of life. It seems like formalizing t
On Tue, Jun 27, 2017 at 02:47:30PM -0400, Doug Hellmann wrote:
> Excerpts from Tony Breeds's message of 2017-06-27 16:51:37 +1000:
> > Hi all,
> > Up 'til now we haven't set a last release date for a stable branch
> > approaching end of life. It seems like formalizing that would be a good
> >
Excerpts from Tony Breeds's message of 2017-06-27 16:51:37 +1000:
> Hi all,
> Up 'til now we haven't set a last release date for a stable branch
> approaching end of life. It seems like formalizing that would be a good
> thing.
>
> This comes up as we need time to verify that said release int
Hi all,
Up 'til now we haven't set a last release date for a stable branch
approaching end of life. It seems like formalizing that would be a good
thing.
This comes up as we need time to verify that said release integrates
well (at least doesn't break) said branch. So should we define a date