All product POMs & distribution versions must change On Mon, Jun 27, 2011 at 5:03 PM, Amila Maha Arachchi <ami...@wso2.com>wrote:
> > > On Mon, Jun 27, 2011 at 4:56 PM, Afkham Azeez <az...@wso2.com> wrote: > >> Yes, only if something changes we will introduce new versions. Otherwise, >> we will stick with old versions for components, features etc. >> > > Versioning for components and features are clear. > > But, what about the manager/1.5.1/modules/features..... For example > org.wso2.manager.server.feature > > At the moment we dont have a versioned folder such as 3.2.0 or 3.2.1 as in > components or features. What if we do changes in them? How should we > proceed? > >> >> On Mon, Jun 27, 2011 at 4:50 PM, Muhammed Shariq <sha...@wso2.com> wrote: >> >>> If an artifact hasn't changed then the version should be 1.1.0 for >>> stratos components. Only if we are branching after 3.2.0, then the version >>> should 3.2.1 and 1.5.1 for stratos. So its not wrong to have 1.1.0 artifacts >>> IMO ... in fact the unchanged artifacts should be referred to as 1.1.0 ? >>> >>> On Mon, Jun 27, 2011 at 4:44 PM, Amila Maha Arachchi <ami...@wso2.com>wrote: >>> >>>> Hi all, >>>> >>>> I created 3.2.1 branches for some stratos components and then I had to >>>> change the respective versions in >>>> manager/1.5.1/modules/features/org.wso2.stratos.manager.server.feature and >>>> ui.feature. There I found out their versions are still 1.1.0. This should >>>> be >>>> 1.5.1. Azeez too confirmed this in an offline chat. >>>> >>>> When I had a look at appserver's service poms also I observed this. >>>> >>>> I am confused over these version numbers. Can somebody provide clear >>>> instructions on this. >>>> >>>> If the correct version is 1.5.1, each and every service has to make this >>>> change. >>>> >>>> Thanks, >>>> AmilaM. >>>> >>>> _______________________________________________ >>>> Stratos-dev mailing list >>>> stratos-...@wso2.org >>>> https://wso2.org/cgi-bin/mailman/listinfo/stratos-dev >>>> >>>> >>> >>> _______________________________________________ >>> Carbon-dev mailing list >>> Carbon-dev@wso2.org >>> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev >>> >>> >> >> >> -- >> *Afkham Azeez* >> Director of Architecture; WSO2, Inc.; http://wso2.com >> Member; Apache Software Foundation; http://www.apache.org/ >> * <http://www.apache.org/>** >> email: **az...@wso2.com* <az...@wso2.com>* cell: +94 77 3320919 >> blog: **http://blog.afkham.org* <http://blog.afkham.org>* >> twitter: **http://twitter.com/afkham_azeez*<http://twitter.com/afkham_azeez> >> * >> linked-in: **http://lk.linkedin.com/in/afkhamazeez* >> * >> * >> *Lean . Enterprise . Middleware* >> >> > -- *Afkham Azeez* Director of Architecture; WSO2, Inc.; http://wso2.com Member; Apache Software Foundation; http://www.apache.org/ * <http://www.apache.org/>** email: **az...@wso2.com* <az...@wso2.com>* cell: +94 77 3320919 blog: **http://blog.afkham.org* <http://blog.afkham.org>* twitter: **http://twitter.com/afkham_azeez*<http://twitter.com/afkham_azeez> * linked-in: **http://lk.linkedin.com/in/afkhamazeez* * * *Lean . Enterprise . Middleware*
_______________________________________________ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
