I'm good with cut a release and iterate on testing that. On Fri, Feb 25, 2022 at 11:03 AM Adam Rosien <[email protected]> wrote:
> I think it's better to cut a release and iterate on that testing-wise. > > On Wed, Feb 23, 2022 at 7:24 AM Mike Beckerle <[email protected]> > wrote: > >> I have not had time to test the vscode debugger recently. >> >> We could hold off doing that, or I could do that as part of the rc1 >> evaluation process if you prefer before we vote on accepting it. >> >> >> >> On Tue, Feb 22, 2022 at 3:06 PM John Wass <[email protected]> wrote: >> >> > All issues are resolved. If we are good to proceed I would nominate >> Shane >> > Dell to be the release manager. >> > >> > On Thu, Feb 17, 2022, 10:38 John Wass <[email protected]> wrote: >> > >> > > > #81 yarn disallows SVG's in the README >> > > > #82 yarn build fails with missing icon >> > > > #83 Rename vsix convenience binary? >> > > >> > > Agree, added those to the 1.0.0 milestone. >> > > >> > > >> > > >> > > On Thu, Feb 17, 2022 at 10:27 AM Steve Lawrence <[email protected] >> > >> > > wrote: >> > > >> > >> I believe these two issues prevent building the .vsix file and should >> > >> probably be fixed--being able to build a .vsix file seems critical >> for a >> > >> release: >> > >> >> > >> #81 yarn disallows SVG's in the README >> > >> >> > >> https://github.com/apache/daffodil-vscode/issues/81 >> > >> >> > >> #82 yarn build fails with missing icon >> > >> >> > >> https://github.com/apache/daffodil-vscode/issues/82 >> > >> >> > >> I'd also suggest we might to resolve #83. It's not as critical to me >> as >> > >> the other two, but it seems like a good idea to get a consensus on >> the >> > >> best name for the convenience binary so that future releases are >> > >> consistent. >> > >> >> > >> #83 Rename vsix convenience binary? >> > >> >> > >> https://github.com/apache/daffodil-vscode/issues/83 >> > >> >> > >> >> > >> >> > >> On 2/17/22 10:06 AM, John Wass wrote: >> > >> > I'd like to discuss starting the first official release of the >> > Daffodil >> > >> VS >> > >> > Code extension. >> > >> > >> > >> > All items in the 1.0.0 GitHub milestone have been closed (aside >> from >> > one >> > >> > about performing the release). Are there any issues remaining on >> the >> > >> > tracker that should be considered required, or any other blockers >> to >> > >> > getting a 1.0.0 RC out there? >> > >> > >> > >> > https://github.com/apache/daffodil-vscode/issues >> > >> > https://github.com/apache/daffodil-vscode/milestone/1 >> > >> > >> > >> >> > >> >> > >> >
