Hello All,
We are in code freeze for OpenHPI-3.2.1 release. Release date will be July 1,
2013.
Please help with the testing of the 3.2.x branch.
svn export http://svn.code.sf.net/p/openhpi/code/openhpi/branches/3.2.x openhpi
Thanks
Mohan
>________________________________
> From: Mohan <[email protected]>
>To: "[email protected]"
><[email protected]>
>Sent: Friday, June 21, 2013 12:49 PM
>Subject: Re: [Openhpi-devel] New OpenHPI release
>
>
>
>Hello All,
>
>Today is the code freeze date for OpenHPI 3.2.1 release. Please go ahead and
>checkin the fixes that you want to see in this release. Future checkins will
>go into the next release.
>
>Thanks
>Mohan
>
>
>
>
>
>
>
>>________________________________
>> From: Mohan <[email protected]>
>>To: "[email protected]"
>><[email protected]>
>>Sent: Tuesday, June 11, 2013 12:24 PM
>>Subject: Re: [Openhpi-devel] New OpenHPI release
>>
>>
>>
>>Hello All,
>>
>>This will be a stable release. We will call this release as 3.2.1. First
>>backport patch is checked in yesterday.
>>
>>Just
created a milestone called 3.2.1 in the tracker. I will be going
through the bugs that are fixed in 3.2.1 and moving the milestones in
the bugs while creating the changelog for the release.
>>
>>If you
have any bugs that are to be fixed for this release, please go ahead and
fix them in the trunk, 3.2.x branch and set the milestone to 3.2.1.
>>
>>Let's have a tentative code freeze date and release date. How about June 21,
>>2013 for code freeze and July 1, 2013 for release?
>>
>>Thanks
>>Mohan
>>
>>
>>
>>>________________________________
>>> From: Rick Lane <[email protected]>
>>>To: Mohan <[email protected]>; [email protected]
>>>Sent: Monday, June 10, 2013 8:04 AM
>>>Subject: Re: [Openhpi-devel] New OpenHPI release
>>>
>>>
>>>
>>>I think this would be good, assume it would be "supported" release (i.e not
>>>development).
>>>I have updated 3.2.0 with at least 4 patches now and it would be
good to get back to official delivery.
>>>
>>>
>>>
>>>RICK LANE
>>>ALCATEL-LUCENT
>>>Room 6C-402
>>>2000 Lucent Ln.
>>>Naperville, IL 60563-1443
>>>T: 630-224-4986
>>>[email protected]
On 6/7/2013 3:35 PM, Mohan wrote:
>>>
>>>Hello All,
>>>>
>>>>
>>>>Since the last release in Aug, 2012 we have had many bug fixes, including
>>>>security fixes.
>>>>Looks like there are no major new features.
>>>>
>>>>
>>>>
>>>>At last sourceforge updated openhpi project also to the new platform. Now
>>>>all our bug numbers have changed among other things.
>>>>In the old system the bug numbers were shared among the projects. In the
>>>>new system each project has its own serial list of bugs. Many of our old
>>>>scripts break too as the field names are changed (for example, component is
>>>>called a label now) among other things. We are working on fixing them and
>>>>creating a mapping file etc
>>>>
>>>>
>>>>
>>>>Considering the above and the need to create a new release, suggest we make
>>>>a release from the 3.2.x branch called 3.2.1. This will not affect the
>>>>trunk. We could make the release in July. What do you think?
>>>>
>>>>
>>>>Regards
>>>>Mohan
>>>>
>>>>
>>>>
>>>>------------------------------------------------------------------------------
How ServiceNow helps IT people transform IT departments:
1. A cloud service to automate IT design, transition and operations
2. Dashboards that offer high-level views of enterprise services
3. A single system of record for all IT processes
http://p.sf.net/sfu/servicenow-d2d-j
>>>>
>>>>
>>>>_______________________________________________
Openhpi-devel mailing list [email protected]
https://lists.sourceforge.net/lists/listinfo/openhpi-devel
>>>
>>>
>>>
>>
>>
>
>------------------------------------------------------------------------------
This SF.net email is sponsored by Windows:
Build for Windows Store.
http://p.sf.net/sfu/windows-dev2dev
_______________________________________________
Openhpi-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/openhpi-devel
