It should be possible to determine default branch visibility of a project

Bug #334923 reported by Cody A.W. Somerville
6
Affects Status Importance Assigned to Milestone
Launchpad itself
Fix Released
Low
Tim Penhey

Bug Description

It should be possible to determine default branch visibility of a branch before you push it. Pushing a branch that you think will be private by default but turns out to be public can be hairy.

Revision history for this message
Christian Reis (kiko) wrote :

What if we changed the Bazaar client to say "Public branch being created and pushed at ..." if it was being created public, and "Private branch" otherwise, since visibility is a default anyway?

Revision history for this message
Martin Pool (mbp) wrote : Re: [Bug 334923] Re: It should be possible to determine default branch visibility of a project

2009/2/27 Christian Reis <email address hidden>:
> What if we changed the Bazaar client to say "Public branch being created
> and pushed at ..." if it was being created public, and "Private branch"
> otherwise, since visibility is a default anyway?

What do you mean by 'is a default'?

--
Martin <http://launchpad.net/~mbp/>

Paul Hummer (rockstar)
Changed in launchpad-bazaar:
importance: Undecided → Low
status: New → Triaged
Revision history for this message
Jonathan Lange (jml) wrote :

Kiko means that you don't initially set it on a per-branch basis, it's derived from a setting on the project. You can then change it later.

Revision history for this message
Martin Pool (mbp) wrote :

OK.

So Bazaar won't know it.

The best thing is probably if Launchpad can give this message back,
maybe just over ssh stderr or maybe through something more structured,
when we create the branch.

--
Martin <http://launchpad.net/~mbp/>

Revision history for this message
Brad Crittenden (bac) wrote :

The bzr integration piece may be nice but it is more important that the UI show that information for a project. Currently we're advising people to push an empty branch and then go look at it, which is a pretty bad work-around.

Revision history for this message
Tim Penhey (thumper) wrote : Re: [Bug 334923] Re: It should be possible to determine default branch visibility of a project

On Fri, 13 Mar 2009 07:54:38 Brad Crittenden wrote:
> The bzr integration piece may be nice but it is more important that the
> UI show that information for a project. Currently we're advising people
> to push an empty branch and then go look at it, which is a pretty bad
> work-around.

I was just thinking about this yesterday when fixing a big problem with the
security. I'll look at this.

Tim Penhey (thumper)
Changed in launchpad-code:
assignee: nobody → Tim Penhey (thumper)
milestone: none → 2.2.5
status: Triaged → In Progress
Tim Penhey (thumper)
Changed in launchpad-code:
status: In Progress → Fix Committed
Paul Hummer (rockstar)
Changed in launchpad-code:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.