os/doc
3
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity
doc/share/images/articles/releng/branches-releng4.pic

105 lines
2.4 KiB
Text
Raw Normal View History

We have "too" many releases in 4.x branch, so branches.pic's default scaling model "got confused" and most of messages become unreadable. Resolve this problem, by spliting of branches diagram into three diagrams: head, releng3 and releng4. It reduces width usage and gives us more control over scalling control.
2004-04-08 10:27:59 +02:00
.\" -*- nroff -*-
.\" $FreeBSD$
.PS 6
RELENG_4_0_0_RELEASE:
ellipse width .9 "\s-24.0-RELEASE\s+2"
move right 4
move up .5
"\s-1RELENG_4 (4.x STABLE Branch)\s+1"
line -> down from RELENG_4_0_0_RELEASE.s
RELENG_4_1_0_RELEASE:
box width .5 "\s-24.1R\s+2"
line -> down from RELENG_4_1_0_RELEASE.s
RELENG_4_1_1_RELEASE:
box width .5 "\s-24.1.1R\s+2"
line -> down from RELENG_4_1_1_RELEASE.s
RELENG_4_2_0_RELEASE:
box width .5 "\s-24.2R\s+2"
line -> right from RELENG_4_2_0_RELEASE.e
RELENG_4_3_0_RELEASE:
ellipse width .5 "\s-24.3R\s+2"
line -> down from RELENG_4_3_0_RELEASE.s
RELENG_4_3:
box width .9 "\s-3RELENG_4_3\s+3" dashed
line -> right from RELENG_4_3_0_RELEASE.e
RELENG_4_4_0_RELEASE:
ellipse width .5 "\s-24.4R\s+2"
line -> down from RELENG_4_4_0_RELEASE.s
RELENG_4_4:
box width .9 "\s-3RELENG_4_4\s+3" dashed
line -> right from RELENG_4_4_0_RELEASE.e
RELENG_4_5_0_RELEASE:
ellipse width .5 "\s-24.5R\s+2"
line -> down from RELENG_4_5_0_RELEASE.s
RELENG_4_5:
box width .9 "\s-3RELENG_4_5\s+3" dashed
line -> right from RELENG_4_5_0_RELEASE.e
RELENG_4_6_0_RELEASE:
ellipse width .5 "\s-24.6R\s+2"
line -> down from RELENG_4_6_0_RELEASE.s
RELENG_4_6_2_RELEASE:
ellipse width .5 "\s-24.6.2R\s+2"
Whitespace cleanup
2004-04-09 12:09:41 +02:00
line -> down from RELENG_4_6_2_RELEASE.s
We have "too" many releases in 4.x branch, so branches.pic's default scaling model "got confused" and most of messages become unreadable. Resolve this problem, by spliting of branches diagram into three diagrams: head, releng3 and releng4. It reduces width usage and gives us more control over scalling control.
2004-04-08 10:27:59 +02:00
RELENG_4_6:
box width .9 "\s-3RELENG_4_6\s+3" dashed
line -> right from RELENG_4_6_0_RELEASE.e
RELENG_4_7_0_RELEASE:
ellipse width .5 "\s-24.7R\s+2"
Whitespace cleanup
2004-04-09 12:09:41 +02:00
line -> down from RELENG_4_7_0_RELEASE.s
We have "too" many releases in 4.x branch, so branches.pic's default scaling model "got confused" and most of messages become unreadable. Resolve this problem, by spliting of branches diagram into three diagrams: head, releng3 and releng4. It reduces width usage and gives us more control over scalling control.
2004-04-08 10:27:59 +02:00
RELENG_4_7:
box width .9 "\s-3RELENG_4_7\s+3" dashed
Whitespace cleanup
2004-04-09 12:09:41 +02:00
line -> right from RELENG_4_7_0_RELEASE.e
We have "too" many releases in 4.x branch, so branches.pic's default scaling model "got confused" and most of messages become unreadable. Resolve this problem, by spliting of branches diagram into three diagrams: head, releng3 and releng4. It reduces width usage and gives us more control over scalling control.
2004-04-08 10:27:59 +02:00
RELENG_4_8_0_RELEASE:
ellipse width .5 "\s-24.8R\s+2"
Whitespace cleanup
2004-04-09 12:09:41 +02:00
line -> down from RELENG_4_8_0_RELEASE.s
We have "too" many releases in 4.x branch, so branches.pic's default scaling model "got confused" and most of messages become unreadable. Resolve this problem, by spliting of branches diagram into three diagrams: head, releng3 and releng4. It reduces width usage and gives us more control over scalling control.
2004-04-08 10:27:59 +02:00
RELENG_4_8:
box width .9 "\s-3RELENG_4_8\s+3" dashed
Whitespace cleanup
2004-04-09 12:09:41 +02:00
line -> right from RELENG_4_8_0_RELEASE.e
We have "too" many releases in 4.x branch, so branches.pic's default scaling model "got confused" and most of messages become unreadable. Resolve this problem, by spliting of branches diagram into three diagrams: head, releng3 and releng4. It reduces width usage and gives us more control over scalling control.
2004-04-08 10:27:59 +02:00
RELENG_4_9_0_RELEASE:
ellipse width .5 "\s-24.9R\s+2"
Whitespace cleanup
2004-04-09 12:09:41 +02:00
line -> down from RELENG_4_9_0_RELEASE.s
We have "too" many releases in 4.x branch, so branches.pic's default scaling model "got confused" and most of messages become unreadable. Resolve this problem, by spliting of branches diagram into three diagrams: head, releng3 and releng4. It reduces width usage and gives us more control over scalling control.
2004-04-08 10:27:59 +02:00
RELENG_4_9:
box width .9 "\s-3RELENG_4_9\s+3" dashed
Whitespace cleanup
2004-04-09 12:09:41 +02:00
line -> right from RELENG_4_9_0_RELEASE.e
Add FreeBSD 4.10-RELEASE.
2004-05-28 02:38:14 +02:00
RELENG_4_10_0_RELEASE:
ellipse width .5 "\s-24.10R\s+2"
line -> down from RELENG_4_10_0_RELEASE.s
RELENG_4_10:
box width .9 "\s-3RELENG_4_10\s+3" dashed
line -> right from RELENG_4_10_0_RELEASE.e
Add 4.11R.
2005-01-25 18:25:38 +01:00
RELENG_4_11_0_RELEASE:
ellipse width .5 "\s-24.11R\s+2"
line -> down from RELENG_4_11_0_RELEASE.s
RELENG_4_11:
box width .9 "\s-3RELENG_4_11\s+3" dashed
line -> right from RELENG_4_11_0_RELEASE.e
We have "too" many releases in 4.x branch, so branches.pic's default scaling model "got confused" and most of messages become unreadable. Resolve this problem, by spliting of branches diagram into three diagrams: head, releng3 and releng4. It reduces width usage and gives us more control over scalling control.
2004-04-08 10:27:59 +02:00
RELENG_4:box "\s-24-STABLE\s+2"
.PE
Reference in a new issue Copy permalink