Opened 12 months ago

Closed 3 months ago

#30839 closed task (fixed)

Update EndOfLifeTor.md with our latest end of life process

Reported by: teor Owned by: teor
Priority: Medium Milestone: Tor: 0.4.4.x-final
Component: Core Tor/Tor Version:
Severity: Normal Keywords: 044-should
Cc: teor Actual Points:
Parent ID: #30917 Points: 1
Reviewer: Sponsor:

Description

The draft is currently in:
https://github.com/torproject/tor/pull/1062/files

Once #28453 merges, I will update the document with:

  • Update git scripts
  • Update Tor Travis Cron Jobs instructions
  • Jenkins test builds
  • Jenkins deb builds, including nightlies and experimental-(latest release), which needs to have a successful build before:
    • Debian website instructions, including JavaScript and no script lists
    • Chutney Travis CI
    • Stem Travis CI
    • sbws Travis CI (the sbws CI does not use multiple tor versions yet, so add a ticket number)

Child Tickets

Change History (16)

comment:1 Changed 12 months ago by teor

The Travis Cron Job instructions are:

  • make sure you have write access to https://github.com/torproject/tor
    • if you don't, open a ticket to be added to the GitHub network-team group
  • go to https://travis-ci.org/torproject/tor/settings
  • log in to Travis using your GitHub account
  • scroll down to the Cron Jobs section
  • tap the bin icon to remove jobs for end of life branches
  • for active maint branches (master, alpha, latest stable), we want a daily job, that doesn't run if there has been a build (triggered by a merge) in the last 24 hours
  • for backport maint branches (old stables, LTS), we want a weekly job, that doesn't run if there has been a build in the last 24 hours

Edit: fix a typo

Last edited 4 months ago by teor (previous) (diff)

comment:2 Changed 12 months ago by teor

Owner: set to teor
Status: newassigned

comment:3 Changed 12 months ago by teor

Status: assignedneeds_information

I'm going to wait about a week for all the code to merge, and further config changes to be made. See the children of #30835.

comment:4 Changed 12 months ago by teor

Sponsor: Sponsor31-can

The CI we're documenting here is used to test refactoring,

comment:5 Changed 11 months ago by nickm

Points: 0.5

comment:6 Changed 11 months ago by teor

Status: needs_informationneeds_revision
Type: defecttask

comment:7 Changed 11 months ago by gaba

Cc: teor added
Keywords: network-team-roadmap-september added
Points: 0.51

comment:8 Changed 10 months ago by gaba

Milestone: Tor: 0.4.1.x-finalTor: 0.4.2.x-final

comment:9 Changed 9 months ago by nickm

Keywords: 042-can added

comment:10 Changed 9 months ago by nickm

Keywords: s31-docs added

comment:11 Changed 8 months ago by teor

Keywords: 041-should removed

comment:12 Changed 5 months ago by teor

There's also a bunch of other work we do when we stop supporting a release:

  • Make deprecated options obsolete, and remove their implementations

And an LTS release:

Along with removing the tor release from the chutney, stem, and sbws CI, we should also update to the latest CI dependencies:

  • OS images
  • python versions

We should do these tasks for fallback-scripts at the same time, even though it doesn't depend on a particular tor version in CI.

This is also a good time to grep for references to obsolete releases (for example: 0.2.9 and 029), and update or remove them.

comment:13 Changed 5 months ago by gaba

Keywords: network-team-roadmap-september removed
Sponsor: Sponsor31-can

Sponsor closed. Remove from roadmap.

comment:14 Changed 4 months ago by teor

Keywords: 044-should added; 042-can s31-docs removed
Milestone: Tor: 0.4.2.x-finalTor: 0.4.4.x-final

comment:15 Changed 3 months ago by teor

Parent ID: #30835

comment:16 Changed 3 months ago by teor

Parent ID: #30917
Resolution: fixed
Status: needs_revisionclosed

Done in #30917.

Note: See TracTickets for help on using tickets.