Just added a bazaar branch for drqueue

I presume you are referring to https://code.launchpad.net/~jorge-drqueue/drqueue/trunk.

You created this bzr mirror branch using https://code.launchpad.net/drqueue/+addbranch. As explained on this page, "The only branch format supported is that of the Bazaar revision control system".

The right place to request a code import for this product from Subversion is https://launchpad.net/drqueue/0.62/+source.

We are aware the user interface is confusing, bug 115965.

In a few days, after the 1.1.8 Launchpad release, you should be able to delete the branch you created by mistake.

Hello David,

first of all thanks for your reply.

My concern is that the place you point out to import the code is
actually representing a subversion branch of DrQueue.

What I really wanted was to put the trunk on bazaar so any other
branch would have real sense based on that.

Maybe it's because I have misunderstood some bazaar concept, but it
seems to me kinda awkward to create a _trunk_ branch from a version
branch, does that work in fact ? But I mean looking into the future
when new branches would be created based on the trunk, or any other
branch that would end up being a child of the trunk. I wouldn't want
to follow the line pass through the trunk and end up in version 0.62.

As I said, I probably got something wrong.

All the best,

Jorge

Jorge Daza García-Blanes
DrQueue Project - http://drqueue.org/
Lead Developer, master and slave...
Phone Numbers:
+1 (310) 601 8521, United States
+61 (03) 9018 6521, Australia
+44 (020) 8123 3078, United Kingdom

On Aug 20, 2007, at 18:32 GMT+02:00, David Allouche wrote:

> Your question #11765 on Launchpad Bazaar Integration changed:
> https://answers.launchpad.net/launchpad-bazaar/+question/11765
>
> Status: Open => Answered
>
> David Allouche proposed the following answer:
> I presume you are referring to https://code.launchpad.net/~jorge-
> drqueue/drqueue/trunk.
>
> You created this bzr mirror branch using
> https://code.launchpad.net/drqueue/+addbranch. As explained on this
> page, "The only branch format supported is that of the Bazaar revision
> control system".
>
> The right place to request a code import for this product from
> Subversion is https://launchpad.net/drqueue/0.62/+source.
>
> We are aware the user interface is confusing, bug 115965.
>
> In a few days, after the 1.1.8 Launchpad release, you should be
> able to
> delete the branch you created by mistake.
>
> --
> If this answers your question, please go to the following page to
> let us
> know that it is solved:
> https://answers.launchpad.net/launchpad-bazaar/+question/11765/
> +confirm?answer_id=0
>
> If you still need help, you can reply to this email or go to the
> following page to enter your feedback:
> https://answers.launchpad.net/launchpad-bazaar/+question/11765
>
> You received this question notification because you are a direct
> subscriber of the question.

Hi Jorge,

All code stored in bzr is considered a branch (even the trunk ones). Since bzr works in a decentralised manner, the `trunk` branch is considered mainline. Anyone wanting to develop a feature will normally branch off trunk, work on their branch and then merge the code back into trunk.

I see that on the page https://launchpad.net/drqueue/stable you have registered the SVN details (https://ssl.drqueue.org/svn/trunk) which is the correct way (at the moment) of requesting a code import. When this code import is running, it will create a branch that is owned by the team `VCS Imports`.

Is the intention to move DrQueue to bzr completely? Or just to provide another mechanism for getting the code?

Tim

Clicked on the wrong button :(

Hello Tim,

my intention at the moment is to keep the svn repo, but provide
bazaar as the great tool I see it is to encourage participation
without the hassle of adding new local users and such.

So I will use both tools to keep the code on synch for a start. Later
on and depending on the results I will decide if I stay that way for
a longer time or if I migrate to bzr completely.

In fact I actually use svk instead of svn even though the repo is
svn, but I need those decentralized tools even for myself.

One question I've got is, would bzr allow a branch to be "hidden" or
not-public during certain time until it is decided it can be made
public ? That feature is one I use on svn through authz and I would
like to keep that. Sometimes the work should not be public because a
client requested a customization and I still need the repo, or
sometimes we just experiment stuff that we'd rather keep away from
the public to lose the little respect we might have without
deserving. :)

Another question would be, that I have a bug tracker based on trac on
the site and I'd like to use it but could not find the way to
associate it with the project. Could that be done ?

Thanks in advance,

Jorge

Jorge Daza García-Blanes
DrQueue Project - http://drqueue.org/
Lead Developer, master and slave...
Phone Numbers:
+1 (310) 601 8521, United States
+61 (03) 9018 6521, Australia
+44 (020) 8123 3078, United Kingdom

On Aug 21, 2007, at 0:55 GMT+02:00, Tim Penhey wrote:

> Your question #11765 on Launchpad Bazaar Integration changed:
> https://answers.launchpad.net/launchpad-bazaar/+question/11765
>
> Status: Open => Answered
>
> Tim Penhey proposed the following answer:
> Hi Jorge,
>
> All code stored in bzr is considered a branch (even the trunk ones).
> Since bzr works in a decentralised manner, the `trunk` branch is
> considered mainline. Anyone wanting to develop a feature will
> normally
> branch off trunk, work on their branch and then merge the code back
> into
> trunk.
>
> I see that on the page https://launchpad.net/drqueue/stable you have
> registered the SVN details (https://ssl.drqueue.org/svn/trunk)
> which is
> the correct way (at the moment) of requesting a code import. When
> this
> code import is running, it will create a branch that is owned by the
> team `VCS Imports`.
>
> Is the intention to move DrQueue to bzr completely? Or just to
> provide
> another mechanism for getting the code?
>
> Tim
>
> --
> If this answers your question, please go to the following page to
> let us
> know that it is solved:
> https://answers.launchpad.net/launchpad-bazaar/+question/11765/
> +confirm?answer_id=2
>
> If you still need help, you can reply to this email or go to the
> following page to enter your feedback:
> https://answers.launchpad.net/launchpad-bazaar/+question/11765
>
> You received this question notification because you are a direct
> subscriber of the question.

On Tuesday 21 August 2007 11:27:07 Jorge Daza García-Blanes wrote:
> Question #11765 on Launchpad Bazaar Integration changed:
> https://answers.launchpad.net/launchpad-bazaar/+question/11765
>
> Status: Needs information => Open
>
> Jorge Daza García-Blanes gave more information on the question:
> Hello Tim,
>
> my intention at the moment is to keep the svn repo, but provide
> bazaar as the great tool I see it is to encourage participation
> without the hassle of adding new local users and such.

Then using an import is a great way to support this.

> So I will use both tools to keep the code on synch for a start. Later
> on and depending on the results I will decide if I stay that way for
> a longer time or if I migrate to bzr completely.
>
> In fact I actually use svk instead of svn even though the repo is
> svn, but I need those decentralized tools even for myself.
>
> One question I've got is, would bzr allow a branch to be "hidden" or
> not-public during certain time until it is decided it can be made
> public ? That feature is one I use on svn through authz and I would
> like to keep that. Sometimes the work should not be public because a
> client requested a customization and I still need the repo, or
> sometimes we just experiment stuff that we'd rather keep away from
> the public to lose the little respect we might have without
> deserving. :)

All branches pushed to launchpad are considered public (for now).

> Another question would be, that I have a bug tracker based on trac on
> the site and I'd like to use it but could not find the way to
> associate it with the project. Could that be done ?

Launchpad is about to get remote bug tracking with trac support.
This will allow a bug registered in launchpad to be associated with
a bug in trac and have its status updated based on the trac status.

Tim

I followed your instructions and registered two branches to be imported, but on the status says "Do not import". Is there anything wrong on the information ?

Thanks again,

Jorge

Jorge: you seem to be asking about something new. Please file a new question.

In this new question, please provide the URLs of the launchpad pages of the two branches you are referring to.