[oae-production] [oae-dev] Bug Bash - Wednesday, October 5th

N. Matthijs nicolaas.matthijs at caret.cam.ac.uk
Wed Oct 5 03:54:34 PDT 2011


Great news, awesome.

> Ok, I now have got SAKIII-4095 working locally, after banging through
> config files and running my dualing eclipse debuggers.  ( I feel like we
> should make a dualing bango's type of video, but with Eclipse debuggers
> running on multiple nodes both debugging the same request/response cycle
> between different apps! )
>
> I don't think it requires any code changes, and after I clean up my mess
> of torn up config files, I think we should be able to hammer things out
> with Alan and Kent on the QA servers.
>
> -s
>
> On 10/04/2011 04:31 PM, Fitzgerald, Kent wrote:
>> Hi Nico,
>> > From the information I received, the current bug bash server likely
>> would not have sufficient memory to run a single node Hybrid instance.
>>
>> If we can't get the configuration resolved in the near future, I think
>> it'd be useful to look into finding a server we can provision for that
>> purpose. Steve suggested a virtual machine with 4 GB of RAM as a
>> starting point awhile back.
>>
>> I'm hoping we can work through the issues and test initially on a
>> multi-node instance though.
>>
>> -Kent
>>
>>
>> On Oct 4, 2011, at 3:46 PM, N. Matthijs wrote:
>>
>>> Hi Kent,
>>>
>>> Would it be possible to test Hybrid 1 anyway, if only by using a CLE
>>> and
>>> OAE instance on the same box? That would at least allow us to test
>>> the UI side of Hybrid 1, giving us some time to sort out those issues
>>> whilst we figure out the deployment issue.
>>>
>>> However, if it is distracting to get that set up, I'd be happy holding
>>> off
>>> on that.
>>>
>>> Thanks,
>>> Nicolaas
>>>
>>>> Hello everyone, we'll be holding a Bug Bash tomorrow, October 5th, at
>>>> the
>>>> time listed below
>>>>
>>>> We are currently working through some configuration for Hybrid1 on the
>>>> bug
>>>> bash server. If Hybrid1 is ready, we'll make that available for
>>>> testing.
>>>> Regardless, we'd like to have a bug bash for users to look at the rest
>>>> of
>>>> OAE. If Hybrid1 is not ready, we'll schedule another bug bash to focus
>>>> on
>>>> it as soon as possible
>>>>
>>>> Time Zone
>>>>
>>>> Date/Time
>>>>
>>>> Pacific time
>>>>
>>>> October 5th: 9:30-10:30
>>>>
>>>> Eastern Daylight Time
>>>>
>>>> October 5th: 12:30-13:30
>>>>
>>>> BST
>>>>
>>>> October 5th: 17:30-18:30
>>>>
>>>>
>>>> The server will be:
>>>> http://qa20-us.sakaiproject.org:8088/<http://qa20-us.sakaiproject.org:808>
>>>> (please note the port change)
>>>>
>>>> The database will be populated with new data.  Feel free to interact
>>>> with
>>>> any of that data in addition to creating your own.
>>>>
>>>> If filing a bug in JIRA, please use the following values for the
>>>> fields:
>>>> Project: Sakai 3 UI Dev
>>>> Affects Version/s: Sprint 112 AND 1.0.1
>>>> Fix Version/s: Unknown Future Version
>>>>
>>>> Reminder: Clear your browser cache and then restart your browser
>>>> before
>>>> you start testing. If you don't, you'll definitely have issues.
>>>>
>>>> I'll send out a reminder email in the morning with any additional
>>>> details.
>>>>
>>>> If you can attend, the protocol will be the same as bashes that have
>>>> occurred previously, which you can find below.
>>>>
>>>> -----------------------------------------------------------------------------------
>>>>
>>>> What's a bug bash? It's an hour of your time, spent with your peers,
>>>> working to find bugs in OAE. Simply, we get a bunch of people together
>>>> at
>>>> one time to bash the product around. We'll have a common server to log
>>>> onto, an IRC session to that we can use to communicate, and the goal
>>>> is to
>>>> log as many Jiras as possible. Please make it a priority to attend and
>>>> contribute - for the project team, this takes priority over all other
>>>> project work.
>>>>
>>>> Prep
>>>> You'll need the following before the bash:
>>>> 1. Your favorite browser and an internet connection.
>>>> 2. An account on Jira so that you can log bugs. Most people should
>>>> have
>>>> this already. Jira instructions below if you need them.
>>>> 3. Ability to log onto IRC. We'll taking over the developer channel
>>>> for
>>>> this hour: #sakai on irc.freenode.net<http://irc.freenode.net/>. IRC
>>>> instructions below if you need them.
>>>> *****4. Clear your browser cache.*****
>>>>
>>>> Server
>>>> Log on here http://qa20-us.sakaiproject.org:8080/.
>>>>
>>>> What to Look For
>>>> Anything is fair game, but try to do the following items:
>>>>
>>>> 1. Find contacts and communicate with them.
>>>> 2. Create groups and pages, add content, and share with contacts.
>>>> 3. Add widgets/goodies to your pages.
>>>> 4. Update your profile information.
>>>> 5. Find a buddy and test permissions on content.
>>>>
>>>> Where to Log Jiras
>>>> 1. Go to http://jira.sakaiproject.org/browse/SAKIII.
>>>> 2. Log in
>>>> 3. Click: Create issue in project Sakai 3 UI Dev
>>>> 4) Select Bug
>>>> 3. Be as clear as possible in your report.
>>>> Here's info on creating Jiras:
>>>> <http://confluence.sakaiproject.org/display/SAKDEV/Sakai+3+QA+-+Reporting+a+bug+in+Jira>
>>>> http://confluence.sakaiproject.org/display/SAKDEV/Sakai+3+QA+-+Reporting+a+<http://confluence.sakaiproject.org/display/SAKDEV/Sakai+3+QA+-+Reporting+a+bug+in+Jira>bug<http://confluence.sakaiproject.org/display/SAKDEV/Sakai+3+QA+-+Reporting+a+bug+in+Jira>+in+Jira<http://confluence.sakaiproject.org/display/SAKDEV/Sakai+3+QA+-+Reporting+a+bug+in+Jira>
>>>> Screenshots are very helpful, please use freely.
>>>>
>>>> Extra Instructions for those who need them
>>>> 1. Add a Jira account here:
>>>> [http://jira.sakaiproject.org/secure/Signup!default.jspa].
>>>>
>>>> 2. If you don't have an IRC client, the easiest thing to do is this:
>>>>     a. http://webchat.freenode.net<http://webchat.freenode.net/>
>>>>     b. Nickname: something that helps us to know who you are.
>>>>     c. Channels: #sakai
>>>>     d. Connect
>>>>
>>>> Then just join the conversation.
>>>> _______________________________________________
>>>> sakai-ui-dev mailing list
>>>> sakai-ui-dev at collab.sakaiproject.org<mailto:sakai-ui-dev at collab.sakaiproject.org>
>>>> http://collab.sakaiproject.org/mailman/listinfo/sakai-ui-dev
>>>> _______________________________________________
>>>> oae-dev mailing list
>>>> oae-dev at collab.sakaiproject.org
>>>> http://collab.sakaiproject.org/mailman/listinfo/oae-dev
>>>>
>>>
>> _______________________________________________
>> oae-dev mailing list
>> oae-dev at collab.sakaiproject.org
>> http://collab.sakaiproject.org/mailman/listinfo/oae-dev
>
>




More information about the oae-production mailing list