Hello, It's been a few days since we discussed the possible release of Apache Taverna Language incubator. Since then we have corrected many build issues and identified areas where documentation (NOTICE, LICENSE and README) can be improved. I don't think that any of the documentation issues are enough to stop us going ahead with the release and the fact that we identified build issues and corrected them shows that the release process is working. I believe that we should go ahead with the release while adding the documentation issues to JIRA so that we can fix them when we have time to do so.
Cheers, Ian -----Original Message----- From: Andy Seaborne [mailto:[email protected]] Sent: 25 June 2015 22:46 To: [email protected] Subject: Re: [VOTE] Release Apache Taverna Language 0.15.0-incubating RC2 On 24/06/15 13:45, Ian Dunlop wrote: > Hello, > > I have removed the hardcoded junit, commons-io and airlift versions from the > projects I mentioned yesterday and merged a pull request (which I generated!). > > This raises a question about what is best practice if you are already a > committer. I don't really want to push straight to master since I would > always like someone to give my changes a quick look. This is why I forked the > github repos and raised the pull requests. Is this sensible or should I > change master or create a new branch or........what is the 'apache' way to do > things. > You, the Taverna community, get to decide. Andy > Cheers, > > Ian >
