hi marvin, a released version can't get dropped later on. (it's important that the commit and release history is immutable.)
therefore we send out a heads-up mail (about two weeks before a release-vote). (since we release quite often some projects even have a 2nd ci-job which executes the test-suite (of the application) against the latest (daily) snapshot (see [1]) to ensure that they can upgrade to the next version easily and without a significant overhead.) regards, gerhard [1] http://deltaspike.apache.org/documentation/snapshots.html 2015-08-12 16:15 GMT+02:00 Marvin Toll <marvint...@gtcgroup.com>: > Gerhard, > > > > We are attempting to provide feedback as we have time. There was quite a > bit of confusion for a couple of days as we naturally presumed our problems > were of our own making. > > > > So, until such time as Amita (a.k.a. “akm”) is able to get us > “back-on-track” and subsequently provide concrete examples… my suggestion > was (and is) to remove 1.4.2 from circulation. > > > > Note: We would like to think that our problems are similar to Harald’s… > however, we have no definitive understanding of Harald’s problems. Is that > available? > > > > _Marvin > > > > *------------------------------------------* > > *|** USA Cell:** 248.866.4897 <248.866.4897>* > > *|** Email:* *mar...@gtcgroup.com* <marvint...@gtcgroup.com> > > *|** Web:* *http://MarvinToll.com* <http://marvintoll.com/> > > *|** Skype: **marvin.toll* > > *------------------------------------------* > > > > *Pattern Enabled Development* *®** (PED) - **http://pedCentral.com* > <http://pedcentral.com/> > > PED seeks to advance Java/JavaScript application construction > > by inspiring software engineers with Pattern First Thinking, > > enabling project teams with a Pattern Palette, and harmonizing > > enterprise communication with a Unified Pattern Language. > > > > *From:* Gerhard Petracek [mailto:gerhard.petra...@gmail.com] > *Sent:* Wednesday, August 12, 2015 9:13 AM > *To:* dev@deltaspike.apache.org; Marvin Toll <marvint...@gtcgroup.com> > > *Subject:* Re: [VOTE] Release of Apache DeltaSpike 1.5.0 > > > > hi marvin, > > > > please provide concrete details and maybe even tests which illustrate the > issue. > > only with such tests, we can improve our test-suite over time. > > (if you are facing the same issue as harald: we will fix it with v1.5.1.) > > > > regards, > > gerhard > > > > > > > > 2015-08-12 14:53 GMT+02:00 Marvin Toll <marvint...@gtcgroup.com>: > > An update from an unspecified Motor Company: > > We made the decision to roll-back from 1.4.2 to 1.4.0 this morning... as > we had skipped 1.4.1. > > I'd suggest that you pull 1.4.2... as it now appears this release broke > about 50 of our Reference Application JUnit tests. > > _Marvin > > > -----Original Message----- > From: Harald Wellmann [mailto:hwellmann...@gmail.com] > Sent: Tuesday, August 11, 2015 2:30 PM > To: dev@deltaspike.apache.org > Subject: Re: [VOTE] Release of Apache DeltaSpike 1.5.0 > > Hi Gerhard, > > I compared to 1.4.1 because that's the last known good version, 1.4.2 > broke my application already (DELTASPIKE-965), > > After some analysis, I believe the "new regressions" I reported yesterday > were introduced in 1.4.2 and not in 1.5.0 - I wasn't able to see them with > 1.4.2 due to that first blocker (or maybe I should have looked more > closely). > > The point is, the behavior of EntityRepository.save() has changed in an > incompatible way which is likely to break some other applications (not just > mine). > > > I now change my vote to +1, seeing that this 1.5.0 candidate is an > improvement over 1.4.2, but that does not mean that all is well - we need > to sort out a couple of issues related to save(). > > I'll start a separate thread on that, to keep the discussion focused. > > Regards, > Harald > > > > >
