Hi Peter, We definitely need some release notes, and a separate (linked) formatted list of what is new since 4.0 would be very beneficial. I plan to write at least some of this information. Like you, my life is really busy right now with a work project.
One thing that a Release Manager can do is try to come up with a schedule. I hope that we can release 5.0 'soon', but I honestly do not know what will really happen. Thanks, and I hope that you are able to get some free time soon. Not for ctakes, but for your own self. Sean ________________________________ From: Peter Abramowitsch <pabramowit...@gmail.com> Sent: Wednesday, February 22, 2023 11:47 AM To: dev@ctakes.apache.org <dev@ctakes.apache.org> Subject: Re: It is Official! Steps toward a cTAKES 5.0 release. [EXTERNAL] * External Email - Caution * Hi Sean and all, If you expect the release process to last a couple of months, I can volunteer. At the moment and for the next few weeks I'm really busy. One thing that would really help is to have a list of all the major changes & additions that have happened since the 4.0.0 release. I think that would be valuable for everyone. I also have some additions to fold in, but without a good knowledge of what's been added/changed and why, it would not be safe to do that. For instance there's a project ctakes-pbj in the sources. Unless I've missed something, it's Readme doesn't have any explanation of what it actually is. And there are new annotators and functionality. Is there a comprehensive list? Probably it would be for each author to document their own additions, for accuracy and completeness. I will be doing that for sure. Peter On Wed, Feb 22, 2023 at 7:12 AM Finan, Sean <sean.fi...@childrens.harvard.edu.invalid> wrote: > Hi Gandhi, > > Thank you very much for volunteering! > > I am waiting to see if anybody else volunteers to be the RM, but I will > help anybody that volunteers for any position as much as I can. > > Cheers, > > Sean > ________________________________ > From: gandhi rajan <gandhiraja...@gmail.com> > Sent: Monday, February 20, 2023 11:06 PM > To: dev@ctakes.apache.org <dev@ctakes.apache.org> > Subject: Re: It is Official! Steps toward a cTAKES 5.0 release. [EXTERNAL] > > * External Email - Caution * > > > Hi Sean, > > I can volunteer for co-RM so that I can work under your guidance. Thanks. > > On Tue, 21 Feb 2023 at 03:43, Finan, Sean > <sean.fi...@childrens.harvard.edu.invalid> wrote: > > > 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 > > > > > > -- > Regards, > Gandhi > > "The best way to find urself is to lose urself in the service of others > !!!" >
