wow - 3.2.2 was really messy for some reason - just noticed that upgrade
docs don't mention gremlin-python at all...............how did that get by?!

On Mon, Sep 12, 2016 at 6:24 AM, Stephen Mallette <spmalle...@gmail.com>
wrote:

> totally flubbed the first release to pypi. i realized that i didn't have
> license/notice in the pypi distributions after i deployed 3.2.2. i decided
> to add them, delete the old distribution and then re-upload. i didn't
> realize that deleting the release from pypi deletes the files but the name,
> 3.2.2, stays forever and it won't let me upload a new one even though i can
> delete it................python ecosystem is so weird. maybe i should have
> checked for the latest docs on sourceforge first :/
>
> soooooo - i ended up deploying it as "3.2.2rc1" which i guess fits what we
> were saying anyway with this first release of gremlin-python in that it is
> somewhat experimental. Anyway - it's up there:
>
> https://pypi.python.org/pypi?:action=display&name=gremlinpyt
> hon&version=3.2.2rc1
>
> on top of that, my maven integration didn't work so well. not that it
> wouldn't have worked, but i have it setup right now that it would have
> re-deployed the java artifacts to sonatype if i'd have used the maven
> toolchain......that's no good. i'll have to figure out how to decouple
> that. it's too bad pypi doesn't have a staging system for artifacts like
> sonatype does - that would solve the problem.
>
> 3.2.2 java artifacts have been released on sonatype and the apache mirrors
> have the release available at this point. i'll send the release email as
> soon as ted sends his so that we can release in order. TinkerPop home page
> has already been updated to reflect the releases.
>
> I've merged tp31 to master and bumped master to 3.2.3-SNAPSHOT. I've also
> published a fresh snapshot for that version and docs. And with that, master
> is open for 3.2.3 development. I'll create the tp32 branch later today and
> send a separate email when our git workflow changes once that happens.
>
>
>
>
>
> On Tue, Sep 6, 2016 at 4:24 PM, Stephen Mallette <spmalle...@gmail.com>
> wrote:
>
>> Oh - a quick note to those voting who use validate-distribution.sh. Ted
>> just added his gpg stuff to the KEYS file:
>>
>> https://dist.apache.org/repos/dist/dev/tinkerpop/KEYS
>>
>> You will need to import his key with:
>>
>> $ gpg --import KEYS
>>
>> if you don't validate-distribution.sh won't be happy and you will get:
>>
>> $ bin/validate-distribution.sh 3.1.4
>>
>> Validating binary distributions
>>
>> * downloading Apache TinkerPop Gremlin 
>> (apache-tinkerpop-gremlin-console-3.1.4-bin.zip)...
>> OK
>> * validating signatures and checksums ...
>>   * PGP signature ... failed
>>
>>
>>
>> On Tue, Sep 6, 2016 at 4:12 PM, Stephen Mallette <spmalle...@gmail.com>
>> wrote:
>>
>>> Looks like the plan to split the release manager duties between
>>> 3.1.4/3.2.2 was a success. It required very little communication aside from
>>> a few messages in HipChat. I actually found it easier to do this way
>>> because I felt focused on just the release i was working on - in the
>>> drudgery of release my mind would lapse sometimes and I'd make some dumb
>>> mistakes. Anyway, I've setup JIRA for our next releases of 3.1.5 (!) and
>>> 3.2.3. Haven't bumped the repos back to SNAPSHOT yet so please keep work in
>>> branches until that happens.
>>>
>>> Note that there are no artifacts for gremlin-python in pypi yet as they
>>> don't have a staging system like sonatype. I'll publicly have to release
>>> those after we VOTE.
>>>
>>> Thanks to Ted for doing the 3.1.4 release - much appreciated.
>>>
>>>
>>>
>>> On Tue, Sep 6, 2016 at 7:04 AM, Stephen Mallette <spmalle...@gmail.com>
>>> wrote:
>>>
>>>> I've started working on release stuff, though it occurred to me that
>>>> I'm dependent on Ted completing certain aspects of his 3.1.4 release so
>>>> that tp31 can merge to master with all the "release" updates. Anyway, I'll
>>>> go as far as I can then wait for word from Ted on 3.1.4.
>>>>
>>>> On Fri, Sep 2, 2016 at 11:44 AM, Stephen Mallette <spmalle...@gmail.com
>>>> > wrote:
>>>>
>>>>> Ted, fixed up some javadoc on tp31 branch - meant to do it earlier in
>>>>> the week (but forgot unfortunately):
>>>>>
>>>>> https://issues.apache.org/jira/browse/TINKERPOP-1418
>>>>>
>>>>> Updated CHANGELOG with the JIRA issue. Anyway, everything is looking
>>>>> pretty good for release next week.
>>>>>
>>>>> On Thu, Sep 1, 2016 at 6:21 PM, Stephen Mallette <spmalle...@gmail.com
>>>>> > wrote:
>>>>>
>>>>>> Just published what I believe is the final 3.2.2-SNAPSHOT docs prior
>>>>>> to VOTE.
>>>>>>
>>>>>> http://tinkerpop.apache.org/docs/3.2.2-SNAPSHOT/
>>>>>>
>>>>>> On Thu, Sep 1, 2016 at 3:38 PM, Ted Wilmes <twil...@gmail.com> wrote:
>>>>>>
>>>>>>> Cool, thanks for the update.  I had not merged tp31 back into master
>>>>>>> after
>>>>>>> my changelog updates so thanks for taking care of that.
>>>>>>>
>>>>>>> --Ted
>>>>>>>
>>>>>>> On Thu, Sep 1, 2016 at 12:54 PM, Stephen Mallette <
>>>>>>> spmalle...@gmail.com>
>>>>>>> wrote:
>>>>>>>
>>>>>>> > Ted, I noticed some formatting problems in the headers for
>>>>>>> asciidoc on the
>>>>>>> > tp31 branch. I corrected those. I don't think you need to
>>>>>>> republish the
>>>>>>> > SNAPSHOT docs over that minor change. Obviously, we'd get the
>>>>>>> fixes in the
>>>>>>> > official release.  I also implemented this on tp31:
>>>>>>> >
>>>>>>> > https://issues.apache.org/jira/browse/TINKERPOP-1416
>>>>>>> >
>>>>>>> > I updated CHANGELOG manually since you already generated that
>>>>>>> stuff.
>>>>>>> >
>>>>>>> >
>>>>>>> >
>>>>>>> > On Wed, Aug 31, 2016 at 3:00 PM, Ted Wilmes <twil...@gmail.com>
>>>>>>> wrote:
>>>>>>> >
>>>>>>> > > The 3.1.4-SNAPSHOT docs have been published to:
>>>>>>> http://tinkerpop.apache.
>>>>>>> > > org/docs/3.1.4-SNAPSHOT/
>>>>>>> > >
>>>>>>> > > Changelog bugs and improvements have also been updated with
>>>>>>> where we
>>>>>>> > stand
>>>>>>> > > at this point with 3.1.4:
>>>>>>> > > https://github.com/apache/tinkerpop/blob/tp31/CHANGELOG.asciidoc
>>>>>>> > >
>>>>>>> > > Thanks,
>>>>>>> > > Ted
>>>>>>> > >
>>>>>>> > >
>>>>>>> > >
>>>>>>> > >
>>>>>>> > > On Sun, Aug 28, 2016 at 7:52 AM, Ted Wilmes <twil...@gmail.com>
>>>>>>> wrote:
>>>>>>> > >
>>>>>>> > > > Hello,
>>>>>>> > > > The 3.1.4-SNAPSHOT has been published.  As Stephen mentioned,
>>>>>>> we do not
>>>>>>> > > > expect any
>>>>>>> > > > non-doc changes/additions to tp31 but let me know if something
>>>>>>> comes
>>>>>>> > up.
>>>>>>> > > > I'll be reviewing
>>>>>>> > > > the docs and publishing a doc snapshot later this week.
>>>>>>> > > >
>>>>>>> > > > Thanks,
>>>>>>> > > > Ted
>>>>>>> > > >
>>>>>>> > > > On Sat, Aug 27, 2016 at 5:15 AM, Stephen Mallette <
>>>>>>> > spmalle...@gmail.com>
>>>>>>> > > > wrote:
>>>>>>> > > >
>>>>>>> > > >> Code freeze begins today. Some minor changes to expect on
>>>>>>> master:
>>>>>>> > > >>
>>>>>>> > > >> + We have one lingering PR that needs to be merged once it is
>>>>>>> rebased:
>>>>>>> > > >> https://github.com/apache/tinkerpop/pull/385
>>>>>>> > > >> + I suspect we will see more tests on gremlin-python as well
>>>>>>> as tweaks
>>>>>>> > > to
>>>>>>> > > >> the build process
>>>>>>> > > >> + We may see one more serializers added to GraphSON 2.0 -
>>>>>>> > > >> TraversalExplanation
>>>>>>> > > >> + More docs as usual
>>>>>>> > > >>
>>>>>>> > > >> Recall, that gremlin-python and GraphSON 2.0 will be
>>>>>>> "experimental"
>>>>>>> > so I
>>>>>>> > > >> don't think we should be too concerned about late changes on
>>>>>>> that
>>>>>>> > stuff
>>>>>>> > > at
>>>>>>> > > >> this point. So - nothing major coming down the pike and as
>>>>>>> far as I
>>>>>>> > know
>>>>>>> > > >> there shouldn't be any change on tp31 branch aside from some
>>>>>>> added
>>>>>>> > > >> documentation.
>>>>>>> > > >>
>>>>>>> > > >> Providers should be free to test things out in their
>>>>>>> implementations.
>>>>>>> > > I've
>>>>>>> > > >> published the 3.2.2-SNAPSHOT to Apache Snapshots repo. Note
>>>>>>> that Ted
>>>>>>> > is
>>>>>>> > > >> going to be handling the 3.1.4 release - he will publish the
>>>>>>> > > >> 3.1.4-SNAPSHOT
>>>>>>> > > >> sometime soon (thanks for helping out with that Ted - it will
>>>>>>> be
>>>>>>> > > >> interesting to have two voices taking us through code freeze
>>>>>>> week into
>>>>>>> > > >> release)..
>>>>>>> > > >>
>>>>>>> > > >> As usual, please stay tuned to this thread for updates as we
>>>>>>> head to
>>>>>>> > > >> release. Thanks!
>>>>>>> > > >>
>>>>>>> > > >
>>>>>>> > > >
>>>>>>> > >
>>>>>>> >
>>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>
>>>
>>
>

Reply via email to