Hello, all. I went through the list of bugs and created a shortlist of bugs
that need to be looked at for 2.02. I have marked them with plan_release_id
set to 2.02.
Statistics: [1]
Search (with loads of false positives unfortunately): [2]
Not every bug there is a release blocker, for some of them it just would be
nice to know status before releasing. Some of them are probably already
fixed.

Additionally I created a category "Hardware specific" [3]. Bugs there are
not release blockers but fixing them could benefit the release.

I would also appreciate if distros would tell which patches they would
carry if 2.02 was released as it is now. If some patches are in more than 1
distro we probably need to look into including them.

Please bring up any tasks that needs to be done in your opinion for 2.02
and not mentioned as separate thread with [2.02] in subject line.

I would like to come up with a complete list of 2.02 blockers in one week
time, so that we can have a reasonable timeline

[1]
https://savannah.gnu.org/bugs/reporting.php?group_id=68&field=plan_release_id
[2]
https://savannah.gnu.org/search/?type_of_search=bugs&words=plan_release_id+2.02&only_group_id=68&offset=0&max_rows=25#results
[3]
https://savannah.gnu.org/bugs/index.php?go_report=Apply&group=grub&func=browse&set=custom&msort=1&report_id=101&advsrch=1&status_id%5B%5D=1&resolution_id%5B%5D=0&submitted_by%5B%5D=0&assigned_to%5B%5D=0&category_id%5B%5D=0&bug_group_id%5B%5D=105&severity%5B%5D=0&priority%5B%5D=0&summary=&details=&sumORdet=0&history_search=0&history_field=0&history_event=modified&history_date_dayfd=2&history_date_monthfd=3&history_date_yearfd=2016&chunksz=50&spamscore=5&boxoptionwanted=1#options
_______________________________________________
Grub-devel mailing list
Grub-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/grub-devel

Reply via email to