[Systers-dev] A branch of our own?

[स्वक्ष]

On Fri, Jun 4, 2010 at 23:23, Anne Gunn <ompeag at wyoming.com> wrote:
>   This may just be a Bazaar/Systers newbie question, so please feel free

/me is one too, newbie i.e.

>    She is also producing fixes in the form of patches and contributing
>   them to launchpad defect reports when appropriate.
>   But, for Simone and I to stay synchronized with what Erica is doing in
>   her local branch, should we be doing some sort of peer-to-peer
>   commit/pull?  Or should we make a branch of our own up in launchpad?
>   The central branch up on launchpad seems the most natural to me since
>   I'm an old centralized VCS hand.  Also easier for the gatekeeper to use
>   when it comes time to merge Erica's changes back up into the
>   development/production branch.

http://doc.bazaar.canonical.com/latest/en/user-guide/index.html, lists
a central and distributed style. I'd assume the central style is what
you mean by TeamWishlist? and a distributed style is when Robin (and
others with commit access to the main systers repo) wish to pull your
changes upstream. Did I understand this correctly?

Bzr allows you to export a specific revision of a branch that you are
looking for. Keep an eye out for the different URL's on LP for each
task you do there. I'll admit its a little bit confusing at first
--i've not completely groked it myself  yet.


>   Or am I missing the boat entirely and Erica should just be committing
>   straight back into the Development branch when she has a change we are
>   confident about?

IIUC, if you dont have commit rights to the main repo (assuming you
have an LP account), you'd keep the changes you made locally uploaded
to your PPA[1] and a link of that branch is mailed to the upstream
devel.

[1] http://doc.bazaar.canonical.com/latest/en/tutorials/using_bazaar_with_launchpad.html?highlight=personal%20package%20archives

Hope that helps.

-- 
thanks and regards,
vid || http://svaksha.com