On 2/18/07, David Chisnall <[EMAIL PROTECTED]> wrote:
On 17 Feb 2007, at 16:37, Yen-Ju Chen wrote:
> A summary so far is:
>
> 1. -trunk: developers' playground
> 2. -stable: 'works for me' version, targeting GNUstep svn, target of
> bug reports.
> 3. -release: 'works for everyone' version, targeting GNUstep stable.
I have written this up here:
http://www.etoile-project.org/etoile/mediawiki/index.php?title=Status
Please will everyone who contributed to this discussion check this
page and make sure that this reflects the opinion of the whole group,
and not just me.
I agree your point.
I also put all the summary at the bottom of this email
so that people can still review and comment on it.
Here come the Frameworks:
AddressesKit: go stable. little changes since imported.
PaneKit: go stable
BookmarkKit: go stable
CollectionKit: go stable
RSSKit: go stable, used by Grr.
PopplerKit: go stable, little changed since imported, used by Vindaloo
UnitKit: go stable, no major problem, used by many frameworks.
OgreKit: go stable, used by LuceneKit.
XWindowServerKit: go stable, used by some system applications.
OPMLKit: go stable ? used by Grr
EtoileFoundation: go stable ?
EtoileUI: go stable ?
SystemConfig: not sure, used by Hardware.app.
ExtendedWorkspaceKit: not sure
IconKit: not sure
DistributedView: not sure
EtoileThread: not sure
ServicesBarKit: not sure
LuceneKit: not going, not updated for a while, not used by any application
MultimediaKit: not going, too experimental, backend is not finalized yet.
=====================
Etoile SVN repositories:
-trunk: for developers, continual development of a project,
can be unstable stuff, as alpha release or propo-type,
major improvement and reorganization.
-stable: for users, usable to some extent, as beta release, target for
bug reports,
sync with GNUstep trunk, "work-for-me" and ready to be
tested by others,
frameworks better to have unit test so it can be tested
easier by others.
-release: just a tag of -stable once for a while, sync with GNUstep
stable release,
work for most people and platforms.
When a project in trunk reaches certain stability, it can be copied to stable
to be tested by others. The main development still stay in trunk. Therefore,
developers don't need to take care of two code bases. If there are bug reports
for projects in stable, developers can either patch it in stable or copy a newer
version of project from trunk to stable if code in trunk is qualified.
Since projects
in stable are mostly bug-fixed, it can be tagged as release once for a while.
But reports are still targeted for stable, at least for Etoile 0.x release.
For developers who always make sure the code is in a good shape,
the code in trunk and stable can be almost in sync.
For people who want to try out Etoile, ask them to use stable, not trunk.
Ready to be put in stable:
Bundles/Camaelon
Bundles/EtoileBehavior
Bundles/EtoileWildMenus
Languages/Io
Yen-Ju
_______________________________________________
Etoile-dev mailing list
[email protected]
https://mail.gna.org/listinfo/etoile-dev
_______________________________________________
Etoile-dev mailing list
[email protected]
https://mail.gna.org/listinfo/etoile-dev
