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: [email protected]
28,ZhongGuanCun Software Park,No.8 Dong Bei Wang West Road, Haidian
District Beijing P.R.China 100193


                                                                           
             Venkateswara R                                                
             Puvvada                                                       
             <[email protected].                                          To 
             com>                      Li Gong Liu/China/IBM@IBMCN         
                                                                        cc 
             2011-03-04 13:13          [email protected]           
                                                                   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 <[email protected]>
To:        [email protected]
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