[Pkg-parrot-devel] Packages files for Parrot 3.[03].0 imported in git

[Allison Randal]

On 04/30/2011 03:39 PM, Alessandro Ghedini wrote:
> On Wed, Apr 27, 2011 at 02:18:56PM +0200, Dominique Dumont wrote:
>> Le dimanche 24 avril 2011 22:29:31, Alessandro Ghedini a écrit :
>>> git-import-dscs (note the final 's') imports all the versions of a package
>>> but it does not preserve changelog messages, it only saves e.g.
>>> "Imported Upstream version X.Y.Z" and "Imported Debian patch X.Y.Z".
>>>
>>> You can try this with:
>>>
>>>      $ git import-dscs --pristine-tar --debsnap parrot
>>
>> Thanks for the tip.
>>
>> I've used git-import-dscs --pristine-tar to import both parrot packages (3.0.0
>> and 3.3.0)
>
> Given that Allison merged only some parts of the 3.3.0 changes we'll have
> to redo the import (no need to rush, we can wait untill 3.3.0 gets uploaded)
> maybe including also all the previous parrot versions. IMHO the cleanest
> solution would be to re-start with a blank repository, so that unused
> changes does not float around in the repository.
>
> We should also arrange some sort of policy on how to interact with the
> repository (e.g. [0], [1] and [2]) in order to avoid future problems.

Aye, I figured we might restart a time or two on the git repo and 
processes. I'd like to draft our own workflow documents and put them up 
on the pkg-parrot alioth pages.

FYI, this is the current process for packaging Parrot, which we'll be 
migrating from to the new git-based process:

https://github.com/parrot/parrot/blob/master/docs/project/debian_packaging_guide.pod

My main thought at this point is that the 'master' branch in the 
pkg-parrot git repo should only be packages that were actually released 
(i.e. skip 3.0.0 because it was never released), and approved changes. 
So, proposed changes should always be made on branches, and then 
cherry-picked into the master.

We may also want to change the ports/debian directory in the Parrot 
github repository to a git submodule pointing to the alioth pkg-parrot 
master. That would guarantee that the two stay in sync (but may be more 
difficult for Parrot core developers making updates to the debian 
package files).

Allison