Made some good progress towards 4.1.0 release, but squaring that away is going to spill into this week.
Again, master freeze to tie up the 4.1.0 release doesn't preclude sharing code?, and it's certain that there will be a 4.1.1 patch release thereafter, so spiffying up feature branches for merge post-release is not misplaced effort even in the interim. :) Andrew ________________________________ From: Andrew Petro Sent: Thursday, July 03, 2014 12:26 PM To: [email protected] Subject: FREEZE master for 4.1.0 release uPortal developers, I request that Jasig/uPortal/master be considered frozen to changes pending the release of uPortal 4.1.0 GA (or a RC, depending on the outcome of the now pending uPortal 4.1.0 release vote). Of course, part of the beauty of distributed source control is that `master` freeze for release in no way impairs collaboration upon and sharing of code. By all means, fix your favorite bug this weekend. Fixing bugs is patriotic. To the extent that there are changes that need to make it into the 4.1.0 GA release (or that RC), please be sure I'm aware. Kind regards, Andrew ? -- 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
