On Thursday, 19 December 2013, Kristian Rosenvold wrote: > I think all the crap/trolling in the release threads has gone way too far, > it's just not fun any more. > > I can only request that PMC members chip in *before* the the vote to > /improve/ technical problems with a release > rather than spending a ton of energy documenting their -1 *after* the > release is staged.
I did my testing, I found an issue which, in good conscience I feel means I cannot vote +1. I stated my vote was not a veto and I would not stand in the way of a release. This only needed one more +1 from a PMC member... I don't see that as trolling... Where was your vote? > > Kristian > > > 2013/12/19 Robert Scholte <rfscho...@apache.org> > > > Stephens remarks are valid, let me try to pick this up in the next couple > > of weeks. > > > > Robert > > > > Op Thu, 19 Dec 2013 18:31:13 +0100 schreef Dominik Bartholdi < > > d...@fortysix.ch>: > > > > > > Thanks Oliver, > >> its a bit disappointing, as this at the end (at least for me) also means > >> the other scm components are not maintainable anymore… > >> Taking this into account, then its probably a better idea to not have > >> this under the apache umbrella anyway. > >> Where do you think we should release it from? Or should I just make a > >> release with my own gav and publish it via Sonatype? > >> regards Domi > >> > >> On 16.12.2013, at 00:15, Olivier Lamy <ol...@apache.org> wrote: > >> > >> So that's 2 weeks now. > >>> I presume I can say the vote failed. > >>> I will delete the tag and the staging repo. > >>> If someone else want to act RM let's go. perso I'm tired.... > >>> > >>> @Domi I'm sorry I believed if was a good idea to have the module jgit > >>> here (but cvs looks to me more important :P ). > >>> Anyway we can release that separately somewhere else. > >>> > >>> Cheers, > >>> > >>> Olivier > >>> > >>> > >>> On 5 December 2013 04:24, Dominik Bartholdi <d...@fortysix.ch> wrote: > >>> > >>>> OK, then you have my +1 > >>>> /Domi > >>>> > >>>> On 03.12.2013, at 08:20, Olivier Lamy <ol...@apache.org> wrote: > >>>> > >>>> No worries. > >>>>> IMHO it's not the problem. Issue is cvs-commons module. > >>>>> > >>>>> -- > >>>>> Olivier > >>>>> On Dec 3, 2013 3:34 PM, "Dominik Bartholdi" <d...@fortysix.ch> > wrote: > >>>>> > >>>>> Sorry guys, during the week I’m usually a bit short in time… > >>>>>> But is ist possible, that my commit > >>>>>> d1f102e5223e5fe0f852e1a5becb497f0e860d6a is actually causing this > >>>>>> issue? > >>>>>> Its an exclude of some CVS stuff I had in my untracked list all the > >>>>>> time > >>>>>> when doing a full build... > >>>>>> regards Domi > >>>>>> > >>>>>> > >>>>>> On 03.12.2013, at 02:57, Olivier Lamy <ol...@apache.org> wrote: > >>>>>> > >>>>>> On 3 December 2013 12:52, Bernd Eckenfels <e...@zusammenkunft.net> > >>>>>>> > >>>>>> wrote: > >>>>>> > >>>>>>> Am 03.12.2013, 02:47 Uhr, schrieb Olivier Lamy <ol...@apache.org>: > >>>>>>>> > >>>>>>>> For some reasons I don't understand yet why defaultExclude=false > >>>>>>>>> doesn't work for CVS directories. > >>>>>>>>> > >>>>>>>> > >>>>>>>> > >>>>>>>> Uh, isnt that supposed to be "yes" to enable the exclusion of > >>>>>>>> default > >>>>>>>> patterns? > >>>>>>>> > >>>>>>> > >>>>>>> no because in this case we want some cvs directories included in > the > >>>>>>> > >>>>>> assembly. > >>>>>> > >>>>>>> That's why we need to use defaultExclude=false to prevent some > >>>>>>> default > >>>>>>> pattern exclusion (or I really understand nothing :-)) > >>>> -- Sent from my phone
