Yes, I'm suggesting we capture the .asf.yml file and lay that on after we force push the branch "as is".
Then we update the LICENCE and NOTICES as needed for a release. On Wed, Oct 6, 2021 at 11:14 AM Steve Lawrence <slawre...@apache.org> wrote: > Just want to clarify that you are suggesting we force push and overwrite > the current main branch with the IP clearance main branch? This seems > fine to me, but we do need to make sure add back the .asf.yml file. This > can be done as the first PR. > > I'm also not sure we need to tag it. I usually prefer tags for just > releases. If there are ever any concerns about the IP clearance, we can > always refer to the IP clearance documentation, which lists the git > commit hash. Since we are force pushing, the main branch will have the > same commit hash. > > We'll also need to update the LICENSE/NOTICE files prior to release. > There are a lot of npm dependencies that we have verified are compatible > with ALv2, but we still need to document them in the license file of any > convenience binaries. > > Are there even convenience binaries? What is actually published to the > market place? > > As far as the release process, it will be very simialr to the Daffodil > repo. We'll have to do the normal vote, which will be for the source > and convenience binaries. Once that vote passes, we can publish the > convenience binaries to the VSCode marketplace. We might need to work > with Apache Infra if there's an "ASF" thing to publish under. > > We might want a Release Workflow page dedicated to the vscode repo. > > > On 10/6/21 10:40 AM, Mike Beckerle wrote: > > With the IP-clearance now complete, next steps (I think) are: > > > > 1) push to https://github.com/apache/daffodil-vscode repository. > > I believe the existing repo main branch should be pushed here as is, > i.e., > > no need to squash anything. > > Note the main branch is named "main", not master. > > Tag it at the current point on the main branch. (suggest tag name > > apache-ip-clearance ? or happy-apache-birthday ?) > > 2) move over github issues to the new repo issues > > 3) move wiki pages/doc to the github wiki associated with the new > repository > > 4) archive the old original github repo (for posterity). > > 5) update main daffodil-site pages to mention/highlight the new vscode > > debugger and link to its issues and wiki. > > 6) whatever else I forgot > > > > and.... > > > > 7) start planning for release 1.0.0. > > > > I am not sure what additional things are needed in order to meet Apache > > criteria for release, given the vscode marketplace as a means of > > distribution. Perhaps we don't need to solve that yet? > > > > I think we covered almost everything else during the IP-clearance > process. > > > > If there are things, let's discuss them here on the dev list. > > > >
