mirror of
git://git.geda-project.org/gerbvhtdocs
synced 2025-05-09 03:23:18 +08:00
1.0.0 release
This commit is contained in:
parent
ee9a2dfeaa
commit
2ebb2b38a7
@ -13,8 +13,9 @@ quirks. Noticeable are:
|
||||
* Negative and positive layers versus clear and dark settings. This
|
||||
is so weird it makes you yoddle. Anyhow, Richard Lightman spread some
|
||||
light on the issue and sent in a patch that made it work properly.
|
||||
* Exposire flags on aperture macros revisited.
|
||||
* Exposure flags on aperture macros revisited.
|
||||
* Some minor build and segfault issues resolved.
|
||||
* Holes in circles silently ignored before.
|
||||
|
||||
Why stable and unstable?
|
||||
Juergen Haas and Tomasz Motylewski stepped forward and wanted to add
|
||||
@ -22,7 +23,7 @@ pick-and-place file handling to gerbv. The differences between GTK+ 1.2
|
||||
and GTK+ 2.* forced them to make a choice on one of the versions.
|
||||
Thus I decided in my great wisdom to branch of a stable branch to
|
||||
continue support for GTK+ 1.2. In the head branch (which thus is the
|
||||
unstable) GTK+ 1.2 support will be killed off.
|
||||
unstable) GTK+ 1.2 support will slowly be killed off.
|
||||
|
||||
What does that mean to all features?
|
||||
So all cool new features will be added to the unstable branch, while the
|
||||
@ -31,7 +32,9 @@ stable branch will continue to work just about the way it is today.
|
||||
What is the naming convention of the branches?
|
||||
I have decided to use the naming convention of stable-versus-unstable
|
||||
release from Linux. Thus this is 1.0.0. The first unstable release will
|
||||
be called 1.1.0.
|
||||
be called 1.1.0. In the CVS repository the HEAD branch will thus be the
|
||||
unstable branch and currently the stable branch has the tag
|
||||
STABLE_1_x_branch.
|
||||
|
||||
Homepage for gerbv is still http://gerbv.sourceforge.net/ where a bug database,
|
||||
a feature request database, the CVS and a commit mailinglist is available.
|
||||
@ -42,7 +45,7 @@ and grab gerbv-1.0.0.tar.gz
|
||||
|
||||
To install the program do
|
||||
1. gzip -dc gerbv-1.0.0.tar.gz | tar xf -
|
||||
2. cd gerbv-0.16
|
||||
2. cd gerbv-1.0.0
|
||||
3. ./configure
|
||||
4. make install
|
||||
|
||||
|
14
index.html
14
index.html
@ -158,6 +158,10 @@ original authors (which are listed in respective files).
|
||||
|
||||
<h3>News</h3>
|
||||
<ul>
|
||||
<li> 2004-12-28 : 1.0.0 release available
|
||||
<a href="http://prdownloads.sourceforge.net/gerbv/gerbv-1.0.0.tar.gz">here</a>.
|
||||
Announcement is readable <a href="ANNOUNCEMENT-1.0.0">here</a>.
|
||||
|
||||
<li> 2004-10-19 : Another beta of a windows version is released and available
|
||||
<a href="http://sourceforge.net/project/showfiles.php?group_id=33921&package_id=131878&release_id=276492">here</a>.
|
||||
<li> 2004-10-07 : A beta of a windows version is available
|
||||
@ -297,6 +301,16 @@ original authors (which are listed in respective files).
|
||||
|
||||
</ul>
|
||||
|
||||
<h3>Stable versus unstable</h3>
|
||||
Per 2004-12-28 gerbv is split into a stable and one unstable branch.
|
||||
The stable branch is something that will always work, but no new features will
|
||||
be added. GTK+ 1.2 will continue to work. In the unstable branch GTK+ 1.2 will
|
||||
be killed off and new features will be added. But as new features are added,
|
||||
new bugs will probably also crawl up.
|
||||
<br>
|
||||
The unstable branch will be the HEAD branch in CVS. The stable branch is
|
||||
has the tag STABLE_1_x_branch.
|
||||
|
||||
<h3>Install</h3>
|
||||
<ul>
|
||||
<h4>By downloading a release</h4>
|
||||
|
Loading…
x
Reference in New Issue
Block a user