I have added the IS feature categories into the 4.0.3 release. Rajika
On Wed, Oct 31, 2012 at 11:20 AM, Dileepa Jayakody <dile...@wso2.com> wrote: > > > On Wed, Oct 31, 2012 at 10:44 AM, Rajika Kumarasiri <raj...@wso2.com>wrote: > >> I noticed that the current 4.0.3 feature is a copy from the 4.0.2, so it >> has all the released 4.0.2 features defined. Is this intentional or should >> it be fixed ? If this is indented behavior will that not build up the p2 >> repo size each time we do a release ? >> >> Yes this is intended, we followed the same flow since 4.0.0 release. > With 4.0.0 only AM got released so it only had 1 product category in the > repo. > With 4.0.1 the new set of product categories were added with updated > feature versions and the AM category already released was also included. > > Since not all the products are getting released in chunk releases, the > features & products already got released in prev. chunk releases should be > in the p2-repo so users can install them as well. If any of their features > got updated we need to update feature versions. > > So as a summary what needs to be done is; > 1. Add new features or update features that are going to be released in > 4.0.3 > 2. Add new product categories that are going to be released. eg: IS > category > > > *Note: With regard to Product categories* > > As per the discussion we had on current feature categorization we came to > a conclusion that a product category should be defined in a clear and > usable manner so a user can clearly identify the list of required features > to install a product/product combination. Not all features in the > p2-profile-gen need to be added to the category. Composite features > aggregating required set of sub-features should be used as a best practice. > This will become a form of sub-categories for the users in installing > features. > eg: when adding event features, don't add event.ui, event.common, > event.server separately instead add the composite feature. > > Like wise every product category in the current p2-repo should be revised > to remove unwanted features and include composite features in a logical > manner. We need to go forward with a process for this where each product > team need to restructure their categories in a meaningful way for the > carbon users installing features. Will need help from each product team for > this. > > Thanks, > Dileepa > > > > > Rajika >> >> On Wed, Oct 31, 2012 at 1:32 AM, Dileepa Jayakody <dile...@wso2.com>wrote: >> >>> Hi IS team, >>> >>> Can we please add IS category to 4.0.3 p2 repo pom? This is vital to >>> test IS feature group on top other carbon products. If you need further >>> clarifications on defining the feature category please let me know. >>> >>> Thanks, >>> Dileepa >>> >>> -- >>> Dileepa Jayakody, >>> Software Engineer, WSO2 Inc. >>> Lean . Enterprise . Middleware >>> >>> Mobile : +94777-857616 >>> >>> >>> _______________________________________________ >>> Dev mailing list >>> Dev@wso2.org >>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>> >>> >> > > > -- > Dileepa Jayakody, > Software Engineer, WSO2 Inc. > Lean . Enterprise . Middleware > > Mobile : +94777-857616 > >
_______________________________________________ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
