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

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

On 11/10/2019 07:03, fwi...@gm... wrote:
> I have the bundles built and gpg signed, but I'm still missing
> something that prevents me from finalizing the uploads, I'll keep
> trying and post here when we have soft releases available.

It's disappointing the upload tool (website I assume) doesn't pinpoint 
the problem. I think I'd misunderstood earlier: we sign JARs and POM 
individually and bundle don't we, rather than sign each bundle? So where 
my build stops (with 4 purported bundles) isn't a feasible starting 
point: the problem is further back, and these "bundles"  don't have 
signatures for the objects inside. So (explaining to myself), it's the 
contents of ./build/maven that need (individually) signing, as generated 
by the targets bundle, bundle-standalone, etc..

The maven/build.xml we inherited is this: 
https://hg.python.org/jython/file/3b424500eab9/maven/build.xml and my 
changes have been to eliminate the hard-coding of project.version and to 
include the Gradle-built JAR if it exists. I also changed build.dir to 
build.maven (=./build/maven), because the same name meaning something 
completely different from in the main build was confusing me.

I thought it odd that the hard-coding was for 2.7.0 beta, whereas I know 
we have published several times since then. This suggests we didn't 
inherit the latest version.

If this gets too tangled, we could suspend the attempt and I'll try to 
develop (and encapsulate) a working publication process, tested against 
an account I create and own. But Sonatype confuses me: I haven't even 
found the place it invites me to make such an account.

Jeff

>> 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.
>>
> Sounds good, when I get the release uploaded I will do the
> announcements as usual.
>
>> 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.
> 6 weeks works for me.
>
> -Frank
>