Lewis, Jake, I corrected the tests in the portal (fixed some, one is ignored, but shawn and I agree that this is acceptable). I had planned to do more today but ran out of daylight. I have a pretty busy day tomorrow, but will do my best to press onward.
I think the following needs to occur: 1. remaining PRs must be acked (that are relevant to this process) 2. release must be tagged 3. verify that checksums and php signatures are valid 4. make sure release follows branding guidelines 5. document this process in a wiki page 6. put the release files and pgp signatures here: https://dist.apache.org/repos/dist/dev/incubator/usergrid 7. call for a vote on the release Does this sound accurate and in the correct order? Thanks! Rod -- Rod Simpson @rockerston rodsimpson.com On August 20, 2014 at 7:57:07 AM, Lewis John Mcgibbney ([email protected]) wrote: Hi Rod, On Wed, Aug 20, 2014 at 7:34 AM, < [email protected]> wrote: > Release [DISCUSS] > 1430 by: Rod Simpson > > I would like to tag a release tomorrow. Does anyone have any concerns? > We have failing tests in portal package. As we do not currently have a CI build or nightly build for UG yet we may have other failing tests howere this is not a fact it is merely a concern of mine, > Looking at our parent ticket: > > https://issues.apache.org/jira/browse/USERGRID-122 > > I see that all tasks are resolved or closed except USERGRID-4, which is to > add the remaining license headers. Lewis sent in a PR last week with what > I thought was the remaining headers added, then Shawn also added a few more > that were missing. I added a comment for Lewis and will take ownership of > the ticket tomorrow if he is not able to reply as I have time to work on > this tomorrow if needed. > Please see remaining tickets for 1.0 release *http://s.apache.org/JfJ <http://s.apache.org/JfJ>* Several of these are straigh PR's which are blockers and need to be addressed. > > Once we can confirm that all the headers are added, I will tag a release > and put it up for a vote (at least I think that is what I need to do). > As release manager you are the primary person to make that call. Personally I am happy that once the issues above have been addressed we are ready to rock and roll. What I suggest you do as RM is write wiki docutmentation about how this process can be reproduced. I suspect that the release is not going to be 100% straight forward and I therefore think that we should make it as public and understanable as possible. The DRAFT Incubator RM guide will hopefully be very useful here Rod. http://incubator.apache.org/guides/releasemanagement.html I will be on #usergrid all day for a chat if it is of any help. Thanks
