On Wed, 2010-07-28 at 22:29 +0000, Aaron Bentley wrote:
> Rodney, your branch isn't necessarily private because it's for a
> commercial project. It may be private because it is contains (or may
> contain) fixes for security vulnerabilities. For example,
> https://code.edge.launchpad.net/~launchpad-pqm/launchpad/production-
> devel is private for this reason.
>
> You don't want to make this code available until you have publicly-
> available packages that provide it. One way of getting publicly-
> available packages is by building the recipe into a public PPA.
> (Another is by building to a private PPA and then copying to a public
> one.)
OK. But it looks like Julian's reply from a few hours ago, seems to
suggest this irrelevant to how the security fix builds are done. And I
think even in that case, you probably don't want to build to a public
branch, if you're trying to keep it private.
On Wed, 2010-07-28 at 22:29 +0000, Aaron Bentley wrote: /code.edge. launchpad. net/~launchpad- pqm/launchpad/ production-
> Rodney, your branch isn't necessarily private because it's for a
> commercial project. It may be private because it is contains (or may
> contain) fixes for security vulnerabilities. For example,
> https:/
> devel is private for this reason.
>
> You don't want to make this code available until you have publicly-
> available packages that provide it. One way of getting publicly-
> available packages is by building the recipe into a public PPA.
> (Another is by building to a private PPA and then copying to a public
> one.)
OK. But it looks like Julian's reply from a few hours ago, seems to
suggest this irrelevant to how the security fix builds are done. And I
think even in that case, you probably don't want to build to a public
branch, if you're trying to keep it private.