Re: [Jython-dev] Jython 2.7.2b1 -- ready to go?

[Jeff A. <ja...@fa...>]

On 10/10/2019 06:26, fwi...@gm... wrote:
> OK - I got my environment issues worked out (some dumb stuff with my
> local brew setup and mercurial), and I was able to follow the release
> procedure here:
> https://jython-devguide.readthedocs.io/en/latest/release_jy.html I
> think the release process and docs are in good shape. I avoided
> looking at the gradle stuff for now :)
Thanks for diving in. If I understand correctly, you don't need to 
install Gradle because .\gradlew (w is for wrapper, not Windows) and its 
subdirectory brings all you need.
> In section 23.1.7, it suggests that that I run `ant full-check` and
> later suggests that this will create a build, but I think we want `ant
> full-build`, does that sound right? I'm rusty so I could be missing
> something.

In 23.1.7 we run full-check again as a safety check that we're actually 
at the tag, that the output prints what you see in the display box. The 
build does various integrity checks. In the subsequent paragraph (text), 
it says to run the full-build. Could be more explicit.

> On OSX I get one extra failure on `test_socket_jy` but it looks
> similar to the test_ssl_jy failure so not a big deal IMO.

I find networking tests have to be taken with a pinch of salt on 
personal devices, I think because of their interaction with security 
products or ISA DNS hijacking. OTOH networking is an area where Jython 
hangs by a thread (or many concurrent threads :). I take some comfort 
that this ran ok on CI: 
https://travis-ci.org/jythontools/jython/jobs/595290735#L647

> I think it looks like a step was removed from maven/build.xml - it
> previously gpg signed the bundles to be uploaded to maven. I think
> this step is necessary to publish the bundles. I'll look into it in
> more detail tomorrow.

Yes, it failed gracelessly on my machine and looked optional 
(https://hg.python.org/jython/file/05f61ba4d447/maven/build.xml#l172). 
Presumably the person using the script has to have a (your) private key 
anyway for the result to be acceptable. It looks like the signatures 
will sit alongside the JAR files as separate files, but I don't know the 
tool. Sorry, I should have created a personal account at Sonatype to 
dry-run this.

Could it be done manually at the prompt for now? Note that the location 
of the bundles is ./publications now and that's all there is in it, so 
easy to glob. If you edit maven/build.xml the safeguards will force you 
to make a snapshot becuase you have changes not checked-in at the tag.

I have raised issue 2814 to fix.

> But, progress - almost there!
>
> BTW when I get this all published, would you want to do the
> announcement Jeff? I'm happy to do it, but I'm also happy to just
> point to your announcement if you would like to do it.

You have various channels under your control: I don't see why you 
wouldn't use those with much the same announcement as before. I'm able 
to update the website. (I think we want to show 2.7.1 as current and the 
beta alongside.) It's adveretising. Let's do everything.

All: Any thoughts on target duration? I think maybe a fixed 6 weeks 
(subject to personal commitments) and the next thing is either b2 or rc1 
depending on how many new bugs appear and their criticality.

Jeff