Hi Dave,
>From an Attic PoV, this process is already reasonably automated and
takes no additional effort on our part - all the effort is on the
Infra side.
Once the Board resolution retiring the project has been confirmed we
generate a YAML file for the project which adds it to the Attic
website and generates a set of project specific templates. One of
those templates is for an INFRA JIRA ticket to shutdown the project's
resources and that includes removing distributions and setting up a
redirect.
https://attic.apache.org/process-howto.html#5-get-infra-to-lock-down-project-resources
An example of an INFRA JIRA for a recently retired project is here:
https://issues.apache.org/jira/browse/INFRA-28164
So my observations are:
- the real benefit of this is removing a task from the Infra team
- if the task is Attic controlled, then it will add a (small) step to
our retirement process (I would prefer not to do that)
- if the task is automated by tooling, then Attic just needs to
adjust our template for the INFRA JIRA (preferable IMO)
- Will this include setting up the redirect to the project's Attic page?
https://dist.apache.org/repos/dist/release/servicemix/.htaccess
Given the number of project retirements per year, I think it would be
worth consulting with Infra whether removing this one small task from
the things they have todo when a project retires is worth the effort
to automate.
https://attic.apache.org/stats.html
Regards
Niall
On Mon, 31 Aug 2026 at 02:59, Dave Fisher <[email protected]> wrote:
>
> Hi Attic team,
>
> The tooling team can help the attic by automatically archiving all of PMC’s
> project releases once the Board resolution happens.
>
> We are working on the new beta release: https://releases.apache.org/
>
> The implementation detail we wish to discuss is should the Board action or
> the Attic committee start this retirement process? We are ready to support
> both. Since the Attic PMC is responsible for this change we wish that you
> would choose our course.
>
> If the Attic Committee wishes to take charge of performing all the steps then
> we will be building an Attic Dashboard. If completely automated then one is
> uneccessary. A delta admin view is likely good in either case.
>
> Best,
> Dave
