Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.debian.maint.python > #16189

Re: Moving default branch after project creation

From Nicholas D Steeves <sten@debian.org>
Newsgroups linux.debian.maint.python
Subject Re: Moving default branch after project creation
Date 2024-08-08 01:00 +0200
Message-ID <J8XNn-3qlF-9@gated-at.bofh.it> (permalink)
References <J8VBT-3p4M-3@gated-at.bofh.it> <J8VBT-3p4M-1@gated-at.bofh.it>
Organization linux.* mail to news gateway

Show all headers | View raw


[Multipart message — attachments visible in raw view] - view raw

Julian Gilbey <julian@d-and-j.net> writes:

> On Wed, Aug 07, 2024 at 08:27:33PM +0300, Alexandru Mihail wrote:
>> Hi, I've recently created
>> https://salsa.debian.org/python-team/packages/psrecord following
>> previous ITP. The main branch was set to main and I'd like to move it
>> to DEP compliant debian/master and delete the main branch. 
>
> The candidate DEP-14 (https://dep-team.pages.debian.net/deps/dep14/)
> currently reads:
>
>   In Debian this means that uploads to unstable and experimental
>   should be prepared either in the debian/latest branch or
>   respectively in the debian/unstable and debian/experimental
>   branches.
>
> I'm not sure where you got debian/master from?

FYI debian/master was DEP14:

  Changes
    2014-11-05: Initial draft by Raphaël Hertzog.
    2016-11-09: Extended version mangling to troublesome dots -- Ian Jackson.
    2020-11-29:
      * Replace <vendor>/master with <vendor>/latest
      * Recommend <vendor>/<suite> over <vendor>/<codename> for the devel branch
      * For native packages, require the default branch to be a devel branch
      * Minor typo fixes and cosmetic changes
      * Promote DEP to State: CANDIDATE
  Last edited Fri, 08 Mar 2024 12:33:22 +0000
  https://dep-team.pages.debian.net/deps/dep14/

It's certain that there are many packages that follow DEP14 DRAFT rather
than CANDIDATE.  An alternative interpretation is that DEP14 strong
recommends (ie "should use", "should be", "we recommend")
<vendor>/latest rather than <vendor>/master.  Thus, <vendor>/master is
arguably still more DEP14 than not.  We've also seen the proliferation
of <vendor>/main development branches that fulfil all of the technical
objectives of DEP14, and I would consider them to also be DEP14.

As an aside, I'm curious what the undocumented 2024 edit was.

Best,
Nicholas

Back to linux.debian.maint.python | Previous | NextPrevious in thread | Next in thread | Find similar | Unroll thread


Thread

Re: Moving default branch after project creation Julian Gilbey <julian@d-and-j.net> - 2024-08-07 22:40 +0200
  Re: Moving default branch after project creation Nicholas D Steeves <sten@debian.org> - 2024-08-08 01:00 +0200
  Re: Moving default branch after project creation Carsten Schoenert <c.schoenert@t-online.de> - 2024-08-08 06:00 +0200
    Re: Moving default branch after project creation Julian Gilbey <julian@d-and-j.net> - 2024-08-08 08:00 +0200
      Re: Moving default branch after project creation Carsten Schoenert <c.schoenert@t-online.de> - 2024-08-08 09:00 +0200
        Re: Moving default branch after project creation Martin <debacle@debian.org> - 2024-08-08 09:50 +0200
          Re: Moving default branch after project creation Carsten Schoenert <c.schoenert@t-online.de> - 2024-08-08 13:10 +0200
      Re: Moving default branch after project creation Carsten Schoenert <c.schoenert@t-online.de> - 2024-08-12 08:20 +0200
        Re: Moving default branch after project creation Alexandru Mihail <alexandru.mihail2897@gmail.com> - 2024-08-12 09:40 +0200

csiph-web