New MoarVM release and maintainer field

[Daniel Dehennin]

gregor herrmann <gregoa at debian.org> writes:

> It's no problem to upload it now.

Thanks.

>> I made a commit to set the maintainer to the team, like for nqp and
>> rakudo, I hope it's correct.
>
> Sounds good.

Do I need to set some “Uploaders” like in thoses packages?

>  
>> Everything is on a dedicated branch[1] for review.
>
> Why not on master?
> (Just curious, I don't know any team conventions ... In general I'd
> expect new releases on master.)

I just have the habit to use temporary branches, make sure everything is
ok and then merge, like in the “successful git branching model”[1].

Regards.

Footnotes: 
[1]  http://nvie.com/posts/a-successful-git-branching-model/

-- 
Daniel Dehennin
Récupérer ma clef GPG: gpg --recv-keys 0xCC1E9E5B7A6FE2DF
Fingerprint: 3E69 014E 5C23 50E8 9ED6  2AAD CC1E 9E5B 7A6F E2DF
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 342 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/pkg-rakudo-devel/attachments/20150425/29c5b2e7/attachment.sig>