'expected' field is not very interesting after a release is made

[Robert Collins]

e.g. on https://edge.launchpad.net/libcpuinfo/trunk/0.0.1 the expected
field is both empty and not interesting. It would look nicer to me to
hide it.

 affects launchpad

--

[Curtis Hovey (sinzui)]

Hiding it will introduce consistence that the user must guess what is happening. I think we should be setting the expected date to the release date when the milestone is created by the add release form.

[Robert Collins (lifeless)]

On Mon, 2009-06-15 at 19:35 +0000, Curtis Hovey wrote:
> Hiding it will introduce consistence that the user must guess what is
> happening. I think we should be setting the expected date to the release
> date when the milestone is created by the add release form.

Its true that things would be different, but what value does the data
have? How many releases are using it? If few people are using it (the
only use case I can think of is tracking slipped releases) then its
overhead and complexity all users are paying for.

Perhaps it would be nicer to only ever show one date:
Expected at: <xxxx>
{release happens}
Released at: <xxxx>

-Rob

[Curtis Hovey (sinzui)]

I like your suggestion. I will try to get this implemented in the July and August when the team is working on a lot of UI issues.

[Curtis Hovey (sinzui)]

Fixed in db-devel r8923.