[opensource-dev] Submission process when a team is working an issue.

[Oz Linden (Scott Lawrence)]

  On 2010-08-30 12:42, Nicky Perian wrote:
> Oz,
>
> Please clarify the vwr-xxxxx process.
>
> As a example. I built and tested vwr-20879 the issue Robin wrote up 
> concerning Express builds.
>
> She had a six or so additional vwr-xxxxx issues that contributed to a 
> solution. I added a change set that improved one aspect of the six or 
> so. I pushed these to my repo vwr-20879 on bitbucket.
>
> My question; Is this now a single issue and if so, how would it be 
> presented as such?
>
> Please look at my https://bitbucket.org/NickyP/vwr-20879. Is the 
> format of changes correct for a viewer-development pull? I saw a 
> changeset where you did a merge up? Is that a way to combine 
> changesets into one issue from many sub issues? And if so, how?

As long as everyone involved thinks that the combined changes are good, 
multiple changesets are fine.   When the team is satisfied with the 
collection of changes, update the issue with a pointer to the particular 
repository and changeset that is the tip of that set of changes.

Other than the fact that your repo has not been brought up to date with 
viewer-development (a lot went in over the weekend), it would do 
nicely.  (I have not yet reviewed the individual diffs - make sure that 
contributions.txt is appropriately updated).


-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.secondlife.com/pipermail/opensource-dev/attachments/20100830/3e74c574/attachment.htm