-
Notifications
You must be signed in to change notification settings - Fork 92
Home
We will use this repository at Github as the development repository for the Wings3D.
There is another Git repository at Sourceforge that will only contain the ‘master’ branch
and tags for all releases.
There will soon be a 1.0 release. We have released two release candidates so far (1.0-rc1 and 1.0-rc2),
there will be at least one more.
After the 1.0 release, there will be two series of releases.
The releases named 1.0.×.y will only contain bug fixes (no new features). The idea is that the 1.0.×.y series of releases should always be the most stable release of Wings you can find.
Releases named 1.1.×.y will be development releases, where you will find the bleeding edge stuff. We will try to keep these releases as stable as possible, but since there is always the 1.0.×.y release to fall back on, we will probably be a little bit more daring than we had been in the past.
The next stable release, at some point in the future, will be called 1.2.
We use the following branches (inspired by the Git project).
The master branch only contains tested updates and the tip of the master
is supposed to be the most stable version of Wings. It will never be rewound (reset),
so you can safely base your own branches on it.
The maint branch contains corrections for latest stable release.
When the 1.0 release has been released, it will contain changes that are
to appear in the 1.0.1
The next branch contains stuff that we will release in the next 1.1.×.y release.
Anything that is merged onto this branch should be good enough to be released
(as a development release) and it should build and run on Mac OS X, Linux, and Windows.
The ‘next’ branch is stable enough to base development work against. At the time of stable
releases, though, I will probably rewind (reset) it to point to master branch.
I will try to send out a warning to all who has forked from this repository before resetting.
The branch (proposed updates) contains everything in next,
but also bleeding edge stuff that may not be ready or fully tested. You should generally
only use the pu branch for testing – never base any branches on it – as it
may be rewound quite often.
Topic branches are created for specific updates. The first part before the slash
(two-four characters) identifies the author (it usually but not always the
author’s initials). After the slash follows the topic description.
For instance, the branch bg/edge_array is my (Björn Gustavsson’s)
branch for using arrays instead of gb_trees for the edge table, and dgud/wxwidgets
is Dan Gudmundsson’s branch for migrating Wings to use WxWidgets
(instead of ESDL).
Topic branches may be rebased, so you should generally not base branches
on them. Topic branches will be deleted when they have been merged to the
master branch.