[riot-devel] Feature freeze for Release 2019.01
Dear RIOTers, the feature freeze (for major impact new features) will be effective at midnight. As a gentle reminder: the final feature freeze (for other PRs) is January 18th. Wishing you a happy code/polish/review/merge sprint, Cheers, Alex & Emmanuel > ___ devel mailing list devel@riot-os.org https://lists.riot-os.org/mailman/listinfo/devel
[riot-devel] Feature freeze for upcoming release
Dear Community, We are about to focus on the next RIOT release. Feature freeze will take place at the end of the week (Sunday 17th July) and the plan is to get the 2016.10 release out by October 31st. As of now, we still have 114 PRs and 75 open issues marked for the release, a huge number that of course cannot be managed as is. So I ask everyone, to take some time and look through his/her own PRs and issues and bring them up to speed or let them re-marked for the next release. Me and Kaspar will take a look through the current issues/PRs and try to postpone as many as necessary. The goal of this release is to fix major bugs, and merge the most essential new features. So I encourage everyone again to focus on testing and reviewing for the next days, so we can merge as many open PRs as possible before the feature freeze! I have also created an empty release notes document [1]. Please feel free to edit/add to it! Let’s keep a rhythm and continue with the nice job everyone is doing! Cheers! [1] http://www.yourpart.eu/p/RIOT-RN2016.07 -- Francisco Javier Acosta Padilla Research Engineer at INRIA Saclay INFINE Team___ devel mailing list devel@riot-os.org https://lists.riot-os.org/mailman/listinfo/devel
[riot-devel] Feature Freeze
Dear RIOTers, the new 2016.04 release is closing in fast as ever (April 15th). Last night we reached we moved to feature freeze. We will create a release candidate branch shortly (2016.04-RC1), that should be used as a base for running tests, like we did for the last releases. So while in feature freeze: - we should put a lot of effort into testing to make the release as solid as possible - this includes running the tests specified in the release specs [1] - new features should not be merged until the release is out - bug fixes should of course be merged... For everyone opening PRs with new features during this time, please be patient, as code review will most likely be postponed during the time of feature freeze... As of now, we still have 47 issues [2] to solve until release - so every help in testing, fixing, and testing again is highly appreciated! Also feel free to put anything you think might be of interest into the release notes [3]. Keep up the good work and let's make this release great! :-) Cheers, Hauke [1] https://github.com/RIOT-OS/Release-Specs [2] https://github.com/RIOT-OS/RIOT/issues?q=is%3Aopen+is%3Aissue+milestone%3A%22Release+2016.04%22 [3] http://www.yourpart.eu/p/oCGClz07sh ___ devel mailing list devel@riot-os.org https://lists.riot-os.org/mailman/listinfo/devel
[riot-devel] Feature Freeze
Dear relieved IOTlers,
good things come to those who wait: we're finally approaching a date for the
next RIOT release. In order to get there, we're now entering testing phase and
declare a feature freeze. Until the release only PRs that are tagged for this
release (2015.09) will get merged and no more new features will get in until
then. We're hoping to have the release ready on September 18.
Any help with reviewing and testing the open PRs [1] is, of course, highly
appreciated.
Cheers,
Oleg
[1]
https://github.com/RIOT-OS/RIOT/pulls?q=is%3Aopen+milestone%3A%22Release+2015.09%22+is%3Apr
--
panic("Aarggh: attempting to free lock with active wait queue - shoot Andy");
linux-2.0.38/fs/locks.c
signature.asc
Description: PGP signature
___
devel mailing list
devel@riot-os.org
https://lists.riot-os.org/mailman/listinfo/devel
