I realize I’m not a committer and maybe I shouldn’t express an opinion. Apologies in advance if this is inappropriate. However as someone who has gone through the pain of trying to install, learn, and use ctakes; I strongly agree with Sean. I don’t inject myself into the situation lightly or to “vent”. I have been in software development since 1996 and a lot of that time in medical projects and using various open source frameworks like Spring, Seam, Hibernate, etc. Sean is right.
Jeff On Dec 6, 2016, 10:00 AM -0500, Pei Chen <pei.c...@wiredinformatics.com>, wrote: > Considering the amount of time since the release was created, we should not > let any pending Jira’s or features hold up a release. > I suggest just we mark anything that hasn’t been fixed in Jira into the next > release and push forward- I’ll volunteer to do that right now. > In the past, the documentation on the website also shouldn’t hold up a > release either. > > > On Dec 6, 2016, at 9:20 AM, Finan, Sean <sean.fi...@childrens.harvard.edu> > > wrote: > > > > Hi Murali, > > > > Before we make an rc, we must go through the list of currently open tars > > and requests. SOP. A list needs to be compiled of what should be closed as > > fixed or n/a plus another list of outstanding bugs that need to be dealt > > with and an estimate of effort. Then we should try to gather volunteers to > > handle said bugs. Can you take care of compiling those lists? I did this > > many months ago when rc 3.2.3 came up, and there were items on which no > > movement was made. If you can find my email that might be one place to > > start. > > > > The primary takeaways from the hackathon were, not surprisingly: > > 1. Installation of cTAKES is not as straightforward as we believe, and > > 2. Getting started with cTAKES is extremely difficult (no good starting > > point) and scares off a large percentage of people who try. > > 3. Customization is next to impossible without diving into the code, which > > is more time consuming than anyone can stand. > > > > All can be handled best by short and simple GUI tools and some "cTAKES for > > Beginners" documentation. We have some documentation that was used for the > > Hackathon that needs to be modified a bit, then posted on the main cTAKES > > website. > > > > In my opinion these items should be worked upon before creating another > > release, otherwise the release is not as useful as it could be. I have > > started work on a simple pipeline builder gui that creates simple html or > > text output. I will check it into trunk soon, but as new functionality > > community testing will be required before a release. > > > > Sean > > > > -----Original Message----- > > From: Murali Minnah [mailto:mmin...@gmail.com] > > Sent: Monday, December 05, 2016 1:26 PM > > To: dev@ctakes.apache.org > > Subject: cTAKES - 3.2.3 release > > > > I wanted to check to see if there are objections to creating a 3.2.3 tag of > > trunk now to prepare for a 3.2.3-rc1? > > > > Any comments from the participants/organizers on the success/lessons learnt > > from the "hackathon" that the community can benefit from? > > > > Best, > > Murali >
