Re: dev Digest 20 Feb 2023 22:13:01 -0000 Issue 1432 [EXTERNAL]

["Finan, Sean" <Se...@childrens.harvard.edu.INVALID>]

Hi Alexis,

That is an excellent idea!

I know that some classes and engines commonly used in version 4 have been marked "deprecated", but hopefully there is full backward compatibility.  "Famous last words".  We should document these deprecations, reasons for deprecation and existing replacements.

Any problems that arise during testing that relate to incompatibility should definitely be documented - if not fixed.

Many thanks,

Sean

________________________________
From: Alexis Raykhel <ar...@iodinesoftware.com>
Sent: Tuesday, February 21, 2023 10:34 AM
To: dev-digest@ctakes.apache.org <de...@ctakes.apache.org>
Cc: dev@ctakes.apache.org <de...@ctakes.apache.org>
Subject: Re: dev Digest 20 Feb 2023 22:13:01 -0000 Issue 1432 [EXTERNAL]

* External Email - Caution *


Would it be possible to include instructions on upgrading from older
versions (4 and even earlier) with the next release? No, I'm not
volunteering, trust me :D
--


Alexis Raykhel

Senior NLP Engineer

She/Her
https://urldefense.com/v3/__http://www.iodinesoftware.com/__;!!NZvER7FxgEiBAiR_!sobi6JckN7vbEObff6ewFbCCp0xjxRpIgqvZEMfkTd9cpeCw41hG2gKVhrMcHfzt9gsya4PDA2aRfAZvBwl0YEl_uja-heDKB_8$


On Mon, Feb 20, 2023 at 4:13 PM <de...@ctakes.apache.org> wrote:

>
> dev Digest 20 Feb 2023 22:13:01 -0000 Issue 1432
>
> Topics (messages 6959 through 6959)
>
> It is Official!  Steps toward a cTAKES 5.0 release.
>         6959 by: Finan, Sean
>
> Administrivia:
>
> ---------------------------------------------------------------------
> To post to the list, e-mail: dev@ctakes.apache.org
> To unsubscribe, e-mail: dev-digest-unsubscribe@ctakes.apache.org
> For additional commands, e-mail: dev-digest-help@ctakes.apache.org
>
> ----------------------------------------------------------------------
>
>
>
>
> ---------- Forwarded message ----------
> From: "Finan, Sean" <Se...@childrens.harvard.edu.invalid>
> To: "dev@ctakes.apache.org" <de...@ctakes.apache.org>, "
> user@ctakes.apache.org" <us...@ctakes.apache.org>
> Cc:
> Bcc:
> Date: Mon, 20 Feb 2023 22:12:40 +0000
> Subject: It is Official!  Steps toward a cTAKES 5.0 release.
> Hi all,
>
> The cTAKES Project Management Committee has voted that it is time to
> officially begin the release process for cTAKES 5.0
>
> It has been almost 6 years since version 4.0.0 was released, and with a
> worldwide user count estimated in the thousands, a new release will be
> extremely valuable.
>
> Releasing cTAKES 5.0 will involve some work, and the project needs
> volunteers to assist in the process.
>
> The most important thing right now is the appointment of a Release Manager
> (RM).
> While the position is not to be taken lightly and does involve work, it
> can be a great experience (and a resume builder).
>
> We need a cTAKES committer to be the RM, but I am going to split the
> general responsibilities below.
> I am doing this because I believe that any user familiar with cTAKES can
> be a co-RM.
>
> Requiring a committer:
> 1.  Creating Release Candidates of the code.
> 2.  Deploying and Signing the actual Official Release.
>
> Not requiring a committer:
> 1.  Coordinating people performing documentation, testing and bug fixing.
> 2.  Communicating progress with the developer list.
>
> I am sure that I am forgetting something, but those are the 4 tasks that I
> can think of right now.
>
> If you would like to be the Release Manager (or a co-RM), please volunteer
> on the dev@ctakes.apache.org mailing list.
>
> Other tasks that must be performed for a release include:
> 1.  Testing the release candidates.
> 3.  Contributing documentation.
> 2.  Writing fixes for bugs that can be fixed for the release.
> 4.  Updating the release information on ctakes.apache.org
>
> Anybody can test release candidates.  There are countless pipelines that
> can be built and tested, but I think that we should try to cover the 'most
> commonly used' pipelines.  If you run any pipeline, please report success -
> even if you don't run it specifically for release testing.
> Documentation can be contributed by any user.  A cTAKES committer is
> required to actually push the documentation to the wiki, readme, release
> notes, etc. Sending out markdown, images, plain text or just
> recommendations is open to all users.
> While only committers can actually push changes to cTAKES code, any user
> can contribute fixes by creating code patches or even just copy-pasting
> code in an email.
> Updating the ctakes.apache.org website will require a committer, but
> non-committer assistance is possible just like it is for bug fixes.
>
> One person (Tim Miller) has already volunteered to perform testing and
> another (Dennis Johns) is currently working on the GitHub wiki.
> I don't think that people need to officially volunteer to perform last 4
> listed tasks, but it may be beneficial to identify areas that you would
> like to cover in order to prevent duplicated work.
>
> I suspect that I am forgetting at least some minor items, but they will
> come to light when encountered.
>
> I urge you all to take part in the release process.  You can earn good
> karma, become famous as a cTAKES power user, and perhaps be nominated as a
> Committer!
>
> Thank you all,
>
> Sean
>
>

--



This electronic transmission (and any attached document) is for the sole
use of the individual or entity to whom it is addressed. It is confidential
and may contain personal health information. Any further distribution or
copying of this message is strictly prohibited. If you receive this message
in error, please notify me and destroy the attached message (and all
attached documents) immediately.