[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [open-cobol-list] next release
From: |
Keisuke Nishida |
Subject: |
Re: [open-cobol-list] next release |
Date: |
Wed Feb 25 05:12:06 2004 |
User-agent: |
Wanderlust/2.10.0 (Venus) SEMI/1.14.3 (Ushinoya) FLIM/1.14.3 (UnebigoryĆmae) APEL/10.3 Emacs/21.2 (i386-redhat-linux-gnu) MULE/5.0 (SAKAKI) |
At Mon, 23 Feb 2004 18:29:37 +0100,
Thomas Biehler wrote:
>
> - which features are (new) implemented ?
> run the test-scripts with "-l" should give some hints,
> but are there always testscripts for new features ?
> I don't think so. --> a good goal for the future!
Part of the new features and user visible changes are listed
in the file "NEWS". Not all changes are covered, though.
> - Make a "unimplemented_feature.at" and "in_work_feature.at"
> for new (= requested) or in_working features in the tests-directory.
> (which then are always failing!)
> Then the step, descriped above, would much more help.
> (IMO: the both scripts would not run with "make check"!
> a new make target or explicit, manuelly start would be ok!),
> If the feature is (good enough) implemented,
> the used autotests could be moved into other test-scripts!
Good idea. Actually, I have some in my personal directory.
I'll add them in CVS.
> I was saying, a release strategy is TODO.
> Do you agree with me, now ? :-)
Yeah, I do not have a strong opinion about this actually.
I make a new release when people want it.
I will review the manual in a few days, update out-of-date
descriptions, and release 0.30 soon. Let's think about a
better documentation/release strategy after that.
Keisuke