Apache Allura™

Forge software for hosting software projects

Brought to you by: alexluberg, brondsem, deshani, dill0wn, and 10 others

#5816 clone_post_process for upgrades needs to use distinct usernames

Milestone: v1.0.0

Status: closed

Owner: Dave Brondsema

Labels: migration (63) sf-1 (616)

Component: General

Reviewer: Cory Johns

Updated: 2015-08-20

Created: 2013-02-14

Creator: Dave Brondsema

Private: No

clone_post_process for upgrades sends and email to all the devs, but the clone command uses c.user.username. It needs to be a separate email to each dev, with the correct username in the clone command.

Discussion

Dave Brondsema - 2013-02-14

status: open --> in-progress

assigned_to: Dave Brondsema

size: --> 1
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Dave Brondsema - 2013-02-15

forge-classic:db/5816

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Dave Brondsema - 2013-02-15

status: in-progress --> code-review
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Cory Johns - 2013-02-18

qa: Cory Johns
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Cory Johns - 2013-02-18

status: code-review --> closed
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Apache Allura™

Forge software for hosting software projects

Milestone

Searches

Help

#5816 clone_post_process for upgrades needs to use distinct usernames

Discussion