why is imported branch not owned by ~vcs-imports?

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Tim wrote:
> New question #101332 on Launchpad Bazaar Integration:
> https://answers.launchpad.net/launchpad-code/+question/101332
>
> I initiated a vcs import at:
>
> https://code.launchpad.net/~timmie/grass6/grass6_devel
>
> But unlike this one here:
> https://code.launchpad.net/~vcs-imports/grass6/trunk
>
> the branch is still owned by myself instead of the ~vcs-imports.
>
> How can I change this?
>
> Thanks.
>

By default, the import is done as the user who requested the import.
What is the difference between "grass6_devel" and "trunk"?

You might be able to reassign the branch owner under
  https://code.edge.launchpad.net/~timmie/grass6/grass6_devel/+edit

However, I think you can only assign that to a group you are a part of.
Which means you have to make a request (such as this one) to get it
reassigned. I went ahead and updated it to be ~vcs-imports.

John
=:->
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Cygwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAkt7Af0ACgkQJdeBCYSNAAOVzQCfc2vt76VtqTndAgUwYvPldli8
OcoAnigUA2oqidCgPu1bg9z6Aj/u0ofH
=0jNj
-----END PGP SIGNATURE-----

> What is the difference between "grass6_devel" and "trunk"?
grass6_devel imports the current release series: https://svn.osgeo.org/grass/grass/branches/develbranch_6
trunk is the development version with new features: https://svn.osgeo.org/grass/grass/trunk
trunk wil later turn into GRASS 7

> You might be able to reassign the branch owner under
> https://code.edge.launchpad.net/~timmie/grass6/grass6_devel/+edit
> However, I think you can only assign that to a group you are a part of.
I am not part of the group. How can I enter the group?

A big question:
Can we rename

https://code.launchpad.net/grass6

into

https://code.launchpad.net/grass

in order to reflect the new developments towards higher versions?

Thanks for attending this question. You are always of help!

Tim, a change was made recently to have the person who asks for the import to be the owner of the imported branch, rather than a special team withing Launchpad itself. This is why your newly created branch was owned by you not vcs-imports.

The vcs-imports team is special, and not open.

Renaming the project from grass6 to grass is a bigger issue as it breaks a lot of urls, although we can add aliases so I think it is possible to move the project from grass6 -> grass and have an alias for grass6.

You may want to consider abandoning the current trunk import of grass6 and requesting a new one as the current trunk import uses our old importer (CSCVS) and the new one uses bzr-svn. The two branches will not have any common ancestry. If you re-import trunk then assuming the branches have common ancestry in subversion, they will also have common ancestry in bzr.

Please let me know if you want to do this.

Tim

Thanks for following up.

I will come back later as the upstream developers said that they prefer not divert the development to another code hosting portal than the one from OSGEO:
http://thread.gmane.org/gmane.comp.gis.grass.devel/38332

On Wed, 17 Feb 2010 22:43:40 Tim wrote:
> Question #101332 on Launchpad Bazaar Integration changed:
> https://answers.edge.launchpad.net/launchpad-code/+question/101332
>
> Tim posted a new comment:
> Thanks for following up.
>
> I will come back later as the upstream developers said that they prefer not
> divert the development to another code hosting portal than the one from
> OSGEO: http://thread.gmane.org/gmane.comp.gis.grass.devel/38332

I just read the email thread, and to be honest, to me it seems like they don't
care what you use as your client, but they are wanting to keep Subversion as
their back end, which is fine.

I suggest we change the trunk import to use bzr-svn, and you can they use
Bazaar with bzr-svn to push your Bazaar branches to Subversion if you have
commit rights on the server.

>I suggest we change the trunk import to use bzr-svn, and you can they use
Bazaar with bzr-svn to push your Bazaar branches to Subversion if you have
commit rights on the server.
OK, here is a new import:
https://code.launchpad.net/~timmie/grass6/grass_trunk

Is this now using bzr-svn?
How can I check this?

The GRASS project (https://launchpad.net/grass) should have only two imported braches:
* grass6_devel importing https://svn.osgeo.org/grass/grass/branches/develbranch_6
  => this leads to the GRASS 6 release which is the current focus.

* grass_trunk importing https://svn.osgeo.org/grass/grass/trunk
  => this is the development trunk with new features.

What do you suggest to clean up the versioning mess in the URLs?

Thanks again for following up and giving attention.

On Thu, 18 Feb 2010 13:40:24 Tim wrote:
> Question #101332 on Launchpad Bazaar Integration changed:
> https://answers.launchpad.net/launchpad-code/+question/101332
>
> Status: Answered => Open
>
> Tim is still having a problem:
> >I suggest we change the trunk import to use bzr-svn, and you can they use
>
> Bazaar with bzr-svn to push your Bazaar branches to Subversion if you have
> commit rights on the server.
> OK, here is a new import:
> https://code.launchpad.net/~timmie/grass6/grass_trunk
>
> Is this now using bzr-svn?
> How can I check this?

It has been approved. All new Subversion imports are done with bzr-svn.

> The GRASS project (https://launchpad.net/grass) should have only two
> imported braches: * grass6_devel importing
> https://svn.osgeo.org/grass/grass/branches/develbranch_6 => this leads to
> the GRASS 6 release which is the current focus.
>
> * grass_trunk importing https://svn.osgeo.org/grass/grass/trunk
> => this is the development trunk with new features.
>
> What do you suggest to clean up the versioning mess in the URLs?

To change the project name, ask a question on the launchpad project
specifically for the project name change, and an admin can help you (I'm not
one).

Then you probably want to have two series, one for 6.x development, and the
other for 7.x development. You can then link up the import branches to these
series.

You then choose which of 6.x or 7.x you want as the development focus, so the
resulting branches will be accessed like:

  lp:grass (if 6.x is dev focus)
  lp:grass/7.x

or

  lp:grass (if 7.x is dev focus)
  lp:grass/6.x