Our ticketing system¶

Obsolete. We now use Lino Noi as ticketing system.

trac¶

Trac is our ticketing system. When we say trac, then we usually mean our public trac environment at http://trac.lino-framework.org

milestone¶

In trac we can define “milestones”.

“When you file the ticket, you (the ticket submitter) use the version field to indicate the version of the software that exhibits the defect. Once the software maintainer triages the ticket, they assign it to a milestone that indicates the time frame in which the defect will be fixed. The ticket can be re-assigned from one milestone to another depending on project schedule, but the version number will remain the same. Version numbers refer to things that have already been released, and milestones refer to things that are in development or planned for the future and not yet started.” (user “bta” on stackoverflow in Proper way to use versions and milestones)

Every milestone represents either an upgrade or a release.

release¶

A release is when a given project gets a new version number and is published on PyPI. We do this using the fab release command.

upgrade¶

An upgrade is when the Lino installation at a given site gets upgraded.

site¶

A site is a “Django project” running on a given server.

Rules¶

Every upgrade and every release should get a milestone in trac.

Neither upgrades nor releases are not strictly scheduled. We do them when they are ready.

Upgrades are not the same as releases. For example, a release implies a new product version.

Naming milestones¶

Release milestones are named XXXX-version, where XXXX is our internal codename (atelier, lino, welfare…) and version is a string like “1.6.18”.

Upgrade milestones are named XXXX-YYYY-MM, where

XXXX represents the site (these are named using short names like “dsbe”, “chat”, “lf”, “eiche”, “fijal” and so on).
YYYY-MM the month of the (initial) schedule date.
If there is more than one upgrade for a given site in a given month, then we add a sequence number: “XXXX-YYYY-MM-2”