public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Laszlo Ersek" <lersek@redhat.com>
To: devel@edk2.groups.io, rebecca@bsdio.com,
	Liming Gao <gaoliming@byosoft.com.cn>,
	Michael D Kinney <michael.d.kinney@intel.com>,
	Michael Kubacki <mikuback@linux.microsoft.com>
Cc: Gerd Hoffmann <kraxel@redhat.com>
Subject: Re: [edk2-devel] Tagging and releases of edk2-basetools
Date: Wed, 28 Feb 2024 09:27:57 +0100	[thread overview]
Message-ID: <81f30b3f-9b06-21b6-09e6-327ca181a07e@redhat.com> (raw)
In-Reply-To: <257c6ca5-3569-465c-bd86-b1c95f4de629@bsdio.com>

On 2/28/24 02:15, Rebecca Cran wrote:
> edk2-basetools is finally fixed and releases can once again be published
> to PyPI.
> 
> However, in moving from setup.py to pyproject.toml the process has
> changed, and Joey suggested the old way might have been chosen
> deliberately to be different from edk2-pytool-library and
> edk2-pytool-extensions.
> 
> 
> Previously it fetched the list of releases from PyPI and incremented the
> version number before publishing a new version, while it now depends on
> the git repo being tagged.
> 
> 
> Should I work on migrating the old code and figuring out how to make it
> work with pyproject.toml?
> 
> 

Adding Gerd, because of
<https://github.com/tianocore/edk2-basetools/issues/85> -- "[Feature]:
please add release tags to the repository".

Laszlo



-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#116095): https://edk2.groups.io/g/devel/message/116095
Mute This Topic: https://groups.io/mt/104615885/7686176
Group Owner: devel+owner@edk2.groups.io
Unsubscribe: https://edk2.groups.io/g/devel/unsub [rebecca@openfw.io]
-=-=-=-=-=-=-=-=-=-=-=-



  reply	other threads:[~2024-02-28  8:28 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-28  1:15 [edk2-devel] Tagging and releases of edk2-basetools Rebecca Cran
2024-02-28  8:27 ` Laszlo Ersek [this message]
2024-02-28 11:35   ` Gerd Hoffmann
2024-02-28 17:00     ` Rebecca Cran

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-list from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=81f30b3f-9b06-21b6-09e6-327ca181a07e@redhat.com \
    --to=devel@edk2.groups.io \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox