after the prerelease
This discussion is connected to the gimp-developer-list.gnome.org mailing list which is provided by the GIMP developers and not related to gimpusers.com.
This is a read-only list on gimpusers.com so this discussion thread is read-only, too.
| after the prerelease | Sven Neumann | 07 Jan 22:27 |
| after the prerelease | Daniel Rogers | 07 Jan 22:56 |
after the prerelease
Hi,
OK, the prerelease is out and the first bugs were found and fixed. After the prerelease is before the prerelease. We still have about 70 bugs on the 2.0 milestone. Our goal should now be to target this list. Not all these bugs need to be fixed before 2.0. A few, especially feature requests, can be postponed to 2.2. At some point we can also move some remaining minor problems on the 2.0.1 milestone. But all these bug reports need to be revisited. So if you have some spare time, please do a query on the 2.0 milestone and check if you can comment on some of these.
Since we want to ship 2.0 with as many complete translations as possible, we should, from now on, try to avoid any string changes unless the change is essential for a bug-fix. A severe user interface problem definitely counts as a bug here, missing mnemonics probably don't. I've sent a mail to gnome-i18n informing the translators that it is good time to look after the gimp translations, so please stick to this rule and avoid string changes whenever possible.
Sven
after the prerelease
Sven Neumann wrote:
Hi,
OK, the prerelease is out and the first bugs were found and fixed. After the prerelease is before the prerelease. We still have about 70 bugs on the 2.0 milestone. Our goal should now be to target this list. Not all these bugs need to be fixed before 2.0. A few, especially feature requests, can be postponed to 2.2. At some point we can also move some remaining minor problems on the 2.0.1 milestone. But all these bug reports need to be revisited. So if you have some spare time, please do a query on the 2.0 milestone and check if you can comment on some of these.
Some links that are relevent, just to make things a little easier for everyone.
The bugzilla query page for the prerelease.
There is a bug in the query page, it seems, and the milestone is not
properly read from the CGI query string. You will have to input the
milestone (2.0) by hand.
http://bugzilla.gnome.org/query.cgi?product=GIMP&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=NEEDINFO&bug_status=REOPENED&bug_severity=blocker&bug_severity=critical&bug_severity=major&bug_severity=normal&bug_severity=minor&bug_severity=trivial&bug_severity=enhancement&target_milestone=2.0&email1=&emailtype1=substring&emailassigned_to1=1&email2=&emailtype2=substring&emailreporter2=1&changedin=&chfieldfrom=&chfieldto=Now&chfieldvalue=&short_desc=&short_desc_type=substring&long_desc=&long_desc_type=substring&bug_file_loc=&bug_file_loc_type=substring&status_whiteboard=&status_whiteboard_type=substring&keywords=&keywords_type=anywords&op_sys_details=&op_sys_details_type=substring&version_details=&version_details_type=substring&namedcmd=gimp+pre-2.0+blockers&newqueryname=gimp+2.0+blockers&order=Reuse+same+sort+as+last+time&form_name=query
These should both be one one line, so edit accourdingly
--
Dan
