There are a couple of potential issues with this: 1) The sbt build infrastructure currently depends on branches and tags named a certain way. The new branch/tag guidelines break that. Pull request #3 [1] fixes this and adds "Apache" and "incubating" where appropriate. This needs an additional +1 before it can be pushed, and it could be cherry-picked to the v2.0.x support branch, allowing us to create a release.
2) We still do not have SGAs from NCSA and IBM (NCSA is very close), and so we can not relicense the code base. As I understand it, we cannot do an Apache release until we get the SGA's signed and code relicensed. This will likely take some time, especially since we have not done an official Apache release, and there's much more involved in a release than just tagging the repo as we've done in the past. I would say the best solution would be to just create a private copy of the repo for the LWAP project and tag it using old style tag names (e.g. 2.0.0-lwap-hotfix-1) which can be provided to LWAP, making it clear it is not an official Apache release. Once we get the SGAs in place, we can start the process towards a release and get the LWAP project to start following that. [1] https://github.com/apache/incubator-daffodil/pull/3 On 11/22/2017 01:46 PM, Mike Beckerle wrote: > Forgot to send to the dev list. > > > ________________________________ > From: Mike Beckerle > Sent: Wednesday, November 22, 2017 1:30 PM > To: Stephen Lawrence; Taylor Wise; Joshua Adams; Dave Thompson > Subject: LWAP project needs a fix to v2.0.0 > > > So in building some DFDL shcemas for LWAP I found a bug that need to be > fixed. It basically is blocking progress. > > > I created a pull request for merge onto the support/v2.0.x branch. > > > If this is acceptable, then the issue arises of how we create a point > release, which we haven't done as yet. > > > Would this release be called 2.0.1 ? being a tag on the support/v2.0.x branch? >
