Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [jakartaee-platform-dev] Heads-up: Ed and Arjan using Azure Boards to aid in release co-coordinator role.
  • From: Edward Burns <Edward.Burns@xxxxxxxxxxxxx>
  • Date: Tue, 4 Jul 2023 03:23:30 +0000
  • Accept-language: en-US
  • Arc-authentication-results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=microsoft.com; dmarc=pass action=none header.from=microsoft.com; dkim=pass header.d=microsoft.com; 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=kiJWpMTY9I6CY4GLcwLHscDmIvsGZCKnicy3doNiO/g=; b=GWCAWU5/d1De+LCD8Sj8EilPp4XQeOAXh3htadk29eXTemyCTEAg8ZisSM9jm5prGnlQTjw6w2NMKpRri3fv8+kdZ2muvdZ1WfWEudqkXFZkuDjw1poQ7hboSZcdw4VpV65Ws4wpxJiOaJuMLMMHN8ZGlrzdPHh2TBS+qZtI/IQjqc7G7bI1octx5osNtJ4VfAzwLJquh9IY9LYxfW8xfuLG1m93OmCPa0CABqQvayaTPKfEbQ2ZGd9mqffMfYzf1O8yr6tB8lEEOY7Z6TiEChCpdq5tlHYtdELnFdyzXtqhmQ3iqXBSyjd3HnHNFKbhsUlr6gL2SX1WOoDYft1DYA==
  • Arc-seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=dqLxO/UfTeGHQN8hi6erEegEvaQHr9/jKbPobOwZZZw5ytYh0YYlhFllaKdeZaxJwhSl8piCvFsfaKMUJa1dAeBguFdK43hf3jRy18VdDMHEO5KXzzgzHzu98yIXKL+sw5TpN/V0apuXeFcvPxwvsifu0CpXFL77PoXEFm4nVsTo19d2/CQtblWy8SKiq2UiXPiD8ja9o4PRom5g8hTsoOJ3kdrg9b+yHM0hC0pTRNBClUkKO5uEMvkDDTf0q0zNpL/7E1ZKYYBb/KZQEq6phyhsCmOIo8CNdXoMqI9xWj1/CHkOvyqf9NQuEAFj5ZXAOse6tXcqKnPy5ya47zlI8A==
  • Delivered-to: jakartaee-platform-dev@xxxxxxxxxxx
  • List-archive: <https://www.eclipse.org/mailman/private/jakartaee-platform-dev/>
  • List-help: <mailto:jakartaee-platform-dev-request@eclipse.org?subject=help>
  • List-subscribe: <https://www.eclipse.org/mailman/listinfo/jakartaee-platform-dev>, <mailto:jakartaee-platform-dev-request@eclipse.org?subject=subscribe>
  • List-unsubscribe: <https://www.eclipse.org/mailman/options/jakartaee-platform-dev>, <mailto:jakartaee-platform-dev-request@eclipse.org?subject=unsubscribe>
  • Msip_labels: MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_Enabled=True; MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_SiteId=72f988bf-86f1-41af-91ab-2d7cd011db47; MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_SetDate=2023-06-27T13:20:14.9689808Z; MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_ContentBits=0; MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_Method=Standard
  • Thread-index: AQHZqPocSguSLLrArk2tU7nV93hU1a+o+SsE
  • Thread-topic: Heads-up: Ed and Arjan using Azure Boards to aid in release co-coordinator role.

Here is a progress update.

  • Issue https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/issues/3322 has been filed and resolved.
  • I am working through all of the non-closed issues in the jakarta-ee-platform issue tracker and slotting them into a hierarchical structure of Epic/Feature/User Story. This is my process as release co-coordinator to force me to understand, reason about, and coordinate the work for EE 11.
  • The actual work is being tracked in jea-36.
  • Here is my process.
  • For each issue in this query
    • Find the one-and-only-one right Epic/Feature/User Story to link it. This may change in the future as I learn more.
      • Link it as an Existing Issue of type GitHub Issue in the Links section.
      • Once linked, add the label jea-linked to the GitHub Issue. This will cause it to disappear from the query. Be sure select elsewhere in the whitespace of the page to cause GitHub to actually add the label. Failure to do this will cause the label not to be added.
      • Bonus: edit the description to provide a back link into AzDO by using the inserting the text AB#<AzDO issue number>.
    • When creating a new User Story, decide if we are actively working on it in the short term. 
      • If so, schedule it into a Sprint: 2023-07, 2023-08, 2023-09. If you need to go further out than that, schedule it into sprint Future.
      • If we are not actively working on it, schedule it into sprint Future.
      • Scheduling a User Story into a sprint is a matter of setting the Iteration field.
    • Create new Epic/Feature/User Story work items as necessary, but be extremely mindful and never create a semantic duplicate.

I have 35 issues left. I will split them up with Arjan so I can get them done more quickly.

Once I’ve done this, I hope we can start to increase velocity of progress.

Ed

 

From: Edward Burns <Edward.Burns@xxxxxxxxxxxxx>
Date: Tuesday, June 27, 2023 at 09:23
To: jakartaee-platform-dev@xxxxxxxxxxx <jakartaee-platform-dev@xxxxxxxxxxx>
Subject: Heads-up: Ed and Arjan using Azure Boards to aid in release co-coordinator role.

Hello Jakarta EE Platform team.

 

I've been a fan of using an appropriate level of process formality for a very long time. Recently, I've grown accustomed to Microsoft's system of record for project management, Azure Boards. This email is a notification that Arjan and I will be using this software to aid in our work as release co-coordinators. No one (except for Arjan) will be forced to use this system, though it really would be helpful if you played along if I ask you to. GitHub Projects and Issues will continue to be the system of record for "leaf node" level tasks.

 

Once I get the Azure Boards organization/project configured I will share more details here.

 

Thanks for your support.

 

Ed

 

Back to the top