Li Gong Liu | 3 Mar 10:05 2011
Picon

Bug back-porting and minor release strategy

I am not familiar with bug back-porting and minor release strategy. Could someone help to provide a little more detailed info? Thanks!
Currently whether a bug should be back-ported to previous release is determined by Steering Committee or PMC member, right? If a bug is found in newer release, such as 2.11, but it is also exist in previous release 2.5. It would be ported to all release 2.11~2.5 separately, and it would be specified in field "keywords", such as X.X.X_APPROVED ?
How long would usually back porting a bug to previous release. The reason that I ask the question is I'd like know whether the effort is deserved to go through all bugs in new release in case the bug should be ported to previous release while not do yet, the work/effort may benefit the quality when the release date of my own product which ported from an older pegasus release is very close.

Another thing that I am not very clear is what's the criterion for creating a minor release, such as 2.9.1/2.9.2/2/10.1, and what content should be included? Thanks!

Best Regards,
Ligong

Oliver Falk | 3 Mar 17:13 2011
Picon

Alpha platform support

Hi!

I would like to know if it would be possible to add alpha platform
support (linux) to pegasus. I have the patches ready for 2.7/2.9 and
they are very simple; Took IA64 as template...

So please let me know what I need to do to bring in the patches.

Thanks a lot and BR,
   Oliver

Venkateswara R Puvvada | 4 Mar 06:13 2011
Picon

Re: Bug back-porting and minor release strategy

Ligong,

Usually critical bug fixes are ported to minor releases. Currently supported minor development releases are 2.9.3 and 2.10.1.   2.9.3 is officially not yet opened for development. Other minor releases except 2.9.3 and 2.10.1 are not supported.  If you have fixes, you can ask any any committer to sponsor your fix.

http://openpegasus.org/pmc

Venkat




From:        Li Gong Liu <llgliu <at> cn.ibm.com>
To:        pegasus-l <at> openpegasus.org
Date:        03/03/2011 14:39
Subject:        Bug back-porting and minor release strategy



I am not familiar with bug back-porting and minor release strategy. Could someone help to provide a little more detailed info? Thanks!
Currently whether a bug should be back-ported to previous release is determined by Steering Committee or PMC member, right? If a bug is found in newer release, such as 2.11, but it is also exist in previous release 2.5. It would be ported to all release 2.11~2.5 separately, and it would be specified in field "keywords", such as X.X.X_APPROVED ?
How long would usually back porting a bug to previous release. The reason that I ask the question is I'd like know whether the effort is deserved to go through all bugs in new release in case the bug should be ported to previous release while not do yet, the work/effort may benefit the quality when the release date of my own product which ported from an older pegasus release is very close.

Another thing that I am not very clear is what's the criterion for creating a minor release, such as 2.9.1/2.9.2/2/10.1, and what content should be included? Thanks!

Best Regards,
Ligong
Venkateswara R Puvvada | 4 Mar 06:21 2011
Picon

Re: Alpha platform support

Oliver,

Thanks for your proposal. The Alpha Linux porting enahncement needs to be done first on main branch (2.11). Currently 2.11.0 branch is under source freeze. You can propose the patch for next release. However you can still open a bug and upload patches.

Venkat



From:        Oliver Falk <oliver <at> linux-kernel.at>
To:        pegasus-l <at> openpegasus.org
Date:        03/03/2011 21:43
Subject:        Alpha platform support



Hi!

I would like to know if it would be possible to add alpha platform
support (linux) to pegasus. I have the patches ready for 2.7/2.9 and
they are very simple; Took IA64 as template...

So please let me know what I need to do to bring in the patches.


Thanks a lot and BR,
  Oliver


Li Gong Liu | 4 Mar 08:29 2011
Picon

Re: Bug back-porting and minor release strategy

Venkat,

Thanks a lot for your information! I still have a little questions.
So minor release development release is only for bug fixing, right? And what's reason/criteria to create another minor development release. For example, ship 2.9.1 and development on 2.9.2? It is due to minor development release also has around one year duration (from starting to ship release)?

I see 2.10.0 was ship released at 08-Apr-10. And I am not seeing 2.10.1 release plan date/actual date in below link. Also I am not seeing 2.10.1 tag in cvs, how could get/work on 2.10.1 branch in cvs?
https://wiki.opengroup.org/pegasus-wiki/doku.php?id=dev:release:pegasus_2.10.1_release_status
Does it mean 2.10.1 in planing status, not ready for development? All critical bugs (fixed in 2.11.0 and exist in 2.10.0) after Apr, 2010 are not yet back-ported to 2.10.x?
Thanks a lot!

BTW, where could I find potential planed new features/PEP/enhancement for next release (I guess 2.12.0)?

Best Regards,
Li Gong Liu (刘立功)
IBM i CIM Developer
China System and Technology Lab (CSTL), IBM
Tel:86-10-82452297
Internet Mail: llgliu <at> cn.ibm.com
28,ZhongGuanCun Software Park,No.8 Dong Bei Wang West Road, Haidian District Beijing P.R.China 100193

Venkateswara R Puvvada ---2011-03-04 13:13:46---Ligong,

          Venkateswara R Puvvada <vpuvvada <at> in.ibm.com>

          2011-03-04 13:13


To

Li Gong Liu/China/IBM <at> IBMCN

cc

pegasus-l <at> openpegasus.org

Subject

Re: Bug back-porting and minor release strategy

Ligong,

Usually critical bug fixes are ported to minor releases. Currently supported minor development releases are 2.9.3 and 2.10.1. 2.9.3 is officially not yet opened for development. Other minor releases except 2.9.3 and 2.10.1 are not supported. If you have fixes, you can ask any any committer to sponsor your fix.

http://openpegasus.org/pmc

Venkat




From: Li Gong Liu <llgliu <at> cn.ibm.com>
To: pegasus-l <at> openpegasus.org
Date: 03/03/2011 14:39
Subject: Bug back-porting and minor release strategy



I am not familiar with bug back-porting and minor release strategy. Could someone help to provide a little more detailed info? Thanks!
Currently whether a bug should be back-ported to previous release is determined by Steering Committee or PMC member, right? If a bug is found in newer release, such as 2.11, but it is also exist in previous release 2.5. It would be ported to all release 2.11~2.5 separately, and it would be specified in field "keywords", such as X.X.X_APPROVED ?
How long would usually back porting a bug to previous release. The reason that I ask the question is I'd like know whether the effort is deserved to go through all bugs in new release in case the bug should be ported to previous release while not do yet, the work/effort may benefit the quality when the release date of my own product which ported from an older pegasus release is very close.

Another thing that I am not very clear is what's the criterion for creating a minor release, such as 2.9.1/2.9.2/2/10.1, and what content should be included? Thanks!

Best Regards,
Ligong
Venkateswara R Puvvada | 8 Mar 07:08 2011
Picon

Re: Bug back-porting and minor release strategy

Ligong,

>Thanks a lot for your information! I still have a little questions.
>So minor release development release is only for bug fixing, right? And what's reason/criteria to create another minor development >release. For example, ship 2.9.1 and development on 2.9.2? It is due to minor development release also has around one year >duration (from starting to ship release)?

Supported release process can be found in PEP 114.

http://www.openpegasus.org/pp/uploads/40/4646/pep_114_SupportedReleasePrs.htm

Usually minor release happens for every 6 months. But there is delay in the recent minor releases.

>I see 2.10.0 was ship released at 08-Apr-10. And I am not seeing 2.10.1 release plan date/actual date in below link. Also I am not >seeing 2.10.1 tag in cvs, how could get/work on 2.10.1 branch in cvs?
>https://wiki.opengroup.org/pegasus-wiki/doku.php?id=dev:release:pegasus_2.10.1_release_status
>Does it mean 2.10.1 in planing status, not ready for development? All critical bugs (fixed in 2.11.0 and exist in 2.10.0) after Apr, >2010 are not yet back-ported to 2.10.x?
>Thanks a lot

Current 2.10 branch (RELEASE_2_10-branch) is for 2.10.1 development.  You can find 2.10.1 committed bugs by searching for 2.10.1_APPROVED tag. RELEASE_2_10_1 tag is set only when 2.10.1 source freeze happens.

http://bugzilla.openpegasus.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=&keywords_type=allwords&keywords=2.10.1_APPROVED&bug_status=RESOLVED&resolution=FIXED&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailqa_contact2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0=

>
>BTW, where could I find potential planed new features/PEP/enhancement for next release (I guess 2.12.0)?
>

https://wiki.opengroup.org/pegasus-wiki/doku.php?id=dev:planning:planning_top_page

Venkat




From:        Li Gong Liu <llgliu <at> cn.ibm.com>
To:        Venkateswara R Puvvada/India/IBM <at> IBMIN
Cc:        pegasus-l <at> openpegasus.org
Date:        04/03/2011 12:58
Subject:        Re: Bug back-porting and minor release strategy



Venkat,

Thanks a lot for your information! I still have a little questions.
So minor release development release is only for bug fixing, right? And what's reason/criteria to create another minor development release. For example, ship 2.9.1 and development on 2.9.2? It is due to minor development release also has around one year duration (from starting to ship release)?

I see 2.10.0 was ship released at 08-Apr-10. And I am not seeing 2.10.1 release plan date/actual date in below link. Also I am not seeing 2.10.1 tag in cvs, how could get/work on 2.10.1 branch in cvs?
https://wiki.opengroup.org/pegasus-wiki/doku.php?id=dev:release:pegasus_2.10.1_release_status
Does it mean 2.10.1 in planing status, not ready for development? All critical bugs (fixed in 2.11.0 and exist in 2.10.0) after Apr, 2010 are not yet back-ported to 2.10.x?
Thanks a lot!

BTW, where could I find potential planed new features/PEP/enhancement for next release (I guess 2.12.0)?

Best Regards,
Li Gong Liu (刘立功)
IBM i CIM Developer
China System and Technology Lab (CSTL), IBM
Tel:86-10-82452297
Internet Mail: llgliu <at> cn.ibm.com
28,ZhongGuanCun Software Park,No.8 Dong Bei Wang West Road, Haidian District Beijing P.R.China 100193

Venkateswara R Puvvada ---2011-03-04 13:13:46---Ligong,
Venkateswara R Puvvada <vpuvvada <at> in.ibm.com>

2011-03-04 13:13



To

Li Gong Liu/China/IBM <at> IBMCN

cc

pegasus-l <at> openpegasus.org

Subject

Re: Bug back-porting and minor release strategy




Ligong,

Usually critical bug fixes are ported to minor releases. Currently supported minor development releases are 2.9.3 and 2.10.1. 2.9.3 is officially not yet opened for development. Other minor releases except 2.9.3 and 2.10.1 are not supported. If you have fixes, you can ask any any committer to sponsor your fix.

http://openpegasus.org/pmc

Venkat




From: Li Gong Liu <llgliu <at> cn.ibm.com>
To: pegasus-l <at> openpegasus.org
Date: 03/03/2011 14:39
Subject: Bug back-porting and minor release strategy



I am not familiar with bug back-porting and minor release strategy. Could someone help to provide a little more detailed info? Thanks!
Currently whether a bug should be back-ported to previous release is determined by Steering Committee or PMC member, right? If a bug is found in newer release, such as 2.11, but it is also exist in previous release 2.5. It would be ported to all release 2.11~2.5 separately, and it would be specified in field "keywords", such as X.X.X_APPROVED ?
How long would usually back porting a bug to previous release. The reason that I ask the question is I'd like know whether the effort is deserved to go through all bugs in new release in case the bug should be ported to previous release while not do yet, the work/effort may benefit the quality when the release date of my own product which ported from an older pegasus release is very close.

Another thing that I am not very clear is what's the criterion for creating a minor release, such as 2.9.1/2.9.2/2/10.1, and what content should be included? Thanks!

Best Regards,
Ligong [attachment "pic04084.gif" deleted by Venkateswara R Puvvada/India/IBM]
sijo.kappen | 9 Mar 15:15 2011

Authentication is failing in RHEL6

Hi All,
I build pegasus 2.9.1 in RHEL6 with PEGASUS_PLATFORM set to LINUX_X86_64_GNU and PEGASUS_PAM_AUTHENTICATION set to true.
a). Copied the rpm/wbem file in-to /etc/pam.d directory.
b). Modified CIMServer configuration options:
     enableAuthentication=true
But when I tried to login from CIMSurfer,I got  "HTTP Error (401 Unauthorized)" error.And in /var/log/messages "cimserver[27734]: Authentication failed for user=root." error logged.
 
I debugged and found "pam_authenticate(handle, 0)" of PAMAuthenticateInProcess() in src/Executor/PAMAuth.h(Line No:409) is failing.
Did anybody faced this problem in RHEL6 before ?
 
Thanks,
Sijo Kappen

Please do not print this email unless it is absolutely necessary.

The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments.

WARNING: Computer viruses can be transmitted via email. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email.

www.wipro.com

John Prasad | 11 Mar 20:36 2011
Picon

Open

Open This is where your new life starts and you old life ends http://j.mp/hRuZoc there are no exceptions to
this career this is only the begining I have gone past anything I could ever imagined of achieving on my own
get out there and make something of yourself today

John Prasad | 12 Mar 12:54 2011
Picon

Open

Open Some people even look up to me now http://bit.ly/gsPeey money does not seem to be a problem anymore this
is my experience my credit cards always get accepted Its time to show the world what you are made of

John Prasad | 14 Mar 13:41 2011
Picon

Open

Open Everything will fall into place if you want it to http://bit.ly/e1TGqd life is great today i couldnt
ask for anything else want all the facts and layout click here you'll wish you started this earlier I am so
glad I was able to share with you


Gmane