Re: Apache Commons VFS2 version 2.4.2 release?
On Mon, Oct 28, 2019 at 4:46 AM Jurrie Overgoor wrote: > Hi Gary, > > Err... really? > > On the 6th of October you wrote that you were "waiting for feedback on > VFS-733 before cutting an RC." So I waited a week. > > Then, on the 17th of October you wrote that "once Woosan is done with PR > 52 we can create an RC". So I waited 10 days. > > Now, you write that "we are sorting out a new module" which is blocking > an RC. > > So what's next? :) > > I mean, I totally get the "it's done when it's done" thing. But this is > more like saying "it's done, except for XYZ" and then thinking of > something new to put into the next release. That way, it'll never be done. > What is next hopefully is an adjustment of your expectations and attitude :-) to sunny with a chance of meatballs :-) I am a volunteer here as is everyone else contributing. I do what I can when I can for what seems to me at the time like the best outcome for a given component. I am sorry this is not matching up with your expectations. Unfortunately for all of us, releasing components is a bit of a pain (IMO, others differ) and it's not a one button click type of process. So, I try to chunk in work from other folks that are contributing their free time as well to making Apache Commons better. Gary > Jurrie > > > > On 27-10-19 23:39, Gary Gregory wrote: > > We are sorting out a new module ATM, I think that once we are done with > > that, we can propose an RC... > > > > Gary > > > > On Sun, Oct 27, 2019 at 2:48 PM Jurrie Overgoor wrote: > > > >> Hi Gary, > >> > >> https://github.com/apache/commons-vfs/pull/52 was merged to master 10 > >> days ago. Could you release the RC for 2.5.0 please? > >> > >> With kind regards, > >> > >> Jurrie > >> > >> > >> On 17-10-19 16:44, Gary Gregory wrote: > >>> I think that once Woonsan is done with > >>> https://github.com/apache/commons-vfs/pull/52 we can create an RC for > >> 2.5.0. > >>> Gary > >>> > >>> > >>> On Wed, Oct 16, 2019 at 10:34 AM Jurrie Overgoor > >> wrote: > Hi Gary, > > VFS-733 was changed to status 'closed' a week ago. Could you release > the > RC please? > > Again: if there's anything I can help with, let me know. > > With kind regards, > > Jurrie > > > > On 06-10-19 23:41, Gary Gregory wrote: > > Jurrie, > > > > The next release will be labeled 2.5.0 and I am waiting on feedback > for > > https://issues.apache.org/jira/browse/VFS-733 before cutting an RC. > > > > Gary > > > > On Mon, Sep 30, 2019 at 8:54 AM Gary Gregory > > wrote: > >> Jurrie, > >> > >> Nothing is blocking the release of 2.4.2 but for a PMC member to > take > the > >> time to do so. If no one gets to it, I might within a week or two. > >> > >> You are welcome to improve the code base with PRs on GitHub :-) > >> > >> Gary > >> > >> > >> On Mon, Sep 30, 2019 at 6:04 AM Jurrie Overgoor > wrote: > >>> Hello everyone, > >>> > >>> I'm trying to upgrade commons-vfs2 from 2.1. Specifically, I need > >>> VFS-688 and VFS-360, which are introduced in commons-vfs2 2.3. > >>> > >>> But I run into VFS-727, which is also introduced in commons-vfs2 > 2.3. > >>> The bug is solved in 2.4.2, but that version is not yet released. > >>> > >>> 2.4.2 has some unsolved issues: VFS-651, VFS-613, VFS-600, VFS-596, > >>> VFS-586, VFS-500, VFS-298. Are these issues blocking the release of > >>> 2.4.2? (They are all older than 2.4.1.) > >>> > >>> Would it be possible to release 2.4.2? What can I do to help with > >> this? > >>> With kind regards, > >>> > >>> Jurrie > >>> > >>> > >>> > >>> > - > >>> To unsubscribe, e-mail: user-unsubscr...@commons.apache.org > >>> For additional commands, e-mail: user-h...@commons.apache.org > >>> > >>> > - > To unsubscribe, e-mail: user-unsubscr...@commons.apache.org > For additional commands, e-mail: user-h...@commons.apache.org > > > >> - > >> To unsubscribe, e-mail: user-unsubscr...@commons.apache.org > >> For additional commands, e-mail: user-h...@commons.apache.org > >> > >> > > - > To unsubscribe, e-mail: user-unsubscr...@commons.apache.org > For additional commands, e-mail: user-h...@commons.apache.org > >
Re: Apache Commons VFS2 version 2.4.2 release?
Hello, Jurrie if you make contributors spent their time defending themself you won’t speed up the process. If you need it urgently just compile it yourself. A release takes time, especially if it is done in people’s sparetime. Gruss Bernd -- http://bernd.eckenfels.net Von: Jurrie Overgoor Gesendet: Montag, Oktober 28, 2019 9:46 AM An: user@commons.apache.org Betreff: Re: Apache Commons VFS2 version 2.4.2 release? Hi Gary, Err... really? On the 6th of October you wrote that you were "waiting for feedback on VFS-733 before cutting an RC." So I waited a week. Then, on the 17th of October you wrote that "once Woosan is done with PR 52 we can create an RC". So I waited 10 days. Now, you write that "we are sorting out a new module" which is blocking an RC. So what's next? :) I mean, I totally get the "it's done when it's done" thing. But this is more like saying "it's done, except for XYZ" and then thinking of something new to put into the next release. That way, it'll never be done. Jurrie On 27-10-19 23:39, Gary Gregory wrote: > We are sorting out a new module ATM, I think that once we are done with > that, we can propose an RC... > > Gary > > On Sun, Oct 27, 2019 at 2:48 PM Jurrie Overgoor wrote: > >> Hi Gary, >> >> https://github.com/apache/commons-vfs/pull/52 was merged to master 10 >> days ago. Could you release the RC for 2.5.0 please? >> >> With kind regards, >> >> Jurrie >> >> >> On 17-10-19 16:44, Gary Gregory wrote: >>> I think that once Woonsan is done with >>> https://github.com/apache/commons-vfs/pull/52 we can create an RC for >> 2.5.0. >>> Gary >>> >>> >>> On Wed, Oct 16, 2019 at 10:34 AM Jurrie Overgoor >> wrote: Hi Gary, VFS-733 was changed to status 'closed' a week ago. Could you release the RC please? Again: if there's anything I can help with, let me know. With kind regards, Jurrie On 06-10-19 23:41, Gary Gregory wrote: > Jurrie, > > The next release will be labeled 2.5.0 and I am waiting on feedback for > https://issues.apache.org/jira/browse/VFS-733 before cutting an RC. > > Gary > > On Mon, Sep 30, 2019 at 8:54 AM Gary Gregory wrote: >> Jurrie, >> >> Nothing is blocking the release of 2.4.2 but for a PMC member to take the >> time to do so. If no one gets to it, I might within a week or two. >> >> You are welcome to improve the code base with PRs on GitHub :-) >> >> Gary >> >> >> On Mon, Sep 30, 2019 at 6:04 AM Jurrie Overgoor wrote: >>> Hello everyone, >>> >>> I'm trying to upgrade commons-vfs2 from 2.1. Specifically, I need >>> VFS-688 and VFS-360, which are introduced in commons-vfs2 2.3. >>> >>> But I run into VFS-727, which is also introduced in commons-vfs2 2.3. >>> The bug is solved in 2.4.2, but that version is not yet released. >>> >>> 2.4.2 has some unsolved issues: VFS-651, VFS-613, VFS-600, VFS-596, >>> VFS-586, VFS-500, VFS-298. Are these issues blocking the release of >>> 2.4.2? (They are all older than 2.4.1.) >>> >>> Would it be possible to release 2.4.2? What can I do to help with >> this? >>> With kind regards, >>> >>> Jurrie >>> >>> >>> >>> - >>> To unsubscribe, e-mail: user-unsubscr...@commons.apache.org >>> For additional commands, e-mail: user-h...@commons.apache.org >>> >>> - To unsubscribe, e-mail: user-unsubscr...@commons.apache.org For additional commands, e-mail: user-h...@commons.apache.org >> - >> To unsubscribe, e-mail: user-unsubscr...@commons.apache.org >> For additional commands, e-mail: user-h...@commons.apache.org >> >> - To unsubscribe, e-mail: user-unsubscr...@commons.apache.org For additional commands, e-mail: user-h...@commons.apache.org
Re: Apache Commons VFS2 version 2.4.2 release?
Hi Gary, Err... really? On the 6th of October you wrote that you were "waiting for feedback on VFS-733 before cutting an RC." So I waited a week. Then, on the 17th of October you wrote that "once Woosan is done with PR 52 we can create an RC". So I waited 10 days. Now, you write that "we are sorting out a new module" which is blocking an RC. So what's next? :) I mean, I totally get the "it's done when it's done" thing. But this is more like saying "it's done, except for XYZ" and then thinking of something new to put into the next release. That way, it'll never be done. Jurrie On 27-10-19 23:39, Gary Gregory wrote: We are sorting out a new module ATM, I think that once we are done with that, we can propose an RC... Gary On Sun, Oct 27, 2019 at 2:48 PM Jurrie Overgoor wrote: Hi Gary, https://github.com/apache/commons-vfs/pull/52 was merged to master 10 days ago. Could you release the RC for 2.5.0 please? With kind regards, Jurrie On 17-10-19 16:44, Gary Gregory wrote: I think that once Woonsan is done with https://github.com/apache/commons-vfs/pull/52 we can create an RC for 2.5.0. Gary On Wed, Oct 16, 2019 at 10:34 AM Jurrie Overgoor wrote: Hi Gary, VFS-733 was changed to status 'closed' a week ago. Could you release the RC please? Again: if there's anything I can help with, let me know. With kind regards, Jurrie On 06-10-19 23:41, Gary Gregory wrote: Jurrie, The next release will be labeled 2.5.0 and I am waiting on feedback for https://issues.apache.org/jira/browse/VFS-733 before cutting an RC. Gary On Mon, Sep 30, 2019 at 8:54 AM Gary Gregory wrote: Jurrie, Nothing is blocking the release of 2.4.2 but for a PMC member to take the time to do so. If no one gets to it, I might within a week or two. You are welcome to improve the code base with PRs on GitHub :-) Gary On Mon, Sep 30, 2019 at 6:04 AM Jurrie Overgoor wrote: Hello everyone, I'm trying to upgrade commons-vfs2 from 2.1. Specifically, I need VFS-688 and VFS-360, which are introduced in commons-vfs2 2.3. But I run into VFS-727, which is also introduced in commons-vfs2 2.3. The bug is solved in 2.4.2, but that version is not yet released. 2.4.2 has some unsolved issues: VFS-651, VFS-613, VFS-600, VFS-596, VFS-586, VFS-500, VFS-298. Are these issues blocking the release of 2.4.2? (They are all older than 2.4.1.) Would it be possible to release 2.4.2? What can I do to help with this? With kind regards, Jurrie - To unsubscribe, e-mail: user-unsubscr...@commons.apache.org For additional commands, e-mail: user-h...@commons.apache.org - To unsubscribe, e-mail: user-unsubscr...@commons.apache.org For additional commands, e-mail: user-h...@commons.apache.org - To unsubscribe, e-mail: user-unsubscr...@commons.apache.org For additional commands, e-mail: user-h...@commons.apache.org - To unsubscribe, e-mail: user-unsubscr...@commons.apache.org For additional commands, e-mail: user-h...@commons.apache.org