At this point, if its not a bug, why is it being tagged for a release candidate? That just increases the chances of more bugs :-)
On Thu, Oct 3, 2013 at 11:14 AM, Jérôme LELEU <[email protected]> wrote: > Hi, > > I don't think we have a precise one. There are a list of remaining JIRAs. > I have changed the fix version to 4.0.0-RC2 to mark the ones that must be > addressed for the RC : > > https://issues.jasig.org/browse/CAS-1362?jql=project%20%3D%20CAS%20AND%20affectedVersion%20in%20(%224.0%22%2C%20%224.0%20RC1%22)%20AND%20fixVersion%20%3D%20%224.0%20RC2%22%20AND%20status%20in%20(Open%2C%20%22In%20Progress%22%2C%20Reopened) > > Feedbacks are welcome. > > Best regards, > Jérôme > > > > 2013/10/3 Scott Battaglia <[email protected]> > >> My understanding of a release candidate status is that we are feature >> complete, in a testing/polishing mode for a general audience release. >> >> I see us still committing things that increase the scope of a 4.0 >> release. Have we redefined release candidate? >> >> -- >> You are currently subscribed to [email protected] as: [email protected] >> To unsubscribe, change settings or access archives, see >> http://www.ja-sig.org/wiki/display/JSG/cas-dev >> >> > -- > You are currently subscribed to [email protected] as: > [email protected] > > To unsubscribe, change settings or access archives, see > http://www.ja-sig.org/wiki/display/JSG/cas-dev > > -- You are currently subscribed to [email protected] as: [email protected] To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/cas-dev
