> I created a ticket to track this and I can probably take care of it next week
that makes sense, thank you. separately, code freeze is now lifted on tp33 - i've bumped to 3.3.5-SNAPSHOT, published initial docs/artifacts and all is good to go. I've left tp32 on 3.2.10 until we decide to actually do something on that branch. For now, we'll just say we're done there as we discussed elsethread. kuppitz, feel free to fire up the dead branch cleanup email. i wonder if it will be more convenient to delete branches as we go now that we have the github UI available to us. might be good to just hit the "delete branch" button right when we hit the merge one. i will announce the releases on monday morning EST time. On Fri, Oct 19, 2018 at 5:04 PM Florian Hockmann <[email protected]> wrote: > We currently use this to push the package: > > ${nugetExe} push Gremlin.Net/bin/Gremlin.Net.*.nupkg > > which pushes all NuGet packages starting with Gremlin.Net. You probably > also had the package for version 3.4.0-rc2 in that directory. So, > nuget.exe tried to push that version again which isn't allowed by NuGet > as packages are immutable for a given version. > > I guess we should specify the exact version here instead to avoid these > problems in the future. Otherwise we could push development versions to > nuget.org by accident. I probably implemented it like this at first > because I assumed that mvn clean would always remove older packages > which seems to be not the case here. > > Anyway, I created a ticket to track this and I can probably take care of > it next week: > > https://issues.apache.org/jira/browse/TINKERPOP-2074 > > > Am 19.10.2018 um 21:16 schrieb Stephen Mallette: > > Florian, any idea what's going on with this error when i deployed 3.3.4: > > > > main: > > [echo] nuget.exe already downloaded. > > [exec] Pushing Gremlin.Net.3.3.4.nupkg to ' > > https://www.nuget.org/api/v2/package'... > > [exec] PUT https://www.nuget.org/api/v2/package/ > > [exec] Created https://www.nuget.org/api/v2/package/ 1362ms > > [exec] Your package was pushed. > > [exec] Pushing Gremlin.Net.Template.3.3.4.nupkg to ' > > https://www.nuget.org/api/v2/package'... > > [exec] PUT https://www.nuget.org/api/v2/package/ > > [exec] Created https://www.nuget.org/api/v2/package/ 11405ms > > [exec] Your package was pushed. > > [exec] Pushing Gremlin.Net.Template.3.4.0-rc2.nupkg to ' > > https://www.nuget.org/api/v2/package'... > > [exec] PUT https://www.nuget.org/api/v2/package/ > > [exec] Conflict https://www.nuget.org/api/v2/package/ 365ms > > [exec] 409 (A package with ID 'Gremlin.Net.Template' and version > > '3.4.0-rc2' already exists and cannot be modified.) > > > > > > why is it trying to push the 3.4.0 line? looks like the error didn't > > matter as the other two published fine, but let's fix the error if we > > can........... > > > > On Fri, Oct 12, 2018 at 7:27 PM Stephen Mallette <[email protected]> > > wrote: > > > >> Robert Dale is without power so I pushed the 3.2.10-SNAPSHOT artifacts > and > >> docs too: > >> > >> http://tinkerpop.apache.org/docs/3.2.10-SNAPSHOT/ > >> > >> > >> > >> On Fri, Oct 12, 2018 at 8:22 AM Stephen Mallette <[email protected]> > >> wrote: > >> > >>> I just published final 3.3.4-SNAPSHOT artifacts and docs: > >>> > >>> http://tinkerpop.apache.org/docs/3.3.4-SNAPSHOT/ > >>> > >>> On Sun, Oct 7, 2018 at 8:33 AM Robert Dale <[email protected]> wrote: > >>> > >>>> I'll take 3.2.10. > >>>> > >>>> Robert Dale > >>>> > >>>> > >>>> On Fri, Oct 5, 2018 at 7:40 PM Stephen Mallette <[email protected] > > > >>>> wrote: > >>>> > >>>>> So - code freeze for the tp32 and tp33 branches is in effect at this > >>>> point. > >>>>> We'll use this thread to discuss issues related to 3.2.10 and 3.3.4 > >>>> leading > >>>>> up to the build of release artifacts for 10/15. We currently have a > >>>> few PRs > >>>>> that need merging to those branches, > >>>>> > >>>>> https://github.com/apache/tinkerpop/pull/952 (submit scripts with > >>>>> gremlin-javascript) > >>>>> https://github.com/apache/tinkerpop/pull/953 (minor fix for testing > >>>> around > >>>>> inject in .net) > >>>>> > >>>>> but they are related to GLVs so we shouldn't be affecting the ability > >>>> of > >>>>> graph providers to test against the core code. If those merge during > >>>> code > >>>>> freeze, I don't think that's too big a problem. > >>>>> > >>>>> Note that the master branch will remain open for development during > >>>> this > >>>>> time period. > >>>>> > >>>>> Anyone care to volunteer for release manager duties for either of > these > >>>>> releases? > >>>>> > >
