We (Drew, Eric G, I, and some others) were just talking yesterday about this. We collectively agree there is no reason to wait at this point for any other changes. We are ready for a 4.1.0 release. If someone has time to pull in any of the existing pull requests that are worth while that is great, but I'd say let's cut and celebrate!
James Wennmacher - Unicon 480.558.2420 On 07/01/2014 09:05 AM, Andrew Petro wrote: > > So, how about that uPortal 4.1 release? > > > All of the JIRA issues identified in James' email are marked resolved. > > > There are no "Blocker" issues tagged as affecting 4.1.0, though maybe > this one ought to be a "Blocker": > https://issues.jasig.org/browse/UP-3935 . There are no unresolved > "Blocker" issues tagged as fix-for 4.1.0. > > > So. Anyone intend to fix something in `master` so important that it > ought to hold up releasing 4.1.0 ? Or are we at that point where > 4.1.0 GA ought to be cut from master whenever release engineering > bandwidth can be mustered? > > > Kind regards, > > > Andrew > > > > ------------------------------------------------------------------------ > *From:* [email protected] > <[email protected]> on behalf of James > Wennmacher <[email protected]> > *Sent:* Thursday, June 19, 2014 2:45 PM > *To:* [email protected] > *Subject:* Re: [uportal-dev] uPortal 4.1 release march > I suggest holding off for about two weeks. We are tackling some > issues for some clients that are important enough to them that they > want to hold up a release for a fix. > > Their issues are: > - IE10 support (UP-4121, UP-4122, UP-4123) > - Drag n drop portlets from customize (UP-4000) > - hide add tab in maximized view (UP-4104) > > I think these would benefit the broader community and might as well be > in a GA release. > James Wennmacher - Unicon > 480.558.2420 > On 06/19/2014 08:43 AM, Andrew Petro wrote: >> So, how about that uPortal 4.1 release? >> >> Anyone aware of defects in 4.1 RC2, unfixed on master, that are so >> significant they ought to block a 4.1 GA release? >> >> There are no BLOCKER issues tagged as affecting 4.1.0: >> >> http://goo.gl/SV6mJV >> >> And there are no unresolved BLOCKER issues tagged as fix-for 4.1.0: >> >> http://goo.gl/4lxwND >> >> So. Anyone intend to fix something soon in master so important it >> ought to hold up 4.1.0? Or are we at that post-conference point of >> good to cut 4.1.0 whenever release engineering attentions can be applied? >> >> >> >> >> > -- > > 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/uportal-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/uportal-dev
