[riot-devel] Release 2016.10

Martine Lenders mlenders at riot-os.org
Wed Oct 26 18:04:33 CEST 2016

with the last ACK'd PR of yesterdays Hack'n'ACK still waiting for a re-ACK
I think it's time for a short update and what's still ahead before the
feature freeze next Monday.

There are still 122 PRs open for this release. Some of those already have
low change of getting merged, but let's give it a try. To make things
easier to manage I sorted the open PRs into categories. Two of them (High
priority reviews and Low-hanging nice-to-haves) only have 14 PRs left
together (see [1]). @maintainers please focus your reviews on those until
Monday, especially those that are *not* marked as bug (bugs can always be
fixed after feature freeze).

There are also 128 issues open. Some of them have PRs open that are in the
categories above and some should be fixable rather straight forward. I put
those into the category "Fixable for release" under [1]. Please also have a
look if you can manage to fix those until Monday.

Happy hacking!

[1] https://github.com/RIOT-OS/RIOT/projects/4

2016-10-18 18:13 GMT+02:00 Martine Lenders <mlenders at riot-os.org>:

> Good evening,
> I finally sifted through all open issues and PRs and evaluated them
> for the release [1]. If I missed one, please feel free to point them
> out / move them to the respective columns.
> Feel  also free to dig into the columns to find some issues that need
> fixing until the feature freeze, especially "Fixable for release" (but
> also "Open feature and enhancement requests" and "Known issues" if you
> are more ambitious ;-))
> These are the categories for now:
> # Open feature and enhancement requests
> Feature or enhancement requests I think to be important enough to get
> a boost during the two weeks of sprint until the feature freeze (but
> won't necessarily get merged to this point)
> # Known issues
> Bugs or failing applications that are known by now.
> # Fixable for release
> Low-bar issues (both "Known issues" and "Open feature and enhancement
> requests") that might be fixable until the release to my assessment
> (or issues were a corresponding non-WIP-PR already exists).
> # Under review for release
> Open PRs marked with the "Release 2016.10" milestone.
> # Fixed issues from last release
> Issues mentioned in the "Known issues" section of last release's
> release notes and that are now fixed
> # Fixed issues
> Issues that were fixed during the release (and are not in "Fixed
> issues from last release")
> # New features & platforms
> PRs that introduced new features or platforms.
> # Merged
> PRs that were merged during the release but are no new features or
> platforms.
> Since both "Known issue" and the "Under review for release" columns
> are rather large now, I'll to get things a little bit more manageable
> in the next few days.
> @maintainers: The project panel is now free to be edited by anyone.
> Cheers,
> Martine
> [1] https://github.com/RIOT-OS/RIOT/projects/4
> 2016-10-14 8:04 GMT+02:00 Martine Lenders <mlenders at riot-os.org>:
> > Dear release-hungry IoTlers,
> > I'm currently in the process of reevaluating the Pull Requests and
> > issues for our autumn release [1]. While I'm doing this, here a few
> > important dates for the release:
> >
> > * Feature Freeze: Monday, Oct 31 (we have a Hackathon at Wikimedia
> > coming up Oct 29 [2], so that's why it so late)
> > * Estimated Release date: Monday, Nov 7
> >
> > So let's get merging.
> >
> > Cheers,
> > Martine
> >
> > [1] https://github.com/RIOT-OS/RIOT/projects/4
> > [2] https://www.wikimedia.de/wiki/LadiesthatFOSS
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.riot-os.org/pipermail/devel/attachments/20161026/983462e5/attachment.html>

More information about the devel mailing list