I would vote for a simple official release more than final versions
of all dependancies. Just make 2.0.0.86 an official release. I've
been using it for while now with no problems. When I go to
http://www.objectstyle.org/woproject
I want to see version 2.0 and be able to download it without any
trouble. Right now, it's difficult to find WOLips 2 and get it
installed but it works great.
Marc
On Jan 5, 2006, at 4:25 PM, Anjo Krank wrote:
> Hi,
>
> while I would be the first one to welcome a stable release without
> a ton of beta dependencies, I'd guess that this won't happen. It's
> just too much work to downgrade the new features to 3.1 and with a
> few of them, this is not even possible.
>
> So the best bet is to wait out for 3.2 final and WTP final and then
> try to make a stable version.
>
> Unless there is someone who volunteers to do all the backporting
> work...
>
> Cheers, Anjo
>
> Am 04.01.2006 um 23:52 schrieb mar..iffy-berlin.in-berlin.de:
>
>> Hi,
>>
>> Happy new year to everybody! I'm a longtime and happy user of
>> WOLips, and as I never participated in the project itself, I feel
>> not really in the position to complain, but still I would like to
>> voice my opinion on a couple of things.
>>
>> I see that there is a lot of interesting development going on.
>> Which is good. I like bug fixes, and I like the new features like
>> for example binding validation which is awesome. But I see no
>> effort whatsoever to make a new stable version.
>>
>> For me as a simple user, the current situation is quite
>> unsatisfactory. The last stable release (1.1.0.102 RC2) is
>> horribly outdated. The website doesn't even mention the 2.0
>> version, nor the wiki or the bugtracker. Whenever I want to find
>> the wiki, I google for it.
>>
>> It is very unclear which of all the 2.0 versions in the CVS is fit
>> for daily use (I'm using 2.0.86 at the moment). The requirements
>> for these versions are also unclear, and although there is
>> information in the wiki about this, it is outdated. From what I
>> understand, we need a patched Eclipse plugin, and a beta release
>> of Eclipse (3.2M4) now? For me that effectively means that I'm
>> stuck with the 2.0.86 now, as I cannot afford to upgrade to a beta
>> Eclipse release.
>>
>>
>> So what I would like to propose is to make a CVS branch of the
>> current (or a previous) version, and use that to make the next
>> stable release of Wolips.
>>
>> Stable for me means that:
>> - there is a defined set of features. These should preferably work
>> as advertised and not be under active developent. If that means to
>> take out parts which are under development, thats fine.
>> - there is a defined set of requirements. Especially no
>> requirements on beta or patched software. This would probably mean
>> Eclipse 3.1.1 and some of the plugins for wodclipse.
>>
>> Bugfixes would be made in the stable branch, while normal
>> development continues in the main trunk. There are tools to
>> automatically merge over the changes form the stable to the main
>> branch. When after some time (a couple of weeks?) the version in
>> the stable branch is stable enough to be released the stable
>> branch would then be declared dead and everything switches back to
>> the main trunk.
>>
>> What do you think about this? Comments, ideas?
>> Marc
>>
>
This archive was generated by hypermail 2.0.0 : Thu Jan 05 2006 - 17:27:03 EST