Project Processes
Apache Ant™ Project Processes/Checklists
Here we describe some of the processes we use.
Retire a subproject or component
The process starts by a format vote by the Ant PMC
on the main development mailinglist.
Basically we have to announce it and make resources read-only.
Retire: Version Control
Most of our source code is in git, only "site" and "sandbox" use subversion.
We place a marker RETIRED_PROJECT file on the top level.
Add a note at the top of a README file as well so it is immediately visible
to people browsing the github mirror. Include a link to this page for
a possible future reactivation and a link to the vote result.
Ask infra to make the repository read-only.
Retire: Issue Tracker
If the subproject/component has its own issue tracker we have to close that.
It is enough to make it read-only, so these information are longer available.
Retire: Mailing List
If the subproject/component has its own mailing list we have to close
this. We should send a final email.
Retire: Announcement
We have to announce the retirement of the subproject at dev@ant,
announce@apache and the Ant main page.
Retire: Build Jobs
All build jobs on Jenkins@Apache, TeamCity and Gump have to be deleted.
Retire: Homepage
Add the retirement to the archive-page.
Retire: Releases
The last released artifacts, if any, should be removed from the Apache
distribution server. To do so, remove any artifact related to the retired
subproject in https://dist.apache.org/repos/dist/release/ant/
(it is managed with subversion).
Note: as every Apache release, nothing is deleted but everything is archived,
the artifacts will still be available at https://archive.apache.org/dist/ant/
(or https://archive.apache.org/dist/incubator/
for Incubator releases).
Retire: Free Further Resources
Maybe a subproject locks further resources (update-site, ...).
So we have to unblock them.
Reactivate a subproject or component
The process starts by a format vote by the Ant PMC
on the main development mailinglist.
Basically we have to announce it and make resources read-write again.
Reactivate: Version Control
Delete the marker file "RETIRED_PROJECT".
Delete the note at the top of a README file as well so it is immediately
visible to people browsing the github mirror.
Ask infra to make the repository read-write again.
Reactivate: Issue Tracker
If the subproject/component has its own issue tracker we have to reopen that.
Reactivate: Mailing List
Because reopeing implies a smaller community we should use the main mailinglist
dev@ant. So reactivating a special list is not required and could be postponed
to a later PMC decision.
Reactivate: Announcement
Announce the reactivation of the subproject at dev@ant.
Decide about announcing the reactivation of the subproject at announce@apache.
Reactivate: Build Jobs
New build jobs on Jenkins@Apache, TeamCity and Gump could be created as
required.
Reactivate: Homepage
Remove the component from the archive-page.
Reactivate: Releases
All earlier releases are available at https://archive.apache.org/dist/ant/.
We don't have to copy them back to https://dist.apache.org/repos/dist/release/ant/.
But further releases are placed here.
Reactivate: Free Further Resources
Make existing read-only resources read-write again.
Further resources could be gained as required.