[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [stellation-res] Re: stellation-res digest, Vol 1 #414 - 1 msg
|
On Feb 20, 2004, at 12:51 PM, Xavier Méhaut wrote:
Hi everybody,
I've been following the mailing list since quite a long time now ;)
but I
don't see release update plan. The last version is quite old . When do
you
think :
* provide a new version of stellation
Probably about a week from now, we'll have an interim release. The
server code will be mostly the same, except for bugfixes; the Eclipse
plugin
will be dramatically different, and vastly improved over what was in
the last release.
The main reason why things have been so quiet is that we've been
hard at work on WVCM. Stellation is providing the reference
implementation for WVCM, and we've been working hard on learning the
semantics of WVCM, and figuring out how to change the system to support
it.
I checked in the first new component for the WVCM work this afternoon.
* and provide a MySQL compliant version ?
Unfortunately, never. The MySQL JDBC implementation is distributed
under the GPL, and IBMs legal staff will not allow us to distribute code
under the GPL, because they say that GPL and CPL are not compatible.
The MySQL folks had told us they were planning on changing the license
to make it more friendly; unfortunately, the changes they made are not
enough for us to be able to use it.
It's unfortunate, but that's the way these things go sometimes...
What is the timeframe of delivering a first production release?
The first "production" release of Stellation was last summer :-). We're
using it to manage our own code right now, and we've heard from a
couple of other folks who are using it. The main limiting factor at the
moment is that the command line code is a mess, and the Eclipse
client hasn't been ready for a production release.
The release next week will be a semi-production level release. The
command line code continues to be the same as it was (we're afraid to
touch it, and it needs to be completely rewritten for WVCM anyway, so
we're not taking any time to do anything except critical bug fixes on
it). The
Eclipse client will be usable, but the support for merge will be
very preliminary, and rather ugly.
Is there a plan to make Stellation the natural SCM tool for Eclipse?
Not yet. We're going to try to sell them on WVCM as the core of the
Team API; if that happens, then any WVCM provided will be the natural
tool for Eclipse; since we'll be the free reference implementation, I
would guess that
many Eclipse users will probably choose to use STellation as their WVCM
provider.
Do you need some "little harms" to help? If yes, in which kind of
domain?
regards
We would *love* some help. There are two main areas that we're focusing
on at the moment: implementing WVCM, and working on the Eclipse client.
We would love to have help on either one, and we could make suggestions
for nice starting points for digging into whichever one interests you.
The
Eclipse client work is mainly GUI work; the WVCM is mainly backend
and plumbing. If you let us know which kind of hacking appeals to
you more, we'll help you find something interesting to do.
-Mark
Xavier
----- Original Message -----
From: <stellation-res-request@xxxxxxxxxxx>
To: <stellation-res@xxxxxxxxxxx>
Sent: Friday, February 20, 2004 6:00 PM
Subject: stellation-res digest, Vol 1 #414 - 1 msg
Send stellation-res mailing list submissions to
stellation-res@xxxxxxxxxxx
To subscribe or unsubscribe via the World Wide Web, visit
http://dev.eclipse.org/mailman/listinfo/stellation-res
or, via email, send a message with subject or body 'help' to
stellation-res-request@xxxxxxxxxxx
You can reach the person managing the list at
stellation-res-admin@xxxxxxxxxxx
When replying, please edit your Subject line so it is more specific
than "Re: Contents of stellation-res digest..."
Today's Topics:
1. T-Client: Wiki Update, Merge plans. (Jim Wright - IBM Research)
--__--__--
Message: 1
Date: Thu, 19 Feb 2004 15:29:34 -0500
To: stellation-res@xxxxxxxxxxxxxxx
From: Jim Wright - IBM Research <jwright@xxxxxxxxxxxxxx>
Subject: [stellation-res] T-Client: Wiki Update, Merge plans.
Reply-To: stellation-res@xxxxxxxxxxx
I've updated Wiki pages related to the T-client and added a new
'T-Client
Status' page:
http://stellation.eclipse.org/twiki/bin/view/Stellation/TClientStatus
We are in the process of updating the binaries running the Stellation
project repository (stellation.eclipse.org) to incorporate a bugfix
and
ensure compatibility with the the current T-client code (and vice
versa).
Once this is done, the current T-Client code will be checked in for
other
committers to use. (A brief usage guide is included on the Wiki page
mentioned above; )
Mark and I are proposing that the initial T-Client merge capability be
similar to the current CLI merge capability. This means that, when
conflicts
are found, all versions of the conflicting section(s) will be
inserted in
place, with appropriate comment markers. I should also be able to
insert
Eclipse bookmarks to facilitate the manual merge reconciliation
process.
Once this basic merge functionality is supported by the T-Client, I'll
start
working on a GUI merge capability that leverages the new Eclipse R3
Compare/Sync/TeamSubscriber APIs.
Regards,
Jim
--
Jim Wright, IBM T.J. Watson Research Center
*** The Stellation project: Advanced SCM for Collaboration
*** http://www.eclipse.org/stellation
*** Work Email: jwright@xxxxxxxxxxxxxx ------- Personal Email:
jim.wright@xxxxxxx
s
--__--__--
_______________________________________________
stellation-res mailing list
stellation-res@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/stellation-res
End of stellation-res Digest
_______________________________________________
stellation-res mailing list
stellation-res@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/stellation-res
Mark Craig Chu-Carroll, IBM T.J. Watson Research Center
*** The Stellation project: Advanced SCM Research
*** http://stellation.eclipse.org
*** Work: mcc@xxxxxxxxxxxxxx/Home: markcc@xxxxxxx
