public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Rebecca Cran" <rebecca@bsdio.com>
To: Gerd Hoffmann <kraxel@redhat.com>,
	Laszlo Ersek <lersek@redhat.com>, Sean <spbrogan@outlook.com>
Cc: devel@edk2.groups.io, Liming Gao <gaoliming@byosoft.com.cn>,
	Michael D Kinney <michael.d.kinney@intel.com>,
	Michael Kubacki <mikuback@linux.microsoft.com>
Subject: Re: [edk2-devel] Tagging and releases of edk2-basetools
Date: Wed, 28 Feb 2024 10:00:10 -0700	[thread overview]
Message-ID: <d94b802e-abac-4956-8b68-fb6b7b786c8c@bsdio.com> (raw)
In-Reply-To: <wda6ew7veibyqefxqfve6tci3dzjhfm2ovlibiygy4usqcg5xf@4r7yh6exsbxs>

Thanks.

Since Sean commented on 
https://github.com/tianocore/edk2-basetools/issues/85, adding him for 
more context around the original request.


-- 
Rebecca Cran


On 2/28/24 04:35, Gerd Hoffmann wrote:
> On Wed, Feb 28, 2024 at 09:27:57AM +0100, Laszlo Ersek wrote:
>> 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?
> Not sure what exactly you want migrate.  I think releases being
> triggered by tags in the repo makes alot of sense.
>
> take care,
>    Gerd
>


-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#116124): https://edk2.groups.io/g/devel/message/116124
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 17:00 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
2024-02-28 11:35   ` Gerd Hoffmann
2024-02-28 17:00     ` Rebecca Cran [this message]

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=d94b802e-abac-4956-8b68-fb6b7b786c8c@bsdio.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