Hi,
some of you may be aware of the wiki I set up to manage/document the
todo lists and parts of the release management for PHP releases. In
response to this Wez created a set of patches to enable developers to
set milestones (aka PHP versions) for bug reports. While I do not think
this replaces the need for the wiki (which is maintained independent of
php.net ressources anyways), which is way more flexible, I think its a
very good addition.
For example we currently mark things as "fixed in CVS" even if things
will never be fixed in the branch for which the user filed the bug
report (like with the streams API). Therefore I think its a very
important tool to let users know when things will get fixed. I could see
the same kinds of things happen with unicode issues being reported in
the 5.x branch but only getting addressed in php 6.x.
Anyways I think it would be a good idea to add this feature again along
with the ability to filter by milestones on the "advanced search" page.
I think this would make the life of our RMs alot easier as well.
regards,
Lukas
Unnecessary, you can tell the user within the closing comment
in which branches you fixed the bug. Don't forget that it can
CHANGE later, someone reverts the fix or the fix wasn't needed
or.. you get the picture.
--Jani
Hi,
some of you may be aware of the wiki I set up to manage/document the todo
lists and parts of the release management for PHP releases. In response to
this Wez created a set of patches to enable developers to set milestones (aka
PHP versions) for bug reports. While I do not think this replaces the need for
the wiki (which is maintained independent of php.net ressources anyways),
which is way more flexible, I think its a very good addition.For example we currently mark things as "fixed in CVS" even if things will
never be fixed in the branch for which the user filed the bug report (like
with the streams API). Therefore I think its a very important tool to let
users know when things will get fixed. I could see the same kinds of things
happen with unicode issues being reported in the 5.x branch but only getting
addressed in php 6.x.Anyways I think it would be a good idea to add this feature again along with
the ability to filter by milestones on the "advanced search" page. I think
this would make the life of our RMs alot easier as well.regards,
Lukas
Jani Taskinen wrote:
Unnecessary, you can tell the user within the closing comment in which branches you fixed the bug. Don't forget that it can CHANGE later, someone reverts the fix or the fix wasn't needed or.. you get the picture.
Does it hurt though?
It makes it alot easier to update things if necessary. Say for example
we decide not to release a specific version we can easily find all the
relevant bug reports and update the milestone version. Also it will help
reminds developers to even put this information in, compared to the
current state of affairs where the tendency to not note anything.
Finally this information will be a in a fixed location in a fixed
format, compared to in the comments where additional comments can
clutter this information away.
Finally the RM can target any relevant open bugs easily this way and
quickly get to them.
I see only advantages and no real disadvantage.
regards,
Lukas
Jani Taskinen wrote:
Unnecessary, you can tell the user within the closing comment in which branches you fixed the bug. Don't forget that it can CHANGE later, someone reverts the fix or the fix wasn't needed or.. you get the picture.Does it hurt though?
Yes, if everyone doesn't use it. And it's useless as long
as you can select only one "milestone".
It makes it alot easier to update things if necessary. Say for example we
decide not to release a specific version we can easily find all the relevant
bug reports and update the milestone version. Also it will help reminds
developers to even put this information in, compared to the current state of
affairs where the tendency to not note anything. Finally this information will
be a in a fixed location in a fixed format, compared to in the comments where
additional comments can clutter this information away.
We already have the fixed bugs in NEWS, that's enough.
Finally the RM can target any relevant open bugs easily this way and quickly
get to them.I see only advantages and no real disadvantage.
I see only more work.
--Jani
Jani Taskinen wrote:
Jani Taskinen wrote:
Unnecessary, you can tell the user within the closing comment in which branches you fixed the bug. Don't forget that it can CHANGE later, someone reverts the fix or the fix wasn't needed or.. you get the picture.Does it hurt though?
Yes, if everyone doesn't use it. And it's useless as long as you can select only one "milestone".It makes it alot easier to update things if necessary. Say for example
we decide not to release a specific version we can easily find all the
relevant bug reports and update the milestone version. Also it will
help reminds developers to even put this information in, compared to
the current state of affairs where the tendency to not note anything.
Finally this information will be a in a fixed location in a fixed
format, compared to in the comments where additional comments can
clutter this information away.We already have the fixed bugs in NEWS, that's enough.Finally the RM can target any relevant open bugs easily this way and
quickly get to them.I see only advantages and no real disadvantage.
I see only more work. --Jani
Which nobody is asking You to do. If someone else is willing to put in
the time and effort to at least try to improve things, at least let
them waste their own time as they see fit (if that turns out to be the
case). Quit being such a wet blanket and lets see if this does help in
practice.
- Davey