nunit-dev team mailing list archive

["Charlie Poole" <charlie@xxxxxxxxx>]

Hi Paul,

Thanks for the comments... 

> http://nunit.org/wiki/doku.php?id=dev:faq:as_a_casual_contributor_how_
> > do_i_f
> > ix_a_single_nunit_bug
> > 
> > Does it make sense? Does it seem right?
> 
> I have a few suggestions.
> 
> I wouldn't suggest using the --stacked branch option for 
> local stuff.  We use stacked in Launchpad to help the speed 
> of push, but creating stacked branches locally doesn't really 
> make a huge difference, and is easily prone to breakage when 
> you decide to move folders around.

I got this idea from http://bazaar-vcs.org/Scenarios/OneOffContribution/

I understand that I wouldn't want to use it when the parent branch
is local, but in this case it's the upstream trunk. Does that make
difference in your view? Branching from lp:nunit-2.5 takes a long
time and I thought this would help, but I haven't actually tested it.

> 
> Also, are you planning on using merge proposals in Launchpad 
> for reviews?  The problem with doing `bzr send` to a mailing 
> list is that you have to be a member of the list.  If you 
> send the email to merge@xxxxxxxxxxxxx, Launchpad will create 
> the branch and add your specific revisions (if you haven't 
> pushed it), and then create a merge proposal, using the 
> content of your email as the merge proposal itself.  It does 
> require your GPG key though.  You can also make sure that the 
> merge proposal creation emails go to the dev list so that all 
> the devs see it by subscribing the nunit-dev team on 
> launchpad to the source branch.

OK, I didn't understand about merge@xxxxxxxxxxxxx and I didn't
want casual contributors - most likely new to Launchpad - to
have to push a branch. This sounds good except for the GPG
key, which many Windows folks won't have, so I'll have to 
add that to the process. Can you point me to some docs on using 
merge@xxxxxxxxxxxxx?

I'll go ahead and work on the repeated contributor scenario
as well, so we have the two to compare. I'm basing that on
http://bazaar-vcs.org/Scenarios/RepeatedContributions  I
have a few questions but I'll wait till it's written to
ask them.

Charlie

PS: Just had a second thought... I was working on the simplest
approach first, and I planned to put them in the FAQ in that
order. But maybe the order should be:

* Normal setup for developers
* Advanced setup 
* Casual setup

Casual could be under a question like "That's all too complicated
for me, is there an easy way to just do a single fix?"

How does that sound?

> Just food for thought.
> 
> Cheers,
> Paul
> 
> 
> _______________________________________________
> Mailing list: https://launchpad.net/~nunit-dev
> Post to     : nunit-dev@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~nunit-dev
> More help   : https://help.launchpad.net/ListHelp
>