Changeset 32310 for trunk/dports/news


Ignore:
Timestamp:
Dec 24, 2007, 3:52:09 AM (12 years ago)
Author:
vinc17@…
Message:

Updated comment about the development model of tin, and the differences
between tin, tin-devel and tin-recent.

File:
1 edited

Legend:

Unmodified
Added
Removed
  • trunk/dports/news/tin-recent/Portfile

    r32145 r32310  
    55#  * stable patches, numbered ddd (001, 002, and so on), which are
    66#    applied to the current stable branch, and in general, to the
    7 #    unstable branch too (i.e. when this makes sense);
     7#    unstable branch too (i.e. when there is one and when this makes
     8#    sense);
    89#  * unstable patches (new features), numbered Uddd (U001, U002,
    910#    and so on), which are applied to the unstable branch only.
    10 # At some point, the unstable branch is regarded as stable, making
    11 # a new stable release and a new stable branch.  Then this branch
    12 # gets stable patches as usual (fixes, translation updates...).
    13 # A new unstable branch is created (split from the current stable
    14 # branch) as soon as the first unstable patch (U001) needs to be
    15 # applied.
     11# In general, at some point in the time, there are two currently
     12# supported branches: a stable branch (e.g. 1.6) and an unstable
     13# branch (e.g. 1.7).  At some later point (i.e. after a feature
     14# freeze?), the development line (coming from the unstable branch)
     15# is regarded as stable; this leads to a new stable release (e.g.
     16# 1.8.0) and a new stable branch (e.g. 1.8).  At this point, the
     17# old stable branch (e.g. 1.6) is abandonned.  Then the new stable
     18# branch (1.8) gets stable patches as usual (fixes, translation
     19# updates...), leading to new stable releases (e.g. 1.8.1), which
     20# correspond to the latest unstable release (e.g. 1.7.10) + bug
     21# fixes.  As soon as the first unstable patch (U001) needs to be
     22# applied, a new unstable branch (e.g. 1.9) is created (split from
     23# the current stable branch).
    1624
    1725# Portfile update policy: Follow the development line as shown on
    1826# <http://www.tin.org/history.html>, preferring unstable versions
    19 # to stable ones when there is a split.
     27# to stable ones when there is a split, i.e. stay on the right.
    2028# The goal of this tin-recent port (as opposed to tin and tin-devel)
    2129# is to have the highest upstream version (regarded as either stable
     
    2331# thus benefiting from some port management features, such as those
    2432# provided by "port outdated" and "port upgrade".
     33
     34# For instance, if ports are updated as soon as tin versions are
     35# released:
     36#    tin   tin-devel   tin-recent
     37#   1.6.2    1.7.9       1.7.9
     38#   1.6.2    1.7.10      1.7.10
     39#   1.8.0    1.7.10      1.8.0
     40#   1.8.1    1.7.10      1.8.1
     41#   1.8.1    1.9.0       1.9.0
     42#   1.8.1    1.9.1       1.9.1
     43#   1.8.2    1.9.1       1.9.1
     44#   1.8.3    1.9.2       1.9.2
     45# where:
     46#   1.7.9  =  1.7.8  + patches U040 to U045.
     47#   1.7.10 =  1.7.9  + patches U046 to U052.
     48#   1.8.0  =  1.7.10 + patches U053 to U056.
     49#   1.8.1  =  1.8.0  + patches 001 to 006.
     50#   1.9.0  =  1.8.1  + patches 007, 008 and U001.
     51#   1.9.1  =  1.9.0  + patches 009 and U002.
     52#   1.8.2  =  1.8.1  + patches 007 to 011.
     53#   1.8.3  =  1.8.2  + patches 012 to 018.
     54#   1.9.2  =  1.9.1  + patches 010 to 018 and U003 to U006.
     55# Said otherwise:
     56#   1.8.1  =  1.8.0  + patches 001 to 006.
     57#   1.9.0  =  1.8.0  + patches 001 to 008 and U001.
     58#   1.9.1  =  1.8.0  + patches 001 to 009 and U001 to U002.
     59#   1.8.2  =  1.8.0  + patches 001 to 011.
     60#   1.8.3  =  1.8.0  + patches 001 to 018.
     61#   1.9.2  =  1.8.0  + patches 001 to 018 and U001 to U006.
    2562
    2663# Note: Portfile reformatted according to portstyle(7).
Note: See TracChangeset for help on using the changeset viewer.