Hi All I will go ahead and prepare the 2.7.3 release tomorrow morning from around 10:30 PST onwards
I have worked through the first few preparatory steps to make sure I am ready to go and have a few questions which if anyone is able to answer for me ahead of my real release run tomorrow would be super helpful and save me bugging people via Skype/email tomorrow: 1 - Step 5 mentions checking the release artifacts but when I do a dry run some of these are not generated. Specifically I only get the top level source release, the distribution zips for Jena and Fuseki are not generated. Is this an artifact of a dry run or a sign of something going wrong? 2 - Step 7 says Go and close the staging repo - record the URL. More detail on what this means would be extremely helpful, where does the staging repo come from, how would I close it and where do I find the URL 3 - Step 11 says Go and clean up your local repo - which repo and what clean up? 4 - Step 13 says Rebuild the jena development build - I assume this means go prod Jenkins? 5 - Where is our project KEYS file kept so I can add my key to it since the release will be signed with my key which currently isn't in there Thanks, Rob On 8/1/12 1:54 PM, "Rob Vesse" <[email protected]> wrote: >Ok great, > > >I will likely try and do a RAT run later today/tomorrow with the aim being >to produce the actual release candidate for a vote on Friday > >Rob > >On 8/1/12 12:28 PM, "Andy Seaborne" <[email protected]> wrote: > >>On 01/08/12 17:15, Stephen Allen wrote: >>> +1 on release. >>> >>> >>> On Wed, Aug 1, 2012 at 5:46 AM, Andy Seaborne <[email protected]> wrote: >>>> Do we want to release after removing (or merely switching off) the >>>> NodeCache? TripleCache? >>>> >>>> As the system seems slightly faster without, I'm minded to switch them >>>>off. >>>> >>>> The Node cache might give a space advantage. But there is another >>>>cache >>>> (which does make a difference) in RIOT for IRI resolution, and so the >>>>string >>>> for the IRI is shared for the same IRI input when using RIOT. >>>> >>>> Integrating RIOT properly into jena-core is ready-to-go but I'm not >>>> comfortable doing that juts before a release. >>>> >>>> Without presuming the decision on the Node cache for this release, >>>>I've made >>>> minimal changes (Node, Triple) to run without caches. My expectation >>>>is >>>> that no-one will, or even can, notice the difference from outside. >>>>The Node >>>> cache can be turned on explicitly. >>>> >>> >>> I'd say totally remove both the Node and Triple caches. Just >>> switching off the cache in Node still leaves the create() method >>> synchronized, and unnecessary checks into the empty cache on node >>> creation. >> >>Done. >> >>The word 'synchronized' does not appear in Node.java anymore. >> >>A quick-and-dirty test: parsing BSBM 25M from compressed :: 132K TPS >>(2.7.2 jars) -> 136K (with changes, and some classes not jars) >> >> Andy >> >>> >>> -Stephen >>> >> >
