milestones leaked proprietatary information

I marked this as private because i didn't know if I should be talking about private branches in public.

I'm not sure I understand the value of having a private milestone. Are you asking for a private milestone for a public project that a private bug can be targeted too? Thus the series page will list only the public milestones? Since a release is tied to a milestone, is the release also private if the milestone is private?

well, launchpad doesn't really have private projects yet.
we have projects where all bugs are private-by-default.
when i'm working with one of those projects, when I create a milestone, the name and date of the milestone is public, which reveals more about the project than I want to (basically embargoed information about the timeline for the project).

No. Private milestones for private projects. So that we can specify
milestones and target dates for them, without the risk of giving out too
much information. I suspect this would be very useful for the OEM team
as well, as there may be milestones for features/support that we and our
partners do not wish to disclose to the public during development.
However, currently these milestone names and their dates are publicly
visible, even for private projects.

On Thu, 2009-04-30 at 17:28 +0000, Curtis Hovey wrote:
> I'm not sure I understand the value of having a private milestone. Are
> you asking for a private milestone for a public project that a private
> bug can be targeted too? Thus the series page will list only the public
> milestones? Since a release is tied to a milestone, is the release also
> private if the milestone is private?
>
> ** Changed in: launchpad-registry
> Importance: Undecided => Low
>
> ** Changed in: launchpad-registry
> Status: New => Triaged
>
> ** Tags added: feature
>

By making a milestone private, the release would also be private.

On Mon, 2009-06-15 at 19:23 +0000, Curtis Hovey wrote:
> By making a milestone private, the release would also be private.

I think that's probably acceptable in places where private milestones
make sense (private projects using private branches). I think the
majority of cases probably want to have private releases, or just won't
have downloadable releases for private milestones, anyway.