I'd like to request more time for this vote.

I have only limited time today to check this release out, and limited
connectivity today as I am on Amtrak with spotty wifi at best.

I don't want to vote yet, because something seemingly environmental is
impeding my ability to evaluate.

Obviously this works for others or it wouldn't be an RC, but I am *not
getting it to even start working*.  I will need some assistance to get past
this.

I have uninstalled VSCode, setup to use Java 11. I have rebooted my PC
(ubuntu). I have fully deleted ~/.vscode, and then I have reinstalled
vscode.
Then I install the release VSIX, and still, I can get nowhere.

No Daffodil command from the command palette does anything other than give
an error.

If I choose Daffodil Debug File from the command palette, I'm immediately
getting "ENOENT: no such file or directory, lstat".

I tried also to select Daffodil Debugger, configure launch.json but I get:

[image: image.png]
(btw: what is 'launch.config'? Shouldn't that say 'launch.json'?)

So something is up environmentally; I can't even test out the features yet.

-mike beckerle





On Wed, Jul 27, 2022 at 2:21 PM Shane Dell <[email protected]> wrote:

> Hello all,I'd like to call a vote to release Apache Daffodil VS Code
> 1.1.0-rc1.
>
> All distribution packages, including signatures, digests, etc. can be
> found at:
> https://dist.apache.org/repos/dist/dev/daffodil/daffodil-vscode/1.1.0-rc1/
>
> This release has been signed with PGP key
> 86DDE7B41291E380237934F007570D3ADC76D51B, corresponding
> to [email protected], which is included in the KEYS file here:
> https://downloads.apache.org/daffodil/KEYS
>
> The release candidate has been tagged in git with 1.1.0-rc1.
>
> For reference, here is a list of all closed GitHub issues tagged with
> 1.1.0:
> https://github.com/apache/daffodil-vscode/milestone/2?closed=1
>
> Please review and vote. The vote will be open for at least 72 hours
> (Saturday, 30 July 2022, 3 Noon EST).
>
> [ ] +1 approve
> [ ] +0 no opinion
> [ ] -1 disapprove (and reason why)
>
> Thank you,
>
> - Shane Dell
>

Reply via email to