Migration to salsa.d.o + git workflow
- Subject: Migration to salsa.d.o + git workflow
- From: sebastien@debian.org (Sébastien Villemot)
- Date: Sat, 10 Mar 2018 11:24:07 +0100
- Message-id: <[🔎] 20180310102407.3gozrvgdn3ocr5nu@villemot.name>
- In-reply-to: <20180129175819.mfz2nn33bqj3hhoj@villemot.name>
- References: <20171228220058.tcid7seznwsc3ims@villemot.name> <6C09C82D-E9F5-4577-877A-94E43A85DA6A@debian.org> <20180103215125.qeaagba6gwogslym@villemot.name> <4B05E3A8-F038-42C8-94CE-B86D8B1CCC6E@debian.org> <20180129175819.mfz2nn33bqj3hhoj@villemot.name>
Hi,
On Mon, Jan 29, 2018 at 06:58:19PM +0100, S?bastien Villemot wrote:
> On Fri, Jan 05, 2018 at 09:51:45PM +0100, pvaneynd at debian.org wrote:
> > > Sure, once we agree on a workflow, I am willing to document it (with
> > > command-line examples) on a wiki page.
> >
> > You certainly have my blessing as you?re also doing most, if not all, of the difficult work!
>
> I wrote the following page documenting in detail the proposed workflow:
>
> https://wiki.debian.org/Teams/DebianCommonLisp/GitPackaging
>
> I also migrated the sbcl repository to salsa so that you can play with the
> example given in the wiki page.
>
> Please read the page and tell me if this workflow is ok with you.
>
> Then, unless there is something to be changed, I'll go ahead with the migration
> of all repositories to salsa (adapting the branch names in the process, and
> creating the pristine-tar branches).
I got no reply to my email above. Should I assume that the git workflow is ok
for the team and that I should complete the migration to salsa? (I already
migrated a few packages that I uploaded in the meantime).
Best,
--
??????? S?bastien Villemot
??????? Debian Developer
??????? http://sebastien.villemot.name
??????? http://www.debian.org
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/pkg-common-lisp-devel/attachments/20180310/3181b58c/attachment.sig>
Reply to: