launchpad-users team mailing list archive
Mailing list archive
Re: In need of Guideline for a small project developpement with Launchpad
I'll check your link and learn ;)
Ok for the dev branch, is useless.
What I'd suggest instead is that when you make a release, at that
point you should make a new branch for that release series and
associate that with the series in Launchpad.
Ok, so that there is a bug on a release branch I can patch this branch.
I don't think you need to set up a gatekeeper unless you especially
want a long test suite to be rigorously enforced and doing it by hand
is not enough.
I'll give feedback.
On Fri, Feb 27, 2009 at 03:03, Martin Pool <mbp@xxxxxxxxxxxxx> wrote:
> Hi Thomas,
> There's some documentation of similar scenarios here that you might find
> and I cc'd some of the people working on them in case there's more
> they'd like to add from your post.
> 2009/2/27 Thomas Manson <dev.mansonthomas@xxxxxxxxx>:
> > Hi,
> > I'm fairly new to Launchpad and Bazaar (on which I have some basic
> > understanding) and I've setup a project on the Launchpad plateform.
> > I'm using Bazaar/launchpad on a small web project which is split up in 3
> > eclipse projects, we're now 2 developer on the project (before I was
> > which make things pretty simple).
> > Bazaar gives a lot of liberty on how to manage your project, but right
> > I'm quite lost...
> > Do I need a gatekeeper ? What branch layout should I start from ?
> > Is the following scheme would be good ?
> > * The project trunked own by the team for release.
> > * a dev branch own by the team
> > * each time a developer works on a functionnality, should he create a
> > for this and then merge it to the dev branch ?
> > * once the dev branch is stable enough we merge it with the trunk ?
> I think that sounds pretty good, except I would question whether you
> really need a separate dev branch and a trunk branch. Each branch
> should have a purpose and would there really be a different purpose
> between the dev branch and trunk?
> What I'd suggest instead is that when you make a release, at that
> point you should make a new branch for that release series and
> associate that with the series in Launchpad.
> I don't think you need to set up a gatekeeper unless you especially
> want a long test suite to be rigorously enforced and doing it by hand
> is not enough.
> > Also I'm used to handle all the VCS inside eclipse GUI (with CVS/SVN
> > plugin), but with Bazaar, I feel that I can't do that, and I really need
> > use command line utilities.
> > (which sounds not that handy compared to CVS/SVN eclipse integration, but
> > yes, they are less powerfull).
> > Is there a short list of utility I should learn ?
> > I'd really like to spend more time on project developement and less on
> > learning Bazaar ;o)))
> So I'd suggest reading the tutorial, and giving feedback on the Bazaar
> list or irc channel for any thing that is lacking from the eclipse
> integration or
> Martin <http://launchpad.net/~mbp/>