Hello all,

This is a final reminder that the normal cutoff for new features in 3.1 is
by end-of-day today.  Once again, here are the bugs in play:

https://bugs.launchpad.net/evergreen/+bugs?field.status%
3Alist=NEW&field.status%3Alist=CONFIRMED&field.status%
3Alist=TRIAGED&field.status%3Alist=INPROGRESS&field.
status%3Alist=INCOMPLETE_WITH_RESPONSE&field.status%3Alist=
INCOMPLETE_WITHOUT_RESPONSE&field.importance%3Alist=
WISHLIST&field.milestone%3Alist=83887&field.tag=pullrequest&field.tags_
combinator=ANY&search=Search&orderby=id&start=0

I know that a number of those bugs are well in progress, so I expect we'll
get through a number of them.  Thank you for all the testing and tweaking
efforts so far!

What happens next?  I do not plan to cut the beta until later on Friday, so
we will have a day or so buffer to wrap things up and apply final
adjustments.  Please continue to push normally through the end of the day
today.  For tomorrow and Friday, small stragglers may still be allowed, but
please run them by me first, as at that point I will reserve the right to
hold out anything which seems likely to destabilize the release.

I will have limited availability this morning, but will be glued to the
keyboard for most of the afternoon through evening to help test and to
answer questions.

Keep up the good work!

Sincerely,
Dan

On Mon, Feb 19, 2018 at 12:43 PM, Daniel Wells <dbwe...@gmail.com> wrote:

> Hello all,
>
> At some point in the last few weeks, I realized that I had broken one of
> the "rules" of release management.  The period between feature-slush and
> feature-freeze is best attended to with undivided attention, but at it
> would turn out, one of the two weeks for that period coincided with a
> certain major library developer conference.
>
> While we still have another week under the original timeline, I have
> decided to proactively extend the feature freeze period by a few days.  The
> new feature-freeze cutoff is now, *Wednesday, Feb. 28*.  This was
> originally scheduled as the beta release day, so that is being pushed back
> by two days to *Friday, March 2*.  There are no plans to adjust any later
> dates in the schedule at this time.
>
> So, for between now and next Wednesday, here's a link to the 3.1-targeted
> feature ("Wishlist") branches needing attention:
>
> https://bugs.launchpad.net/evergreen/+bugs?field.status%
> 3Alist=NEW&field.status%3Alist=CONFIRMED&field.status%
> 3Alist=TRIAGED&field.status%3Alist=INPROGRESS&field.
> status%3Alist=INCOMPLETE_WITH_RESPONSE&field.status%3Alist=
> INCOMPLETE_WITHOUT_RESPONSE&field.importance%3Alist=
> WISHLIST&field.milestone%3Alist=83887&field.tag=pullrequest&field.tags_
> combinator=ANY&search=Search&orderby=id&start=0
>
> At the time of writing, there are 19 items in this list.  Since we are
> past feature slush, this list should not grow, but if after seeing this
> list you realize there is something missing which you expected to see here,
> please let me know.
>
> Finally, just because we are concentrating on feature pushes for the
> coming days, please do not hesitate to push in bug-fix branches as well.
> Here is a simple link including a list of all bugs targeted for 3.1 at this
> time:
>
> https://launchpad.net/evergreen/+milestone/3.1-beta
>
> Thank you!
>
> Sincerely,
> Dan
>

Reply via email to