That sounds reasonable. Does anyone have Laura M's contact info so we can ping her and find out what her process was going to be and how to access the information?
James Wennmacher - Unicon 480.558.2420 On 07/10/2014 12:14 PM, Andrew Petro wrote: > No, I didn't and don't intend to hold 4.1 release for product manual > updates, nor am I personally committed to completing the product > manual updates updates and merging them immediately. > > I did have in mind to nuance the link from the release notes to the > manual with some kind of language about the documentation efforts are > ongoing. > > I do think that there will need to be some documentation update > efforts in support of uP 4.1 upgrades and implementations. I figure at > this point the only realistic option is to pursue that in parallel to > the 4.1.x patch series. > > I don't know how to diff and merge Confluence spaces. > > Andrew > > Sent from my phone > > On Jul 10, 2014, at 1:30 PM, "James Wennmacher" > <[email protected] <mailto:[email protected]>> wrote: > >> One other thing that just occurred to me that needs to be done is to >> incorporate the changes made to the uP 4.0 manual into the uP 4.1 >> manual from the point in time that uP 4.1 manual was duplicated from >> uP 4.0 manual. Andrew was this on your task list? >> >> Laura had some way of seeing the changes to incorporate them from one >> space to another. Does anyone know how to do that? If not we may >> need to contact Laura for guidance. I know I made some edits to both >> 4.0 and 4.1, but not always to both, and sometimes I had different >> edits such as with the CAS Clearpass configuration so a completely >> automated process may not work well if there is one. >> James Wennmacher - Unicon >> 480.558.2420 >> On 07/10/2014 06:09 AM, Andrew Petro wrote: >>> >>> Status update on this: >>> >>> >>> Short version: Updated ETA for uPortal 4.1.0 is Monday July 14th. >>> >>> >>> You can most immediately help by grabbing this changeset, testing >>> it, and reassuring all that it ought to be merged already >>> thanks-very-much. : https://github.com/Jasig/uPortal/pull/378 : :) >>> >>> >>> Long version: >>> >>> >>> The good news is JIRA is now groomed to provide clearer reporting >>> when you ask it questions about the uPortal 4.1.0 release (and the >>> staged 4.1.0 release notes page now embeds a couple of those >>> queries) and human-readable narrative release notes are coming >>> together. uPortal 4.1.0 is a *huge* release in terms of the >>> accumulated goodness since 4.0.0 (much of which has been doled out >>> bit by bit in 4.0.x releases as well). There's a lot to be excited >>> about in the 4.1 release and the tooling is coming together to >>> communicate that substance. >>> >>> >>> The other mostly good news is that I've been in a lot of training >>> and conference this week about presenting skills, conveying >>> presence, and modern UX design and development. I suggest that's >>> great news in that all of those skills are good for the uPortal >>> project. :) >>> >>> >>> However, it does get in the way of heads down release engineering, >>> and there's a limit to how much bandwidth abuse I'm willing to >>> inflict on my fellow conference attendees, so remaining release >>> tasks will click together bit by bit over the next few days. >>> >>> >>> Again, the `master` freeze for 4.1.0 release engineering in no way >>> blocks grabbing the `master` code to work with it and crafting >>> branches and even pull requests for the fixes and improvements that >>> will come into uPortal post 4.1.0. :) >>> >>> >>> Kind regards, >>> >>> >>> Andrew >>> >>> >>> >>> >>> ------------------------------------------------------------------------ >>> *From:* Andrew Petro >>> *Sent:* Sunday, July 06, 2014 10:02 PM >>> *To:* [email protected] >>> *Subject:* RE: FREEZE master for 4.1.0 release >>> >>> 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 [email protected] >>> as:[email protected] >>> To unsubscribe, change settings or access archives, >>> seehttp://www.ja-sig.org/wiki/display/JSG/uportal-dev >> >> -- >> >> You are currently subscribed [email protected] >> <mailto:[email protected]> as:[email protected] >> <mailto:[email protected]> >> To unsubscribe, change settings or access archives, >> seehttp://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 -- 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
