On Fri, 2026-11-20 at 19:50 +0100, Arturo Bernal via dev wrote:
> All,
> 
> We are going ahead with the Jira -> GitHub Issues migration discussed
> earlier on this list (INFRA-28579). Scope:
> 
> HTTPCLIENT -> apache/httpcomponents-client (2347 issues)
> HTTPCORE -> apache/httpcomponents-core (779 issues)
> HTTPASYNC -> apache/httpasyncclient (138 issues, none open)
> 
> What is preserved: reporter and commenter identity, original 
> creation/close dates, fix versions as GitHub milestones, 
> "Affects"/"Backported to" links, component/type as labels, and a 
> back-link to the original Jira key in each issue
> body. Build-bot and old Hudson noise is dropped.
> 
> Plan:
> - All three start the same week, Mon Nov 23: HTTPCORE and HTTPASYNC
> each 
> in a single run, HTTPCLIENT in four runs split by creation date, run 
> back to back.
> - Once a project's issues are exported, that project is frozen in
> Jira: 
> no new issues should be filed there from that point on. Anything
> filed 
> in Jira after the export and before it goes read-only will be missed.
> Use GitHub Issues on the corresponding repo instead.
> 
> As decided, the migration starts on Nov 23 with HTTPCORE. Practical 
> concerns about the execution by Monday morning, please.
> 
> We will post here again once each project is done.
> 

Hi Arturo

Thank you for doing this. It is a major improvement for the project.

Oleg

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to