comanage-dev - Re: [comanage-dev] Canceling v4.0.3, merging to v4.1.0
Subject: COmanage Developers List
List archive
- From: Scott Koranda <>
- To: Benn Oshrin <>
- Cc: COmanage Dev <>
- Subject: Re: [comanage-dev] Canceling v4.0.3, merging to v4.1.0
- Date: Mon, 27 Jun 2022 08:50:30 -0500
- Arc-authentication-results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=illinois.edu; dmarc=pass action=none header.from=illinois.edu; dkim=pass header.d=illinois.edu; arc=none
- Arc-message-signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-AntiSpam-MessageData-ChunkCount:X-MS-Exchange-AntiSpam-MessageData-0:X-MS-Exchange-AntiSpam-MessageData-1; bh=gTRrRG+CKB3eZSpbpFnjd7KcbZjZbbIrkbnNlHKdZD4=; b=NC7aC/XNn8rgjLaxKSg4dZBda5U3Ez4BWabAFbLLJ6dTGCzaNjyxa1kbr2X+YThUKmkN2NeLrqLvQUT+CmDqnuggIWLsErjbwK4Y+NEMYw4B9rtp3FBnJJr3+TAKQpHT9fPQaSHzsCPC8k+DaOuJXgLUZ9m9mWEHEzxfTCDTEiru5UcOcayZen1Sz73dWCOuqh4+LJISHoZDEOg5CFI7sQesWROgDWfKIXKO8iHZ0oOsJdjvim1pd3H8wFbWsQDwv0yvs3EKLEviBAbGQaWPbM77aJZ6/NbHlre+sgG2T7XOPEbWiAFRgSnzRQpyAsRL/GJ1vSIXhiJpA+s4OGuKpw==
- Arc-seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=PSEgN8qDoELbkFVfVriC9Mx7ktMs80EOiYmCFIonXwQdYRBFEVdQrg9i/U6oRlzZdRlsENo9ffff9uc2hjM7JwOAplABj6QzvcCZ1a7K7BB7JbM22AXnMbOnh0yInxP1fETVigucrg+bjV/xtY0LNQwdTddeY07cpe8rbfoVRGDrfuZfjSiScfw9c1ADACZczpSFBeYKPoum7ZfivXwvdMmwzIDHnzM2fW8v8378sNuvp7+luQHYcmtoUym6MXTDlhF2b+O8d/NEOLsAx96HCsnvZF5DpmNNyQVuYSoXS48MKpuIbCInnra1nN86teJGogr865+Ik7B6wZfZqco7sQ==
Hi,
> Following up on today's discussion, I see only one small item in my queue
> that is blocking v4.1.0, so I intend to proceed with the plan to cancel
> v4.0.3 and jump directly to v4.1.0. The steps will be something like
>
> 1. Move all JIRA issues in v4.0.3 to v4.1.0
> 2. Triage remaining v4.1.0 issues
> 3. Merge hotfix-4.0.x into develop
> 4. Address any remaining v4.1.0 issues
> 5. Start RC process, probably right after the July 4 holiday
>
> We can review remaining JIRA items on our June 29 call, in the mean time
> please review any 4.0.3 or 4.1.0 issues of interest to or assigned to you,
> and move anything appropriate into a future release (4.1.1, 4.2.0, or
> FUTURE).
>
> If you have any concerns with the above, please let me know in the forum of
> your choosing.
I do not have a concern per se, but please remember that version 4.1.0
is targeted to be the first version that uses the new container
packaging infrastructure.
As such, I have a good amount of testing to do and documentation to move
into the wiki.
Also, because this is the first release that will use container
packaging incorporated into the repository, the release process will
need to be a bit different and I expect for this first go around we will
need to iterate and move the 4.1.0 tag (since the tag needs to include
code that works for all containers).
So I think the timeline is going to need more collaborative input from
the team (me specifically), and less direct mandates from you solely.
Thanks,
Scott
- [comanage-dev] Canceling v4.0.3, merging to v4.1.0, Benn Oshrin, 06/15/2022
- Re: [comanage-dev] Canceling v4.0.3, merging to v4.1.0, Scott Koranda, 06/27/2022
Archive powered by MHonArc 2.6.24.