I can try to have someone give it a spin and report any issues. It might take a week or so to get to it. (Anticipating only minor things around BulkUpdateHandler)
Mario From: Simon Helsen <[email protected]> To: [email protected], Mario Ds Briggs/India/IBM@IBMIN Date: 02/13/2013 07:48 PM Subject: Re: Jena 2.10.0 - ready yet? I happen to have Mario's store in my workspace and I didn't observe any obvious issues in terms of compilation other than the package renames, but I didn't run our test suite yet because some adaptations will (likely) be required on his side. I've asked Mario to check what needs to be done if we were to upgrade, the reason being that if our part of the organization upgrades, it is desirable if Mario's part upgrades as well. If Mario's effort to adjust is small enough, I should be able to run our own test suite against Mario's store adjusted for 2.10.0 and check if there are any obvious issues or regressions. Simon From: Andy Seaborne <[email protected]> To: [email protected], Mario Ds Briggs <[email protected]>, Date: 02/13/2013 04:43 AM Subject: Re: Jena 2.10.0 - ready yet? Stephen, Let's see how it goes - you mentioned 3-4 weeks, as did Rob, so I worked back from that and started ASAP. If things go well, we can start the vote next week and have some overlap. If you want to prompt on users@ and/or ping specific groups who we know should be testing that will accelerate the process. We can give people the chance - it's up to them to take it or not. And any JIRA triage you have a moment for [do-repeat :-)] Cray and IBM have reported which is good. How about your org? Any migration issues? We (Epimorphics) are running with SNAPSHOTs in deployment but then I both find and fix bugs that arise in our work. It would be good to hear from Mario Briggs of IBM as well as they have a different interest. Personally, I am happy with the state of the codebase and a link to the email to users@ got (re)tweeted enough. Andy On 12/02/13 22:05, Stephen Allen wrote: > Any chance we could accelerate the schedule a little bit? Maybe aim > for 1 week of user testing followed the formal release process? It > would happen to work out well for me if the release was final at least > a few days before the end of the month (around say the 25th or 26th). > All this baring any showstoppers of course. > > I've already started running the snapshot, and things seem to work well. > > -Stephen > > On Tue, Feb 12, 2013 at 4:05 AM, Andy Seaborne <[email protected]> wrote: >> Steve, Rob, all, >> >> OK - let's do it! >> >> If we aim for 2 weeks of user community tests then see where we are. >> (If we aren't getting reports there's little point waiting longer IMO.) The >> formal release process takes 3-5 days. >> >> The message to users@ is about to go ... if you have anything to add to it, >> just reply on users@ >> >> Start twittering and getting the word out ... >> >> Andy >> >> >> >> >>
