Can't easily create a release file from a branch revision or tag

Bug #609796 reported by Monty Taylor on 2010-07-25
32
This bug affects 3 people
Affects Status Importance Assigned to Milestone
Launchpad itself
Low
Unassigned

Bug Description

There is currently a disconnect between managing code in bzr on launchpad and cutting a release, even though launchpad supports both bzr and tarball releases.

It seems to me that all of the elements of the workflow should be possible within launchpad. I would suggest that, in addition to the "create a release" workflow right now (or perhaps as part of it) I should be able to nominate a branch for release, and that nomination should go through something similar to the merge request process. If approved, launchpad should be able to tag the release in bzr.

Or skip the merge request part and just let me create and tag a release - I dunno.

Curtis Hovey (sinzui) wrote :

There is a related bug that requests that is be possible to indicate the version of the branch that constitutes a release. Launchpad model series as a single branch, and the releases are version of the branch.

affects: launchpad → launchpad-code
tags: added: feature
Tim Penhey (thumper) wrote :

Bug 540752 is related, but this bug covers more of a use case.

I don't believe there is a related branch for a milestone/release right now, and Launchpad doesn't show any tags.

Are you thinking that Launchpad should handle the tar ball upload? If this is the case, then it is getting very close to arbitrary code execution to make the tar ball, unless we just tar up an export of the branch, which isn't often what is wanted.

Changed in launchpad-code:
status: New → Triaged
importance: Undecided → Low

On 07/25/2010 06:04 PM, Tim Penhey wrote:
> Bug 540752 is related, but this bug covers more of a use case.
>
> I don't believe there is a related branch for a milestone/release right
> now, and Launchpad doesn't show any tags.
>
> Are you thinking that Launchpad should handle the tar ball upload? If
> this is the case, then it is getting very close to arbitrary code
> execution to make the tar ball, unless we just tar up an export of the
> branch, which isn't often what is wanted.

I agree with that. I do not personally need launchpad to make the
tarball... it just seems like there are steps (specifically related to
adding branch tags) that could be automated/workflowed.

However- fwiw of course, I did receive a gripe from a github user that
"in github I can tag a release and it'll make a tarball for me" ... of
course, what they meant was a tarball of the git tree, rather than
running any commands.

I have no idea why anyone would want this, but whatever.

William Grant (wgrant) on 2013-08-13
summary: - need a system for release tagging/releasing
+ Can't easily create a release file from a branch revision or tag
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Duplicates of this bug

Other bug subscribers