Re: [VOTE] Release Apache Daffodil (Incubating) 2.1.0-rc1

Multiple issues have been found with this release, so I am officially canceling this vote. We would still ask for continued review of the 2.1.0-rc1 release so that any issues found can be fixed in the 2.1.0-rc2 release. Thanks, - Steve On 02/08/2018 11:30 AM, Steve Lawrence wrote: > Hi all, > >

Re: [VOTE] Release Apache Daffodil (Incubating) 2.1.0-rc1

I'll spend some time reviewing it, but right now my vote is a -1 due to the package naming. Ideally, each package is "apache-daffodil-2.1.0-incubating" and this package name should be used on all components. John On Thu, Feb 8, 2018 at 11:30 AM Steve Lawrence wrote: > Hi

Re: [VOTE] Release Apache Daffodil (Incubating) 2.1.0-rc1

We'll definitely hold off for further feedback. Naming logic makes sense to me. As far as binary files in /dist/dev go, my preference (not a strong preference) would be to have the zip/tar/rpm as part of the reviewable materials just so we can catch any errors with those as early as possible,

[jira] [Created] (DAFFODIL-1897) Some Schemas fail to compile with latest updates (v2.1.0-rc1)

Dave Thompson created DAFFODIL-1897: --- Summary: Some Schemas fail to compile with latest updates (v2.1.0-rc1) Key: DAFFODIL-1897 URL: https://issues.apache.org/jira/browse/DAFFODIL-1897 Project:

[jira] [Commented] (DAFFODIL-1897) Some Schemas fail to compile with latest updates (v2.1.0-rc1)

[ https://issues.apache.org/jira/browse/DAFFODIL-1897?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16357307#comment-16357307 ] Steve Lawrence commented on DAFFODIL-1897: -- It is still possible for someone to create at NCSA

[jira] [Updated] (DAFFODIL-1895) Eclipse classpath for daffodil-core needs fix

[ https://issues.apache.org/jira/browse/DAFFODIL-1895?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Lawrence updated DAFFODIL-1895: - Fix Version/s: (was: 2.1.0) 2.2.0 > Eclipse classpath for

[jira] [Updated] (DAFFODIL-1886) Delimited parsing with occursCountKind="implicit" with separators is not handling missing optional elements correctly

[ https://issues.apache.org/jira/browse/DAFFODIL-1886?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Lawrence updated DAFFODIL-1886: - Fix Version/s: (was: 2.0.0) 2.2.0 > Delimited parsing with

[jira] [Updated] (DAFFODIL-1882) Implement support for the various formats of binaryCalendarRep

[ https://issues.apache.org/jira/browse/DAFFODIL-1882?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Lawrence updated DAFFODIL-1882: - Fix Version/s: 2.0.0 > Implement support for the various formats of binaryCalendarRep

[jira] [Created] (DAFFODIL-1898) TDML Runner not assembling mixtures of BE+MSBF and LE+LSBF test data properly.

Michael Beckerle created DAFFODIL-1898: -- Summary: TDML Runner not assembling mixtures of BE+MSBF and LE+LSBF test data properly. Key: DAFFODIL-1898 URL: https://issues.apache.org/jira/browse/DAFFODIL-1898

[jira] [Assigned] (DAFFODIL-1896) Modify artifact names to include "apache" and "incubating"

[ https://issues.apache.org/jira/browse/DAFFODIL-1896?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Lawrence reassigned DAFFODIL-1896: Assignee: Steve Lawrence > Modify artifact names to include "apache" and

[GitHub] mbeckerle opened a new pull request #37: Fix bitOrder bug detected by Link16 schema.

mbeckerle opened a new pull request #37: Fix bitOrder bug detected by Link16 schema. URL: https://github.com/apache/incubator-daffodil/pull/37 Issue was that alignmentFill wasn't able to provide bit alignment. (It was checking for bit-order transitions being proper before doing

[jira] [Commented] (DAFFODIL-1897) Some Schemas fail to compile with latest updates (v2.1.0-rc1)

[ https://issues.apache.org/jira/browse/DAFFODIL-1897?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16357497#comment-16357497 ] Michael Beckerle commented on DAFFODIL-1897: I think moving the built-in-formats is going

[jira] [Commented] (DAFFODIL-1897) Some Schemas fail to compile with latest updates (v2.1.0-rc1)

[ https://issues.apache.org/jira/browse/DAFFODIL-1897?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16357651#comment-16357651 ] Michael Beckerle commented on DAFFODIL-1897: I have been able to get DFDLSchemas minus NITF

[jira] [Updated] (DAFFODIL-1886) Delimited parsing with occursCountKind="implicit" with separators is not handling missing optional elements correctly

[ https://issues.apache.org/jira/browse/DAFFODIL-1886?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Lawrence updated DAFFODIL-1886: - Fix Version/s: 2.0.0 > Delimited parsing with occursCountKind="implicit" with

[GitHub] stevedlawrence commented on issue #36: Change names of zip/tar/rpm binary artifacts

stevedlawrence commented on issue #36: Change names of zip/tar/rpm binary artifacts URL: https://github.com/apache/incubator-daffodil/pull/36#issuecomment-364222715 Note, this is for DAFFODIL-1896. Need to fixup commit message.

[jira] [Commented] (DAFFODIL-1897) Some Schemas fail to compile with latest updates (v2.1.0-rc1)

[ https://issues.apache.org/jira/browse/DAFFODIL-1897?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16357635#comment-16357635 ] Steve Lawrence commented on DAFFODIL-1897: -- Ah, ignore the above comment. Didn't reload the

[jira] [Commented] (DAFFODIL-1897) Some Schemas fail to compile with latest updates (v2.1.0-rc1)

[ https://issues.apache.org/jira/browse/DAFFODIL-1897?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16357674#comment-16357674 ] Michael Beckerle commented on DAFFODIL-1897: Furthermore, these work under eclipse, where

[jira] [Resolved] (DAFFODIL-1881) Prepare 2.1.0 release

[ https://issues.apache.org/jira/browse/DAFFODIL-1881?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Lawrence resolved DAFFODIL-1881. -- Resolution: Fixed Assignee: Dave Thompson (was: Steve Lawrence) Fixed in

[jira] [Closed] (DAFFODIL-1866) Eclipse classpaths need fixing

[ https://issues.apache.org/jira/browse/DAFFODIL-1866?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dave Thompson closed DAFFODIL-1866. --- Pulled latest updates from incubator-daffodil repository which included the specified commit,

[GitHub] stevedlawrence closed pull request #31: Prepare for 2.1.0 release

stevedlawrence closed pull request #31: Prepare for 2.1.0 release URL: https://github.com/apache/incubator-daffodil/pull/31 This is a PR merged from a forked repository. As GitHub hides the original diff on merge, it is displayed below for the sake of provenance: As this is a foreign

[jira] [Closed] (DAFFODIL-1872) Eclipse classpaths for daffodil-io module need fixing

[ https://issues.apache.org/jira/browse/DAFFODIL-1872?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dave Thompson closed DAFFODIL-1872. --- Pulled latest updates from incubator-daffodil repository which included the associated

[jira] [Resolved] (DAFFODIL-1859) Switch to apache.org namespace and Apache v2 license

[ https://issues.apache.org/jira/browse/DAFFODIL-1859?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Lawrence resolved DAFFODIL-1859. -- Resolution: Fixed Assignee: Dave Thompson (was: Steve Lawrence) Fixed in a

[jira] [Updated] (DAFFODIL-1881) Prepare 2.1.0 release

[ https://issues.apache.org/jira/browse/DAFFODIL-1881?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Lawrence updated DAFFODIL-1881: - Component/s: Infrastructure > Prepare 2.1.0 release > - > >

Re: tag for last NCSA-based commit?

I'm not sure a tag would add a whole lot of value, and would add a little bit of clutter. I don't think splitting a rebase into two will help very much (and if it is, the commit of interest just a few commits before the soon to be created 2.1.0-rc1 tag). The hard part is knowing how to deal with

tag for last NCSA-based commit?

I believe this: 945a1c1ab363485003ebf14fef3463055d4fab37 Is the last commit using the old file structure, old packages, etc. I suspect it would be prudent to make a tag for this. This would be in case some developer has lots of outstanding changes based on earlier commits. They could first

Re: tag for last NCSA-based commit?

I have about 5 development branches that I've rebased yesterday onto the last edu.illnois.ncsa commit. I will try to rebase them onto the current master and let you know the outcome. If this goes smoothly, then yeah I would agree with you. From: Steve Lawrence

[jira] [Created] (DAFFODIL-1895) Eclipse classpath for daffodil-core needs fix

Michael Beckerle created DAFFODIL-1895: -- Summary: Eclipse classpath for daffodil-core needs fix Key: DAFFODIL-1895 URL: https://issues.apache.org/jira/browse/DAFFODIL-1895 Project: Daffodil

[jira] [Commented] (DAFFODIL-1895) Eclipse classpath for daffodil-core needs fix

[ https://issues.apache.org/jira/browse/DAFFODIL-1895?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16357033#comment-16357033 ] Michael Beckerle commented on DAFFODIL-1895: PR