Re: Bug fix releases of the 2.2 and 2.4 branches
On Fri, Apr 20, 2012 at 1:08 PM, Alex Parvulescu wrote: > Sure, no problem! > > Bart, this mission is on you, if you choose to accept it ;) I'll accept ;-) I'll start reading the docs and ping you and/or Jukka if I have some questions about the release process. Please let me know if there are some common pitfalls that I need to avoid. Regards, Bart > > best, > alex > > > On Fri, Apr 20, 2012 at 12:33 PM, Jukka Zitting > wrote: >> >> Hi, >> >> On Fri, Apr 20, 2012 at 10:35 AM, Alex Parvulescu >> wrote: >> > About 2.4.x: we did not have a release announcement, so everybody can >> > make >> > sure the issues that they want will get included, like you guys did. >> > I'm thinking it would be too short notice to do it today, so I'd leave >> > it >> > for next week. >> >> Actually, if you and Bart don't mind, it would be great if Bart could >> take care of cutting the 2.4.2 release with your help. The more people >> we have who are familiar with the release process, the better, as that >> removes bottlenecks and allows us to more actively ship releases. >> >> BR, >> >> Jukka Zitting > > -- Amsterdam - Oosteinde 11, 1017 WT Amsterdam Boston - 1 Broadway, Cambridge, MA 02142 US +1 877 414 4776 (toll free) Europe +31(0)20 522 4466 www.onehippo.com
Re: Bug fix releases of the 2.2 and 2.4 branches
Sure, no problem! Bart, this mission is on you, if you choose to accept it ;) best, alex On Fri, Apr 20, 2012 at 12:33 PM, Jukka Zitting wrote: > Hi, > > On Fri, Apr 20, 2012 at 10:35 AM, Alex Parvulescu > wrote: > > About 2.4.x: we did not have a release announcement, so everybody can > make > > sure the issues that they want will get included, like you guys did. > > I'm thinking it would be too short notice to do it today, so I'd leave it > > for next week. > > Actually, if you and Bart don't mind, it would be great if Bart could > take care of cutting the 2.4.2 release with your help. The more people > we have who are familiar with the release process, the better, as that > removes bottlenecks and allows us to more actively ship releases. > > BR, > > Jukka Zitting >
Re: Bug fix releases of the 2.2 and 2.4 branches
Hi, On Fri, Apr 20, 2012 at 10:35 AM, Alex Parvulescu wrote: > About 2.4.x: we did not have a release announcement, so everybody can make > sure the issues that they want will get included, like you guys did. > I'm thinking it would be too short notice to do it today, so I'd leave it > for next week. Actually, if you and Bart don't mind, it would be great if Bart could take care of cutting the 2.4.2 release with your help. The more people we have who are familiar with the release process, the better, as that removes bottlenecks and allows us to more actively ship releases. BR, Jukka Zitting
Re: Bug fix releases of the 2.2 and 2.4 branches
Hi Bart, I'm doing 2.2.12 now, see Jukka's email announcing it as well [0]. About 2.4.x: we did not have a release announcement, so everybody can make sure the issues that they want will get included, like you guys did. I'm thinking it would be too short notice to do it today, so I'd leave it for next week. What do you think? thanks, alex [0] http://jackrabbit.markmail.org/thread/nxqpxasfja4wlyoe On Fri, Apr 20, 2012 at 10:11 AM, Bart van der Schans < [email protected]> wrote: > Great Alex! Since I proposed the releases I'm of course also willing > to help out where possible ;-) > > Regards, > Bart > > On Thu, Apr 19, 2012 at 3:58 PM, Alex Parvulescu > wrote: > > Having been through the process for Oak 0.1 I happily volunteer to > release > > JR 2.2x & 2.4.x > > > > Assuming nobody else wants to give it a go :) > > > > alex > > > > > > On Thu, Apr 19, 2012 at 1:50 PM, Jukka Zitting > > wrote: > >> > >> Hi, > >> > >> On Wed, Apr 18, 2012 at 3:57 PM, Bart van der Schans > >> wrote: > >> > I've merged the fixes to the 2.4 and 2.2 branches since most of our > >> > customers are still on 2.2.x releases. I would like to go for bugfix > >> > releases 'soonish' for both 2.2 as 2.4 as these are rather important > >> > issues (at least to us). Would that be possible and fit with other > >> > outstanding patches? What would be a reasonable time frame? > >> > >> Apart from any blockers (AFAICT none exist for 2.2.x or 2.4.x) we can > >> cut releases as often as we like. > >> > >> I'm a bit busy at least for this and next week, but if you like, I'd > >> be happy to help you (or anyone else) through the release manager > >> tasks. Most of the steps are already covered in > >> http://jackrabbit.apache.org/creating-releases.html. > >> > >> BR, > >> > >> Jukka Zitting > > > > >
Re: Bug fix releases of the 2.2 and 2.4 branches
Great Alex! Since I proposed the releases I'm of course also willing to help out where possible ;-) Regards, Bart On Thu, Apr 19, 2012 at 3:58 PM, Alex Parvulescu wrote: > Having been through the process for Oak 0.1 I happily volunteer to release > JR 2.2x & 2.4.x > > Assuming nobody else wants to give it a go :) > > alex > > > On Thu, Apr 19, 2012 at 1:50 PM, Jukka Zitting > wrote: >> >> Hi, >> >> On Wed, Apr 18, 2012 at 3:57 PM, Bart van der Schans >> wrote: >> > I've merged the fixes to the 2.4 and 2.2 branches since most of our >> > customers are still on 2.2.x releases. I would like to go for bugfix >> > releases 'soonish' for both 2.2 as 2.4 as these are rather important >> > issues (at least to us). Would that be possible and fit with other >> > outstanding patches? What would be a reasonable time frame? >> >> Apart from any blockers (AFAICT none exist for 2.2.x or 2.4.x) we can >> cut releases as often as we like. >> >> I'm a bit busy at least for this and next week, but if you like, I'd >> be happy to help you (or anyone else) through the release manager >> tasks. Most of the steps are already covered in >> http://jackrabbit.apache.org/creating-releases.html. >> >> BR, >> >> Jukka Zitting > >
Re: Bug fix releases of the 2.2 and 2.4 branches
Having been through the process for Oak 0.1 I happily volunteer to release JR 2.2x & 2.4.x Assuming nobody else wants to give it a go :) alex On Thu, Apr 19, 2012 at 1:50 PM, Jukka Zitting wrote: > Hi, > > On Wed, Apr 18, 2012 at 3:57 PM, Bart van der Schans > wrote: > > I've merged the fixes to the 2.4 and 2.2 branches since most of our > > customers are still on 2.2.x releases. I would like to go for bugfix > > releases 'soonish' for both 2.2 as 2.4 as these are rather important > > issues (at least to us). Would that be possible and fit with other > > outstanding patches? What would be a reasonable time frame? > > Apart from any blockers (AFAICT none exist for 2.2.x or 2.4.x) we can > cut releases as often as we like. > > I'm a bit busy at least for this and next week, but if you like, I'd > be happy to help you (or anyone else) through the release manager > tasks. Most of the steps are already covered in > http://jackrabbit.apache.org/creating-releases.html. > > BR, > > Jukka Zitting >
Re: Bug fix releases of the 2.2 and 2.4 branches
Hi, On Wed, Apr 18, 2012 at 3:57 PM, Bart van der Schans wrote: > I've merged the fixes to the 2.4 and 2.2 branches since most of our > customers are still on 2.2.x releases. I would like to go for bugfix > releases 'soonish' for both 2.2 as 2.4 as these are rather important > issues (at least to us). Would that be possible and fit with other > outstanding patches? What would be a reasonable time frame? Apart from any blockers (AFAICT none exist for 2.2.x or 2.4.x) we can cut releases as often as we like. I'm a bit busy at least for this and next week, but if you like, I'd be happy to help you (or anyone else) through the release manager tasks. Most of the steps are already covered in http://jackrabbit.apache.org/creating-releases.html. BR, Jukka Zitting
Re: Bug fix releases of the 2.2 and 2.4 branches
On 2012-04-18 15:57, Bart van der Schans wrote: Hi all, With our customers we have had some considerable issues with data inconsistencies in the repository for quite a while now. As of lately we have spent a considerable amount of time to tackle this. We have taken three approaches: - improving the (stand alone) checker app (still work in progress) - creating a tool that hammers the repository with random concurrent operations to find reproduction paths - fixing the found problems reported by this tool [1,2,3,4] We used to be able to find a lot of inconsistencies after just running five minutes or so. The good news is that after the fixes of [1,2,3,4] we were not able to produce any inconsistencies with concurrent single node tests and concurrent clustered tests! I've merged the fixes to the 2.4 and 2.2 branches since most of our customers are still on 2.2.x releases. I would like to go for bugfix releases 'soonish' for both 2.2 as 2.4 as these are rather important issues (at least to us). Would that be possible and fit with other outstanding patches? What would be a reasonable time frame? Regards, Bart ... +1 on creating new releases as soon as possible (easy to say, as I don't have to do the work for it :-)
