Re: [VOTE] PROJECTMGR in upcoming release
Locked
123
123
Re: [VOTE] PROJECTMGR in upcoming release
 
|
Jacopo,
Back then there were already strong objections to excluding components from the release. I recall that Hans also wanted to keep the SCRUM component in the release, as well as there were proponents for BIRT and other components. These are good additions to the feature set of OFBiz and may be in use already by community members. It would be best that you solicit the advice of the entire community before a decision on excluding components from any release is taken. This affects more participants in this project than just you and the committers. Regards, Pierre Smits *ORRTIZ.COM <http://www.orrtiz.com>* Services & Solutions for Cloud- Based Manufacturing, Professional Services and Retail & Trade http://www.orrtiz.com On Tue, Sep 30, 2014 at 11:49 AM, Jacopo Cappellato < [hidden email]> wrote: > Ok, got it. > The release process that the OFBiz community is following is based on a > feature freeze phase, that for the 13.07 branch started more than one year > ago, during which only bug fixes are backported. > This is done in order to stabilize the branch before an official release > is done. Since the "projectmgr" component has never been part of the 13.07 > branch then it may be unsafe to include it now just before the release is > issued. It would be better to discuss its inclusion in the upcoming new > release branch where it could be stabilized and bug fixed. > > Regards, > > Jacopo > |
|
|
Why not deploy it as another hot-deploy component? Is it considered a
"core" ERP component? On Tue, Sep 30, 2014 at 2:59 AM, Pierre Smits <[hidden email]> wrote: > Jacopo, > > Back then there were already strong objections to excluding components from > the release. I recall that Hans also wanted to keep the SCRUM component in > the release, as well as there were proponents for BIRT and other > components. > > These are good additions to the feature set of OFBiz and may be in use > already by community members. It would be best that you solicit the advice > of the entire community before a decision on excluding components from any > release is taken. This affects more participants in this project than just > you and the committers. > > Regards, > > Pierre Smits > > *ORRTIZ.COM <http://www.orrtiz.com>* > Services & Solutions for Cloud- > Based Manufacturing, Professional > Services and Retail & Trade > http://www.orrtiz.com > > On Tue, Sep 30, 2014 at 11:49 AM, Jacopo Cappellato < > [hidden email]> wrote: > > > Ok, got it. > > The release process that the OFBiz community is following is based on a > > feature freeze phase, that for the 13.07 branch started more than one > year > > ago, during which only bug fixes are backported. > > This is done in order to stabilize the branch before an official release > > is done. Since the "projectmgr" component has never been part of the > 13.07 > > branch then it may be unsafe to include it now just before the release is > > issued. It would be better to discuss its inclusion in the upcoming new > > release branch where it could be stabilized and bug fixed. > > > > Regards, > > > > Jacopo > > > |
Re: [VOTE] PROJECTMGR in upcoming release
|
|
It would be for me since it is one of the components that I want to use.
Perhaps the more knowledgeable people might want to share a bit more of the background of the feature. Is it in 12.xx.xx? Is it currently in the 13.07 branch and therefor currently part of the 13.07 versions that people have put in production or is it just in the trunk that people are putting into production? What are the issues that need to be addressed before it is "stabilized and bug fixed"? Do any of these issues pose a significant risk to the stability of the rest of the functionality? Is anyone using it in production? What are their opinions of the state of the code and the degree of risk? Is anyone prepared to take on the task of getting it "stabilized and bug fixed" to a point where it can be safely included? What is the estimate of the minimum effort required? Ron On 30/09/2014 9:58 AM, Mike wrote: > Why not deploy it as another hot-deploy component? Is it considered a > "core" ERP component? > > On Tue, Sep 30, 2014 at 2:59 AM, Pierre Smits <[hidden email]> > wrote: > >> Jacopo, >> >> Back then there were already strong objections to excluding components from >> the release. I recall that Hans also wanted to keep the SCRUM component in >> the release, as well as there were proponents for BIRT and other >> components. >> >> These are good additions to the feature set of OFBiz and may be in use >> already by community members. It would be best that you solicit the advice >> of the entire community before a decision on excluding components from any >> release is taken. This affects more participants in this project than just >> you and the committers. >> >> Regards, >> >> Pierre Smits >> >> *ORRTIZ.COM <http://www.orrtiz.com>* >> Services & Solutions for Cloud- >> Based Manufacturing, Professional >> Services and Retail & Trade >> http://www.orrtiz.com >> >> On Tue, Sep 30, 2014 at 11:49 AM, Jacopo Cappellato < >> [hidden email]> wrote: >> >>> Ok, got it. >>> The release process that the OFBiz community is following is based on a >>> feature freeze phase, that for the 13.07 branch started more than one >> year >>> ago, during which only bug fixes are backported. >>> This is done in order to stabilize the branch before an official release >>> is done. Since the "projectmgr" component has never been part of the >> 13.07 >>> branch then it may be unsafe to include it now just before the release is >>> issued. It would be better to discuss its inclusion in the upcoming new >>> release branch where it could be stabilized and bug fixed. >>> >>> Regards, >>> >>> Jacopo >>> -- Ron Wheeler President Artifact Software Inc email: [hidden email] skype: ronaldmwheeler phone: 866-970-2435, ext 102 |
|
|
In reply to this post by Mike Z
See below:
On Tue, Sep 30, 2014 at 9:58 AM, Mike <[hidden email]> wrote: > Why not deploy it as another hot-deploy component? Is it considered a > "core" ERP component? > > I do not know about whether or not it is 'core', but the idea of deploying it as a hot-deploy component has merit. As I read Jacopo's remarks, it isn't so much a concern about whether or not the component in question ought to be included in OFBiz at all, but rather the concern is of the risk of including it at a late date in the release cycle (just before a scheduled release). As a developer, I know there would be major pushback by the development team against any manager asking to include a new 'feature' shortly before a scheduled release. We have a feature freeze in a release cycle for a reason. For any new feature, there needs to be a dialog between at least the senior developers and the management, and the users, about what the feature is, how it ought to work, &c., and that is a dialog that can not be rushed if you want a good product; if you work on adding a new feature even months before a release date, I can guarantee it will not be well thought out/designed/implemented. Even if the component being considered at the moment is 'reasonably' well conceived and much work has gone into developing it, if it has never been part of the 13.07 release, including it so close to the scheduled release is a recipe for 'problems', and possibly some sleepless nights and ulcers for whoever has to make it work. In my shop, we have a whole separate system on which new and proposed features are developed and tested thoroughly before that code is even considered for inclusion in our production systems. It is a test bed on which all interested parties can see new features in operation, in the context of the application, and learn about what is practicable and desirable. Sometimes, after working with it on dev, they see that trying to fully implement and deploy the new feature would be foolish and unnecessary; and this before major development effort has been invested. And sometimes, we collectively learn that the new feature is practicable and desirable, and at that point, we already have a prototype that can be used to quickly develop it to a point where it can be deployed to production. Jacopo does say that "It would be better to discuss its inclusion in the upcoming new release branch where it could be stabilized and bug fixed." Myself, I would take that a step further in suggesting, borrowing from Mike's suggestion, that it ought to be available as something that can be used in a hot-deploy sandbox as it were: a method that, conceptually facilitates those interested in it to work with it, test in in their release, &c., but in such a way that it can not damage anything else in the application. It may be useful to look at how R handles these issues. There is R-core, and an R-core team, that is part of the main distribution (all packages included in an installation of it), and then there is CRAN (similar in concept to CPAN, for any Perl programmers out there - I hope it isn't considered blasphemy to talk about Perl in this forum ;-) ), to which all members of the R community can contribute their packages; analogous to components in the context of an application like OFBiz. CRAN has a QA protocol, which must be passed in order for an R package to be added to CRAN; something that assures users that their system will not be trashed if they instal a package available from CRAN. And, sometimes, the R core team decides that one of the packages on CRAN is so important and useful that they decide to add it to core (this doesn't happen often, but it does happen). So then, in the context of OFBiz, the first question becomes, can the hot-deploy support be used in a manner similar to a snadbox that protext the rest of the system from badly behaved code (NB: I am not implying anything about the code in the component in question now, but rather thinking in general terms for any new component anyone may want to contribute)? And then, the question becomes, what protocol can be used for promoting components from the 'sandbox' to incorporation into the 'core release'; whatever you want to call it? Cheers Ted > On Tue, Sep 30, 2014 at 2:59 AM, Pierre Smits <[hidden email]> > wrote: > > > Jacopo, > > > > Back then there were already strong objections to excluding components > from > > the release. I recall that Hans also wanted to keep the SCRUM component > in > > the release, as well as there were proponents for BIRT and other > > components. > > > > These are good additions to the feature set of OFBiz and may be in use > > already by community members. It would be best that you solicit the > advice > > of the entire community before a decision on excluding components from > any > > release is taken. This affects more participants in this project than > just > > you and the committers. > > > > Regards, > > > > Pierre Smits > > > > *ORRTIZ.COM <http://www.orrtiz.com>* > > Services & Solutions for Cloud- > > Based Manufacturing, Professional > > Services and Retail & Trade > > http://www.orrtiz.com > > > > On Tue, Sep 30, 2014 at 11:49 AM, Jacopo Cappellato < > > [hidden email]> wrote: > > > > > Ok, got it. > > > The release process that the OFBiz community is following is based on a > > > feature freeze phase, that for the 13.07 branch started more than one > > year > > > ago, during which only bug fixes are backported. > > > This is done in order to stabilize the branch before an official > release > > > is done. Since the "projectmgr" component has never been part of the > > 13.07 > > > branch then it may be unsafe to include it now just before the release > is > > > issued. It would be better to discuss its inclusion in the upcoming new > > > release branch where it could be stabilized and bug fixed. > > > > > > Regards, > > > > > > Jacopo > > > > > > -- R.E.(Ted) Byers, Ph.D.,Ed.D. [hidden email] |
Re: [VOTE] PROJECTMGR in upcoming release
|
|
In reply to this post by Ron Wheeler
Ron, All,
For an overview of special purpose components included in the 12.x releases, see http://svn.apache.org/viewvc/ofbiz/branches/release12.04/specialpurpose/ For an overview of the special purpose components in the 13.x branch, see: http://svn.apache.org/viewvc/ofbiz/branches/release13.07/specialpurpose/ Regards, Pierre Smits *ORRTIZ.COM <http://www.orrtiz.com>* Services & Solutions for Cloud- Based Manufacturing, Professional Services and Retail & Trade http://www.orrtiz.com On Tue, Sep 30, 2014 at 4:39 PM, Ron Wheeler <[hidden email] > wrote: > It would be for me since it is one of the components that I want to use. > > Perhaps the more knowledgeable people might want to share a bit more of > the background of the feature. > Is it in 12.xx.xx? > > Is it currently in the 13.07 branch and therefor currently part of the > 13.07 versions that people have put in production or is it just in the > trunk that people are putting into production? > > What are the issues that need to be addressed before it is "stabilized and > bug fixed"? > Do any of these issues pose a significant risk to the stability of the > rest of the functionality? > > Is anyone using it in production? What are their opinions of the state of > the code and the degree of risk? > > Is anyone prepared to take on the task of getting it "stabilized and bug > fixed" to a point where it can be safely included? > What is the estimate of the minimum effort required? > > Ron > > > On 30/09/2014 9:58 AM, Mike wrote: > >> Why not deploy it as another hot-deploy component? Is it considered a >> "core" ERP component? >> >> On Tue, Sep 30, 2014 at 2:59 AM, Pierre Smits <[hidden email]> >> wrote: >> >> Jacopo, >>> >>> Back then there were already strong objections to excluding components >>> from >>> the release. I recall that Hans also wanted to keep the SCRUM component >>> in >>> the release, as well as there were proponents for BIRT and other >>> components. >>> >>> These are good additions to the feature set of OFBiz and may be in use >>> already by community members. It would be best that you solicit the >>> advice >>> of the entire community before a decision on excluding components from >>> any >>> release is taken. This affects more participants in this project than >>> just >>> you and the committers. >>> >>> Regards, >>> >>> Pierre Smits >>> >>> *ORRTIZ.COM <http://www.orrtiz.com>* >>> Services & Solutions for Cloud- >>> Based Manufacturing, Professional >>> Services and Retail & Trade >>> http://www.orrtiz.com >>> >>> On Tue, Sep 30, 2014 at 11:49 AM, Jacopo Cappellato < >>> [hidden email]> wrote: >>> >>> Ok, got it. >>>> The release process that the OFBiz community is following is based on a >>>> feature freeze phase, that for the 13.07 branch started more than one >>>> >>> year >>> >>>> ago, during which only bug fixes are backported. >>>> This is done in order to stabilize the branch before an official release >>>> is done. Since the "projectmgr" component has never been part of the >>>> >>> 13.07 >>> >>>> branch then it may be unsafe to include it now just before the release >>>> is >>>> issued. It would be better to discuss its inclusion in the upcoming new >>>> release branch where it could be stabilized and bug fixed. >>>> >>>> Regards, >>>> >>>> Jacopo >>>> >>>> > > -- > Ron Wheeler > President > Artifact Software Inc > email: [hidden email] > skype: ronaldmwheeler > phone: 866-970-2435, ext 102 > > |
Re: [VOTE] PROJECTMGR in upcoming release
|
|
In reply to this post by Ron Wheeler
Yes, I also have a vested interest in keeping this (PROJECTMGR) in the
releases. It is part of our ORRTIZ:COM solution portfolio for our customers and we use it internally. And I have contributed to the improvement of the component. We, at ORRTIZ:COM, even use an extension to the code base to ensure that it also works for fixed price and internal projects. This extension includes generating the gl transactions regarding the cost price of each hour registered regarding a project. We also use the LDAP component to connect to our directory server (Apache Directory Server). Regards, Pierre Smits *ORRTIZ.COM <http://www.orrtiz.com>* Services & Solutions for Cloud- Based Manufacturing, Professional Services and Retail & Trade http://www.orrtiz.com On Tue, Sep 30, 2014 at 4:39 PM, Ron Wheeler <[hidden email] > wrote: > It would be for me since it is one of the components that I want to use. > > Perhaps the more knowledgeable people might want to share a bit more of > the background of the feature. > Is it in 12.xx.xx? > > Is it currently in the 13.07 branch and therefor currently part of the > 13.07 versions that people have put in production or is it just in the > trunk that people are putting into production? > > What are the issues that need to be addressed before it is "stabilized and > bug fixed"? > Do any of these issues pose a significant risk to the stability of the > rest of the functionality? > > Is anyone using it in production? What are their opinions of the state of > the code and the degree of risk? > > Is anyone prepared to take on the task of getting it "stabilized and bug > fixed" to a point where it can be safely included? > What is the estimate of the minimum effort required? > > Ron > > > On 30/09/2014 9:58 AM, Mike wrote: > >> Why not deploy it as another hot-deploy component? Is it considered a >> "core" ERP component? >> >> On Tue, Sep 30, 2014 at 2:59 AM, Pierre Smits <[hidden email]> >> wrote: >> >> Jacopo, >>> >>> Back then there were already strong objections to excluding components >>> from >>> the release. I recall that Hans also wanted to keep the SCRUM component >>> in >>> the release, as well as there were proponents for BIRT and other >>> components. >>> >>> These are good additions to the feature set of OFBiz and may be in use >>> already by community members. It would be best that you solicit the >>> advice >>> of the entire community before a decision on excluding components from >>> any >>> release is taken. This affects more participants in this project than >>> just >>> you and the committers. >>> >>> Regards, >>> >>> Pierre Smits >>> >>> *ORRTIZ.COM <http://www.orrtiz.com>* >>> Services & Solutions for Cloud- >>> Based Manufacturing, Professional >>> Services and Retail & Trade >>> http://www.orrtiz.com >>> >>> On Tue, Sep 30, 2014 at 11:49 AM, Jacopo Cappellato < >>> [hidden email]> wrote: >>> >>> Ok, got it. >>>> The release process that the OFBiz community is following is based on a >>>> feature freeze phase, that for the 13.07 branch started more than one >>>> >>> year >>> >>>> ago, during which only bug fixes are backported. >>>> This is done in order to stabilize the branch before an official release >>>> is done. Since the "projectmgr" component has never been part of the >>>> >>> 13.07 >>> >>>> branch then it may be unsafe to include it now just before the release >>>> is >>>> issued. It would be better to discuss its inclusion in the upcoming new >>>> release branch where it could be stabilized and bug fixed. >>>> >>>> Regards, >>>> >>>> Jacopo >>>> >>>> > > -- > Ron Wheeler > President > Artifact Software Inc > email: [hidden email] > skype: ronaldmwheeler > phone: 866-970-2435, ext 102 > > |
Re: [VOTE] PROJECTMGR in upcoming release
|
|
In reply to this post by Pierre Smits
It seems to be actively maintained on the trunk.
Is it just a matter of copying it to the release branch? Ron On 30/09/2014 2:20 PM, Pierre Smits wrote: > Ron, All, > > For an overview of special purpose components included in the 12.x > releases, see > http://svn.apache.org/viewvc/ofbiz/branches/release12.04/specialpurpose/ > > For an overview of the special purpose components in the 13.x branch, see: > http://svn.apache.org/viewvc/ofbiz/branches/release13.07/specialpurpose/ > > Regards, > > > Pierre Smits > > *ORRTIZ.COM <http://www.orrtiz.com>* > Services & Solutions for Cloud- > Based Manufacturing, Professional > Services and Retail & Trade > http://www.orrtiz.com > > On Tue, Sep 30, 2014 at 4:39 PM, Ron Wheeler <[hidden email] >> wrote: >> It would be for me since it is one of the components that I want to use. >> >> Perhaps the more knowledgeable people might want to share a bit more of >> the background of the feature. >> Is it in 12.xx.xx? >> >> Is it currently in the 13.07 branch and therefor currently part of the >> 13.07 versions that people have put in production or is it just in the >> trunk that people are putting into production? >> >> What are the issues that need to be addressed before it is "stabilized and >> bug fixed"? >> Do any of these issues pose a significant risk to the stability of the >> rest of the functionality? >> >> Is anyone using it in production? What are their opinions of the state of >> the code and the degree of risk? >> >> Is anyone prepared to take on the task of getting it "stabilized and bug >> fixed" to a point where it can be safely included? >> What is the estimate of the minimum effort required? >> >> Ron >> >> >> On 30/09/2014 9:58 AM, Mike wrote: >> >>> Why not deploy it as another hot-deploy component? Is it considered a >>> "core" ERP component? >>> >>> On Tue, Sep 30, 2014 at 2:59 AM, Pierre Smits <[hidden email]> >>> wrote: >>> >>> Jacopo, >>>> Back then there were already strong objections to excluding components >>>> from >>>> the release. I recall that Hans also wanted to keep the SCRUM component >>>> in >>>> the release, as well as there were proponents for BIRT and other >>>> components. >>>> >>>> These are good additions to the feature set of OFBiz and may be in use >>>> already by community members. It would be best that you solicit the >>>> advice >>>> of the entire community before a decision on excluding components from >>>> any >>>> release is taken. This affects more participants in this project than >>>> just >>>> you and the committers. >>>> >>>> Regards, >>>> >>>> Pierre Smits >>>> >>>> *ORRTIZ.COM <http://www.orrtiz.com>* >>>> Services & Solutions for Cloud- >>>> Based Manufacturing, Professional >>>> Services and Retail & Trade >>>> http://www.orrtiz.com >>>> >>>> On Tue, Sep 30, 2014 at 11:49 AM, Jacopo Cappellato < >>>> [hidden email]> wrote: >>>> >>>> Ok, got it. >>>>> The release process that the OFBiz community is following is based on a >>>>> feature freeze phase, that for the 13.07 branch started more than one >>>>> >>>> year >>>> >>>>> ago, during which only bug fixes are backported. >>>>> This is done in order to stabilize the branch before an official release >>>>> is done. Since the "projectmgr" component has never been part of the >>>>> >>>> 13.07 >>>> >>>>> branch then it may be unsafe to include it now just before the release >>>>> is >>>>> issued. It would be better to discuss its inclusion in the upcoming new >>>>> release branch where it could be stabilized and bug fixed. >>>>> >>>>> Regards, >>>>> >>>>> Jacopo >>>>> >>>>> >> -- >> Ron Wheeler >> President >> Artifact Software Inc >> email: [hidden email] >> skype: ronaldmwheeler >> phone: 866-970-2435, ext 102 >> >> -- Ron Wheeler President Artifact Software Inc email: [hidden email] skype: ronaldmwheeler phone: 866-970-2435, ext 102 |
Re: [VOTE] PROJECTMGR in upcoming release
|
|
In reply to this post by Pierre Smits
Are you using it with a 12.04 or 13.xx?
What work is required to get it into 13.07? Ron On 30/09/2014 3:06 PM, Pierre Smits wrote: > Yes, I also have a vested interest in keeping this (PROJECTMGR) in the > releases. It is part of our ORRTIZ:COM solution portfolio for our customers > and we use it internally. And I have contributed to the improvement of the > component. > > We, at ORRTIZ:COM, even use an extension to the code base to ensure that it > also works for fixed price and internal projects. This extension includes > generating the gl transactions regarding the cost price of each hour > registered regarding a project. > > We also use the LDAP component to connect to our directory server (Apache > Directory Server). > > Regards, > > Pierre Smits > > *ORRTIZ.COM <http://www.orrtiz.com>* > Services & Solutions for Cloud- > Based Manufacturing, Professional > Services and Retail & Trade > http://www.orrtiz.com > > On Tue, Sep 30, 2014 at 4:39 PM, Ron Wheeler <[hidden email] >> wrote: >> It would be for me since it is one of the components that I want to use. >> >> Perhaps the more knowledgeable people might want to share a bit more of >> the background of the feature. >> Is it in 12.xx.xx? >> >> Is it currently in the 13.07 branch and therefor currently part of the >> 13.07 versions that people have put in production or is it just in the >> trunk that people are putting into production? >> >> What are the issues that need to be addressed before it is "stabilized and >> bug fixed"? >> Do any of these issues pose a significant risk to the stability of the >> rest of the functionality? >> >> Is anyone using it in production? What are their opinions of the state of >> the code and the degree of risk? >> >> Is anyone prepared to take on the task of getting it "stabilized and bug >> fixed" to a point where it can be safely included? >> What is the estimate of the minimum effort required? >> >> Ron >> >> >> On 30/09/2014 9:58 AM, Mike wrote: >> >>> Why not deploy it as another hot-deploy component? Is it considered a >>> "core" ERP component? >>> >>> On Tue, Sep 30, 2014 at 2:59 AM, Pierre Smits <[hidden email]> >>> wrote: >>> >>> Jacopo, >>>> Back then there were already strong objections to excluding components >>>> from >>>> the release. I recall that Hans also wanted to keep the SCRUM component >>>> in >>>> the release, as well as there were proponents for BIRT and other >>>> components. >>>> >>>> These are good additions to the feature set of OFBiz and may be in use >>>> already by community members. It would be best that you solicit the >>>> advice >>>> of the entire community before a decision on excluding components from >>>> any >>>> release is taken. This affects more participants in this project than >>>> just >>>> you and the committers. >>>> >>>> Regards, >>>> >>>> Pierre Smits >>>> >>>> *ORRTIZ.COM <http://www.orrtiz.com>* >>>> Services & Solutions for Cloud- >>>> Based Manufacturing, Professional >>>> Services and Retail & Trade >>>> http://www.orrtiz.com >>>> >>>> On Tue, Sep 30, 2014 at 11:49 AM, Jacopo Cappellato < >>>> [hidden email]> wrote: >>>> >>>> Ok, got it. >>>>> The release process that the OFBiz community is following is based on a >>>>> feature freeze phase, that for the 13.07 branch started more than one >>>>> >>>> year >>>> >>>>> ago, during which only bug fixes are backported. >>>>> This is done in order to stabilize the branch before an official release >>>>> is done. Since the "projectmgr" component has never been part of the >>>>> >>>> 13.07 >>>> >>>>> branch then it may be unsafe to include it now just before the release >>>>> is >>>>> issued. It would be better to discuss its inclusion in the upcoming new >>>>> release branch where it could be stabilized and bug fixed. >>>>> >>>>> Regards, >>>>> >>>>> Jacopo >>>>> >>>>> >> -- >> Ron Wheeler >> President >> Artifact Software Inc >> email: [hidden email] >> skype: ronaldmwheeler >> phone: 866-970-2435, ext 102 >> >> -- Ron Wheeler President Artifact Software Inc email: [hidden email] skype: ronaldmwheeler phone: 866-970-2435, ext 102 |
Re: [VOTE] PROJECTMGR in upcoming release
|
|
Ron, All,
We use the latest released branch, meaning 12.x. We don't expose our customers to an unstable unreleased branch, that is still undergoing significant changes. But, we test our solutions against trunk. This enables us to identify issues and register them in JIRA. And supply patches when workload allows it. So yes, PROJECTMGR, SCRUM, etc work also in r13.x Regards, Pierre Smits *ORRTIZ.COM <http://www.orrtiz.com>* Services & Solutions for Cloud- Based Manufacturing, Professional Services and Retail & Trade http://www.orrtiz.com On Tue, Sep 30, 2014 at 10:22 PM, Ron Wheeler < [hidden email]> wrote: > Are you using it with a 12.04 or 13.xx? > What work is required to get it into 13.07? > > Ron > On 30/09/2014 3:06 PM, Pierre Smits wrote: > >> Yes, I also have a vested interest in keeping this (PROJECTMGR) in the >> releases. It is part of our ORRTIZ:COM solution portfolio for our >> customers >> and we use it internally. And I have contributed to the improvement of the >> component. >> >> We, at ORRTIZ:COM, even use an extension to the code base to ensure that >> it >> also works for fixed price and internal projects. This extension includes >> generating the gl transactions regarding the cost price of each hour >> registered regarding a project. >> >> We also use the LDAP component to connect to our directory server (Apache >> Directory Server). >> >> Regards, >> >> Pierre Smits >> >> *ORRTIZ.COM <http://www.orrtiz.com>* >> Services & Solutions for Cloud- >> Based Manufacturing, Professional >> Services and Retail & Trade >> http://www.orrtiz.com >> >> On Tue, Sep 30, 2014 at 4:39 PM, Ron Wheeler <rwheeler@artifact-software. >> com >> >>> wrote: >>> It would be for me since it is one of the components that I want to use. >>> >>> Perhaps the more knowledgeable people might want to share a bit more of >>> the background of the feature. >>> Is it in 12.xx.xx? >>> >>> Is it currently in the 13.07 branch and therefor currently part of the >>> 13.07 versions that people have put in production or is it just in the >>> trunk that people are putting into production? >>> >>> What are the issues that need to be addressed before it is "stabilized >>> and >>> bug fixed"? >>> Do any of these issues pose a significant risk to the stability of the >>> rest of the functionality? >>> >>> Is anyone using it in production? What are their opinions of the state of >>> the code and the degree of risk? >>> >>> Is anyone prepared to take on the task of getting it "stabilized and bug >>> fixed" to a point where it can be safely included? >>> What is the estimate of the minimum effort required? >>> >>> Ron >>> >>> >>> On 30/09/2014 9:58 AM, Mike wrote: >>> >>> Why not deploy it as another hot-deploy component? Is it considered a >>>> "core" ERP component? >>>> >>>> On Tue, Sep 30, 2014 at 2:59 AM, Pierre Smits <[hidden email]> >>>> wrote: >>>> >>>> Jacopo, >>>> >>>>> Back then there were already strong objections to excluding components >>>>> from >>>>> the release. I recall that Hans also wanted to keep the SCRUM component >>>>> in >>>>> the release, as well as there were proponents for BIRT and other >>>>> components. >>>>> >>>>> These are good additions to the feature set of OFBiz and may be in use >>>>> already by community members. It would be best that you solicit the >>>>> advice >>>>> of the entire community before a decision on excluding components from >>>>> any >>>>> release is taken. This affects more participants in this project than >>>>> just >>>>> you and the committers. >>>>> >>>>> Regards, >>>>> >>>>> Pierre Smits >>>>> >>>>> *ORRTIZ.COM <http://www.orrtiz.com>* >>>>> Services & Solutions for Cloud- >>>>> Based Manufacturing, Professional >>>>> Services and Retail & Trade >>>>> http://www.orrtiz.com >>>>> >>>>> On Tue, Sep 30, 2014 at 11:49 AM, Jacopo Cappellato < >>>>> [hidden email]> wrote: >>>>> >>>>> Ok, got it. >>>>> >>>>>> The release process that the OFBiz community is following is based on >>>>>> a >>>>>> feature freeze phase, that for the 13.07 branch started more than one >>>>>> >>>>>> year >>>>> >>>>> ago, during which only bug fixes are backported. >>>>>> This is done in order to stabilize the branch before an official >>>>>> release >>>>>> is done. Since the "projectmgr" component has never been part of the >>>>>> >>>>>> 13.07 >>>>> >>>>> branch then it may be unsafe to include it now just before the release >>>>>> is >>>>>> issued. It would be better to discuss its inclusion in the upcoming >>>>>> new >>>>>> release branch where it could be stabilized and bug fixed. >>>>>> >>>>>> Regards, >>>>>> >>>>>> Jacopo >>>>>> >>>>>> >>>>>> -- >>> Ron Wheeler >>> President >>> Artifact Software Inc >>> email: [hidden email] >>> skype: ronaldmwheeler >>> phone: 866-970-2435, ext 102 >>> >>> >>> > > -- > Ron Wheeler > President > Artifact Software Inc > email: [hidden email] > skype: ronaldmwheeler > phone: 866-970-2435, ext 102 > > |
Re: [VOTE] PROJECTMGR in upcoming release
|
|
So, as far as is known from Pierre's testing, there is no work required
to "stabilize and bug fix" the module prior to including it in 13.07.01? Anyone else have any comments on the work required to include it in 13.07.01? Ron On 30/09/2014 5:13 PM, Pierre Smits wrote: > Ron, All, > > We use the latest released branch, meaning 12.x. We don't expose our > customers to an unstable unreleased branch, that is still undergoing > significant changes. > > But, we test our solutions against trunk. This enables us to identify > issues and register them in JIRA. And supply patches when workload allows > it. > > So yes, PROJECTMGR, SCRUM, etc work also in r13.x > > Regards, > > Pierre Smits > > *ORRTIZ.COM <http://www.orrtiz.com>* > Services & Solutions for Cloud- > Based Manufacturing, Professional > Services and Retail & Trade > http://www.orrtiz.com > > On Tue, Sep 30, 2014 at 10:22 PM, Ron Wheeler < > [hidden email]> wrote: > >> Are you using it with a 12.04 or 13.xx? >> What work is required to get it into 13.07? >> >> Ron >> On 30/09/2014 3:06 PM, Pierre Smits wrote: >> >>> Yes, I also have a vested interest in keeping this (PROJECTMGR) in the >>> releases. It is part of our ORRTIZ:COM solution portfolio for our >>> customers >>> and we use it internally. And I have contributed to the improvement of the >>> component. >>> >>> We, at ORRTIZ:COM, even use an extension to the code base to ensure that >>> it >>> also works for fixed price and internal projects. This extension includes >>> generating the gl transactions regarding the cost price of each hour >>> registered regarding a project. >>> >>> We also use the LDAP component to connect to our directory server (Apache >>> Directory Server). >>> >>> Regards, >>> >>> Pierre Smits >>> >>> *ORRTIZ.COM <http://www.orrtiz.com>* >>> Services & Solutions for Cloud- >>> Based Manufacturing, Professional >>> Services and Retail & Trade >>> http://www.orrtiz.com >>> >>> On Tue, Sep 30, 2014 at 4:39 PM, Ron Wheeler <rwheeler@artifact-software. >>> com >>> >>>> wrote: >>>> It would be for me since it is one of the components that I want to use. >>>> >>>> Perhaps the more knowledgeable people might want to share a bit more of >>>> the background of the feature. >>>> Is it in 12.xx.xx? >>>> >>>> Is it currently in the 13.07 branch and therefor currently part of the >>>> 13.07 versions that people have put in production or is it just in the >>>> trunk that people are putting into production? >>>> >>>> What are the issues that need to be addressed before it is "stabilized >>>> and >>>> bug fixed"? >>>> Do any of these issues pose a significant risk to the stability of the >>>> rest of the functionality? >>>> >>>> Is anyone using it in production? What are their opinions of the state of >>>> the code and the degree of risk? >>>> >>>> Is anyone prepared to take on the task of getting it "stabilized and bug >>>> fixed" to a point where it can be safely included? >>>> What is the estimate of the minimum effort required? >>>> >>>> Ron >>>> >>>> >>>> On 30/09/2014 9:58 AM, Mike wrote: >>>> >>>> Why not deploy it as another hot-deploy component? Is it considered a >>>>> "core" ERP component? >>>>> >>>>> On Tue, Sep 30, 2014 at 2:59 AM, Pierre Smits <[hidden email]> >>>>> wrote: >>>>> >>>>> Jacopo, >>>>> >>>>>> Back then there were already strong objections to excluding components >>>>>> from >>>>>> the release. I recall that Hans also wanted to keep the SCRUM component >>>>>> in >>>>>> the release, as well as there were proponents for BIRT and other >>>>>> components. >>>>>> >>>>>> These are good additions to the feature set of OFBiz and may be in use >>>>>> already by community members. It would be best that you solicit the >>>>>> advice >>>>>> of the entire community before a decision on excluding components from >>>>>> any >>>>>> release is taken. This affects more participants in this project than >>>>>> just >>>>>> you and the committers. >>>>>> >>>>>> Regards, >>>>>> >>>>>> Pierre Smits >>>>>> >>>>>> *ORRTIZ.COM <http://www.orrtiz.com>* >>>>>> Services & Solutions for Cloud- >>>>>> Based Manufacturing, Professional >>>>>> Services and Retail & Trade >>>>>> http://www.orrtiz.com >>>>>> >>>>>> On Tue, Sep 30, 2014 at 11:49 AM, Jacopo Cappellato < >>>>>> [hidden email]> wrote: >>>>>> >>>>>> Ok, got it. >>>>>> >>>>>>> The release process that the OFBiz community is following is based on >>>>>>> a >>>>>>> feature freeze phase, that for the 13.07 branch started more than one >>>>>>> >>>>>>> year >>>>>> ago, during which only bug fixes are backported. >>>>>>> This is done in order to stabilize the branch before an official >>>>>>> release >>>>>>> is done. Since the "projectmgr" component has never been part of the >>>>>>> >>>>>>> 13.07 >>>>>> branch then it may be unsafe to include it now just before the release >>>>>>> is >>>>>>> issued. It would be better to discuss its inclusion in the upcoming >>>>>>> new >>>>>>> release branch where it could be stabilized and bug fixed. >>>>>>> >>>>>>> Regards, >>>>>>> >>>>>>> Jacopo >>>>>>> >>>>>>> >>>>>>> -- >>>> Ron Wheeler >>>> President >>>> Artifact Software Inc >>>> email: [hidden email] >>>> skype: ronaldmwheeler >>>> phone: 866-970-2435, ext 102 >>>> >>>> >>>> >> -- >> Ron Wheeler >> President >> Artifact Software Inc >> email: [hidden email] >> skype: ronaldmwheeler >> phone: 866-970-2435, ext 102 >> >> -- Ron Wheeler President Artifact Software Inc email: [hidden email] skype: ronaldmwheeler phone: 866-970-2435, ext 102 |
Re: [VOTE] PROJECTMGR in upcoming release
|
|
The fact that someone is using it in an older branch and testing it in trunk is not enough to guarantee it works well with 13.07; the trunk and 13.07 are very different codebases.
Additionally, the "projectmgr" component has 0 unit tests; I am not sure about about its stability, but for example comments in code like the following don't make me feel super confident: <!-- temporary disabled because it caused a db lock with the checkProjectMembership in projectpermission services --> One more point to note: since the component has not been in the 13.07 branch, it didn't undergo the 1-year long stabilization phase where only bug-fixes are backported: for example, one month ago, with revision 1618313, it was modified by a big commit to replace a series of Freemarker built-ins operation that we decided to not backport to 13.07 but only keep in the trunk. Jacopo On Sep 30, 2014, at 11:19 PM, Ron Wheeler <[hidden email]> wrote: > So, as far as is known from Pierre's testing, there is no work required to "stabilize and bug fix" the module prior to including it in 13.07.01? > > Anyone else have any comments on the work required to include it in 13.07.01? > > Ron > > On 30/09/2014 5:13 PM, Pierre Smits wrote: >> Ron, All, >> >> We use the latest released branch, meaning 12.x. We don't expose our >> customers to an unstable unreleased branch, that is still undergoing >> significant changes. >> >> But, we test our solutions against trunk. This enables us to identify >> issues and register them in JIRA. And supply patches when workload allows >> it. >> >> So yes, PROJECTMGR, SCRUM, etc work also in r13.x >> >> Regards, >> >> Pierre Smits >> >> *ORRTIZ.COM <http://www.orrtiz.com>* >> Services & Solutions for Cloud- >> Based Manufacturing, Professional >> Services and Retail & Trade >> http://www.orrtiz.com >> >> On Tue, Sep 30, 2014 at 10:22 PM, Ron Wheeler < >> [hidden email]> wrote: >> >>> Are you using it with a 12.04 or 13.xx? >>> What work is required to get it into 13.07? >>> >>> Ron >>> On 30/09/2014 3:06 PM, Pierre Smits wrote: >>> >>>> Yes, I also have a vested interest in keeping this (PROJECTMGR) in the >>>> releases. It is part of our ORRTIZ:COM solution portfolio for our >>>> customers >>>> and we use it internally. And I have contributed to the improvement of the >>>> component. >>>> >>>> We, at ORRTIZ:COM, even use an extension to the code base to ensure that >>>> it >>>> also works for fixed price and internal projects. This extension includes >>>> generating the gl transactions regarding the cost price of each hour >>>> registered regarding a project. >>>> >>>> We also use the LDAP component to connect to our directory server (Apache >>>> Directory Server). >>>> >>>> Regards, >>>> >>>> Pierre Smits >>>> >>>> *ORRTIZ.COM <http://www.orrtiz.com>* >>>> Services & Solutions for Cloud- >>>> Based Manufacturing, Professional >>>> Services and Retail & Trade >>>> http://www.orrtiz.com >>>> >>>> On Tue, Sep 30, 2014 at 4:39 PM, Ron Wheeler <rwheeler@artifact-software. >>>> com >>>> >>>>> wrote: >>>>> It would be for me since it is one of the components that I want to use. >>>>> >>>>> Perhaps the more knowledgeable people might want to share a bit more of >>>>> the background of the feature. >>>>> Is it in 12.xx.xx? >>>>> >>>>> Is it currently in the 13.07 branch and therefor currently part of the >>>>> 13.07 versions that people have put in production or is it just in the >>>>> trunk that people are putting into production? >>>>> >>>>> What are the issues that need to be addressed before it is "stabilized >>>>> and >>>>> bug fixed"? >>>>> Do any of these issues pose a significant risk to the stability of the >>>>> rest of the functionality? >>>>> >>>>> Is anyone using it in production? What are their opinions of the state of >>>>> the code and the degree of risk? >>>>> >>>>> Is anyone prepared to take on the task of getting it "stabilized and bug >>>>> fixed" to a point where it can be safely included? >>>>> What is the estimate of the minimum effort required? >>>>> >>>>> Ron >>>>> >>>>> >>>>> On 30/09/2014 9:58 AM, Mike wrote: >>>>> >>>>> Why not deploy it as another hot-deploy component? Is it considered a >>>>>> "core" ERP component? >>>>>> >>>>>> On Tue, Sep 30, 2014 at 2:59 AM, Pierre Smits <[hidden email]> >>>>>> wrote: >>>>>> >>>>>> Jacopo, >>>>>> >>>>>>> Back then there were already strong objections to excluding components >>>>>>> from >>>>>>> the release. I recall that Hans also wanted to keep the SCRUM component >>>>>>> in >>>>>>> the release, as well as there were proponents for BIRT and other >>>>>>> components. >>>>>>> >>>>>>> These are good additions to the feature set of OFBiz and may be in use >>>>>>> already by community members. It would be best that you solicit the >>>>>>> advice >>>>>>> of the entire community before a decision on excluding components from >>>>>>> any >>>>>>> release is taken. This affects more participants in this project than >>>>>>> just >>>>>>> you and the committers. >>>>>>> >>>>>>> Regards, >>>>>>> >>>>>>> Pierre Smits >>>>>>> >>>>>>> *ORRTIZ.COM <http://www.orrtiz.com>* >>>>>>> Services & Solutions for Cloud- >>>>>>> Based Manufacturing, Professional >>>>>>> Services and Retail & Trade >>>>>>> http://www.orrtiz.com >>>>>>> >>>>>>> On Tue, Sep 30, 2014 at 11:49 AM, Jacopo Cappellato < >>>>>>> [hidden email]> wrote: >>>>>>> >>>>>>> Ok, got it. >>>>>>> >>>>>>>> The release process that the OFBiz community is following is based on >>>>>>>> a >>>>>>>> feature freeze phase, that for the 13.07 branch started more than one >>>>>>>> >>>>>>>> year >>>>>>> ago, during which only bug fixes are backported. >>>>>>>> This is done in order to stabilize the branch before an official >>>>>>>> release >>>>>>>> is done. Since the "projectmgr" component has never been part of the >>>>>>>> >>>>>>>> 13.07 >>>>>>> branch then it may be unsafe to include it now just before the release >>>>>>>> is >>>>>>>> issued. It would be better to discuss its inclusion in the upcoming >>>>>>>> new >>>>>>>> release branch where it could be stabilized and bug fixed. >>>>>>>> >>>>>>>> Regards, >>>>>>>> >>>>>>>> Jacopo >>>>>>>> >>>>>>>> >>>>>>>> -- >>>>> Ron Wheeler >>>>> President >>>>> Artifact Software Inc >>>>> email: [hidden email] >>>>> skype: ronaldmwheeler >>>>> phone: 866-970-2435, ext 102 >>>>> >>>>> >>>>> >>> -- >>> Ron Wheeler >>> President >>> Artifact Software Inc >>> email: [hidden email] >>> skype: ronaldmwheeler >>> phone: 866-970-2435, ext 102 >>> >>> > > > -- > Ron Wheeler > President > Artifact Software Inc > email: [hidden email] > skype: ronaldmwheeler > phone: 866-970-2435, ext 102 > |
Re: [VOTE] PROJECTMGR in upcoming release
|
|
That a component doesn't have any unit-tests is unfortunate, but can hardly
be regarded as a show stopper. A lot of code isn't covered with test cases. Getting unit-tests is a catch-up game in this project. Even new additions to a code get in to trunk and releases without those tests. Even more so, the entire HUMANRES component doesn't have any unit tests and is in the release. As for code undergoing the 1-year long stabilization phase, when looking at the HUMANRES component (see here: http://svn.apache.org/viewvc/ofbiz/branches/release13.07/applications/humanres/) you'll see that it got (approx) the same amount of love as the PROJECTMGR component. Pierre Smits *ORRTIZ.COM <http://www.orrtiz.com>* Services & Solutions for Cloud- Based Manufacturing, Professional Services and Retail & Trade http://www.orrtiz.com On Wed, Oct 1, 2014 at 7:45 AM, Jacopo Cappellato < [hidden email]> wrote: > The fact that someone is using it in an older branch and testing it in > trunk is not enough to guarantee it works well with 13.07; the trunk and > 13.07 are very different codebases. > Additionally, the "projectmgr" component has 0 unit tests; I am not sure > about about its stability, but for example comments in code like the > following don't make me feel super confident: > > <!-- temporary disabled because it caused a db lock with the > checkProjectMembership in projectpermission services --> > > One more point to note: since the component has not been in the 13.07 > branch, it didn't undergo the 1-year long stabilization phase where only > bug-fixes are backported: for example, one month ago, with revision > 1618313, it was modified by a big commit to replace a series of Freemarker > built-ins operation that we decided to not backport to 13.07 but only keep > in the trunk. > > Jacopo > > On Sep 30, 2014, at 11:19 PM, Ron Wheeler <[hidden email]> > wrote: > > > So, as far as is known from Pierre's testing, there is no work required > to "stabilize and bug fix" the module prior to including it in 13.07.01? > > > > Anyone else have any comments on the work required to include it in > 13.07.01? > > > > Ron > > > > On 30/09/2014 5:13 PM, Pierre Smits wrote: > >> Ron, All, > >> > >> We use the latest released branch, meaning 12.x. We don't expose our > >> customers to an unstable unreleased branch, that is still undergoing > >> significant changes. > >> > >> But, we test our solutions against trunk. This enables us to identify > >> issues and register them in JIRA. And supply patches when workload > allows > >> it. > >> > >> So yes, PROJECTMGR, SCRUM, etc work also in r13.x > >> > >> Regards, > >> > >> Pierre Smits > >> > >> *ORRTIZ.COM <http://www.orrtiz.com>* > >> Services & Solutions for Cloud- > >> Based Manufacturing, Professional > >> Services and Retail & Trade > >> http://www.orrtiz.com > >> > >> On Tue, Sep 30, 2014 at 10:22 PM, Ron Wheeler < > >> [hidden email]> wrote: > >> > >>> Are you using it with a 12.04 or 13.xx? > >>> What work is required to get it into 13.07? > >>> > >>> Ron > >>> On 30/09/2014 3:06 PM, Pierre Smits wrote: > >>> > >>>> Yes, I also have a vested interest in keeping this (PROJECTMGR) in the > >>>> releases. It is part of our ORRTIZ:COM solution portfolio for our > >>>> customers > >>>> and we use it internally. And I have contributed to the improvement > of the > >>>> component. > >>>> > >>>> We, at ORRTIZ:COM, even use an extension to the code base to ensure > that > >>>> it > >>>> also works for fixed price and internal projects. This extension > includes > >>>> generating the gl transactions regarding the cost price of each hour > >>>> registered regarding a project. > >>>> > >>>> We also use the LDAP component to connect to our directory server > (Apache > >>>> Directory Server). > >>>> > >>>> Regards, > >>>> > >>>> Pierre Smits > >>>> > >>>> *ORRTIZ.COM <http://www.orrtiz.com>* > >>>> Services & Solutions for Cloud- > >>>> Based Manufacturing, Professional > >>>> Services and Retail & Trade > >>>> http://www.orrtiz.com > >>>> > >>>> On Tue, Sep 30, 2014 at 4:39 PM, Ron Wheeler > <rwheeler@artifact-software. > >>>> com > >>>> > >>>>> wrote: > >>>>> It would be for me since it is one of the components that I want to > use. > >>>>> > >>>>> Perhaps the more knowledgeable people might want to share a bit more > of > >>>>> the background of the feature. > >>>>> Is it in 12.xx.xx? > >>>>> > >>>>> Is it currently in the 13.07 branch and therefor currently part of > the > >>>>> 13.07 versions that people have put in production or is it just in > the > >>>>> trunk that people are putting into production? > >>>>> > >>>>> What are the issues that need to be addressed before it is > "stabilized > >>>>> and > >>>>> bug fixed"? > >>>>> Do any of these issues pose a significant risk to the stability of > the > >>>>> rest of the functionality? > >>>>> > >>>>> Is anyone using it in production? What are their opinions of the > state of > >>>>> the code and the degree of risk? > >>>>> > >>>>> Is anyone prepared to take on the task of getting it "stabilized and > bug > >>>>> fixed" to a point where it can be safely included? > >>>>> What is the estimate of the minimum effort required? > >>>>> > >>>>> Ron > >>>>> > >>>>> > >>>>> On 30/09/2014 9:58 AM, Mike wrote: > >>>>> > >>>>> Why not deploy it as another hot-deploy component? Is it > considered a > >>>>>> "core" ERP component? > >>>>>> > >>>>>> On Tue, Sep 30, 2014 at 2:59 AM, Pierre Smits < > [hidden email]> > >>>>>> wrote: > >>>>>> > >>>>>> Jacopo, > >>>>>> > >>>>>>> Back then there were already strong objections to excluding > components > >>>>>>> from > >>>>>>> the release. I recall that Hans also wanted to keep the SCRUM > component > >>>>>>> in > >>>>>>> the release, as well as there were proponents for BIRT and other > >>>>>>> components. > >>>>>>> > >>>>>>> These are good additions to the feature set of OFBiz and may be in > use > >>>>>>> already by community members. It would be best that you solicit the > >>>>>>> advice > >>>>>>> of the entire community before a decision on excluding components > from > >>>>>>> any > >>>>>>> release is taken. This affects more participants in this project > than > >>>>>>> just > >>>>>>> you and the committers. > >>>>>>> > >>>>>>> Regards, > >>>>>>> > >>>>>>> Pierre Smits > >>>>>>> > >>>>>>> *ORRTIZ.COM <http://www.orrtiz.com>* > >>>>>>> Services & Solutions for Cloud- > >>>>>>> Based Manufacturing, Professional > >>>>>>> Services and Retail & Trade > >>>>>>> http://www.orrtiz.com > >>>>>>> > >>>>>>> On Tue, Sep 30, 2014 at 11:49 AM, Jacopo Cappellato < > >>>>>>> [hidden email]> wrote: > >>>>>>> > >>>>>>> Ok, got it. > >>>>>>> > >>>>>>>> The release process that the OFBiz community is following is > based on > >>>>>>>> a > >>>>>>>> feature freeze phase, that for the 13.07 branch started more than > one > >>>>>>>> > >>>>>>>> year > >>>>>>> ago, during which only bug fixes are backported. > >>>>>>>> This is done in order to stabilize the branch before an official > >>>>>>>> release > >>>>>>>> is done. Since the "projectmgr" component has never been part of > the > >>>>>>>> > >>>>>>>> 13.07 > >>>>>>> branch then it may be unsafe to include it now just before the > release > >>>>>>>> is > >>>>>>>> issued. It would be better to discuss its inclusion in the > upcoming > >>>>>>>> new > >>>>>>>> release branch where it could be stabilized and bug fixed. > >>>>>>>> > >>>>>>>> Regards, > >>>>>>>> > >>>>>>>> Jacopo > >>>>>>>> > >>>>>>>> > >>>>>>>> -- > >>>>> Ron Wheeler > >>>>> President > >>>>> Artifact Software Inc > >>>>> email: [hidden email] > >>>>> skype: ronaldmwheeler > >>>>> phone: 866-970-2435, ext 102 > >>>>> > >>>>> > >>>>> > >>> -- > >>> Ron Wheeler > >>> President > >>> Artifact Software Inc > >>> email: [hidden email] > >>> skype: ronaldmwheeler > >>> phone: 866-970-2435, ext 102 > >>> > >>> > > > > > > -- > > Ron Wheeler > > President > > Artifact Software Inc > > email: [hidden email] > > skype: ronaldmwheeler > > phone: 866-970-2435, ext 102 > > > > |
Re: [VOTE] PROJECTMGR in upcoming release
|
|
In reply to this post by Jacopo Cappellato-4
The excuse of using PROJECTMgr in an older branch (12.x, the latest stable
release) and testing it against trunk and therefor not including it in a release of a newer branch, is a lame one. We are diligent about this, meaning that we do follow up against any potential new release branch in order to be able to migrate to the newer branch when there is something released. Pierre Smits *ORRTIZ.COM <http://www.orrtiz.com>* Services & Solutions for Cloud- Based Manufacturing, Professional Services and Retail & Trade http://www.orrtiz.com On Wed, Oct 1, 2014 at 7:45 AM, Jacopo Cappellato < [hidden email]> wrote: > The fact that someone is using it in an older branch and testing it in > trunk is not enough to guarantee it works well with 13.07; the trunk and > 13.07 are very different codebases. > Additionally, the "projectmgr" component has 0 unit tests; I am not sure > about about its stability, but for example comments in code like the > following don't make me feel super confident: > > <!-- temporary disabled because it caused a db lock with the > checkProjectMembership in projectpermission services --> > > One more point to note: since the component has not been in the 13.07 > branch, it didn't undergo the 1-year long stabilization phase where only > bug-fixes are backported: for example, one month ago, with revision > 1618313, it was modified by a big commit to replace a series of Freemarker > built-ins operation that we decided to not backport to 13.07 but only keep > in the trunk. > > Jacopo > > On Sep 30, 2014, at 11:19 PM, Ron Wheeler <[hidden email]> > wrote: > > > So, as far as is known from Pierre's testing, there is no work required > to "stabilize and bug fix" the module prior to including it in 13.07.01? > > > > Anyone else have any comments on the work required to include it in > 13.07.01? > > > > Ron > > > > On 30/09/2014 5:13 PM, Pierre Smits wrote: > >> Ron, All, > >> > >> We use the latest released branch, meaning 12.x. We don't expose our > >> customers to an unstable unreleased branch, that is still undergoing > >> significant changes. > >> > >> But, we test our solutions against trunk. This enables us to identify > >> issues and register them in JIRA. And supply patches when workload > allows > >> it. > >> > >> So yes, PROJECTMGR, SCRUM, etc work also in r13.x > >> > >> Regards, > >> > >> Pierre Smits > >> > >> *ORRTIZ.COM <http://www.orrtiz.com>* > >> Services & Solutions for Cloud- > >> Based Manufacturing, Professional > >> Services and Retail & Trade > >> http://www.orrtiz.com > >> > >> On Tue, Sep 30, 2014 at 10:22 PM, Ron Wheeler < > >> [hidden email]> wrote: > >> > >>> Are you using it with a 12.04 or 13.xx? > >>> What work is required to get it into 13.07? > >>> > >>> Ron > >>> On 30/09/2014 3:06 PM, Pierre Smits wrote: > >>> > >>>> Yes, I also have a vested interest in keeping this (PROJECTMGR) in the > >>>> releases. It is part of our ORRTIZ:COM solution portfolio for our > >>>> customers > >>>> and we use it internally. And I have contributed to the improvement > of the > >>>> component. > >>>> > >>>> We, at ORRTIZ:COM, even use an extension to the code base to ensure > that > >>>> it > >>>> also works for fixed price and internal projects. This extension > includes > >>>> generating the gl transactions regarding the cost price of each hour > >>>> registered regarding a project. > >>>> > >>>> We also use the LDAP component to connect to our directory server > (Apache > >>>> Directory Server). > >>>> > >>>> Regards, > >>>> > >>>> Pierre Smits > >>>> > >>>> *ORRTIZ.COM <http://www.orrtiz.com>* > >>>> Services & Solutions for Cloud- > >>>> Based Manufacturing, Professional > >>>> Services and Retail & Trade > >>>> http://www.orrtiz.com > >>>> > >>>> On Tue, Sep 30, 2014 at 4:39 PM, Ron Wheeler > <rwheeler@artifact-software. > >>>> com > >>>> > >>>>> wrote: > >>>>> It would be for me since it is one of the components that I want to > use. > >>>>> > >>>>> Perhaps the more knowledgeable people might want to share a bit more > of > >>>>> the background of the feature. > >>>>> Is it in 12.xx.xx? > >>>>> > >>>>> Is it currently in the 13.07 branch and therefor currently part of > the > >>>>> 13.07 versions that people have put in production or is it just in > the > >>>>> trunk that people are putting into production? > >>>>> > >>>>> What are the issues that need to be addressed before it is > "stabilized > >>>>> and > >>>>> bug fixed"? > >>>>> Do any of these issues pose a significant risk to the stability of > the > >>>>> rest of the functionality? > >>>>> > >>>>> Is anyone using it in production? What are their opinions of the > state of > >>>>> the code and the degree of risk? > >>>>> > >>>>> Is anyone prepared to take on the task of getting it "stabilized and > bug > >>>>> fixed" to a point where it can be safely included? > >>>>> What is the estimate of the minimum effort required? > >>>>> > >>>>> Ron > >>>>> > >>>>> > >>>>> On 30/09/2014 9:58 AM, Mike wrote: > >>>>> > >>>>> Why not deploy it as another hot-deploy component? Is it > considered a > >>>>>> "core" ERP component? > >>>>>> > >>>>>> On Tue, Sep 30, 2014 at 2:59 AM, Pierre Smits < > [hidden email]> > >>>>>> wrote: > >>>>>> > >>>>>> Jacopo, > >>>>>> > >>>>>>> Back then there were already strong objections to excluding > components > >>>>>>> from > >>>>>>> the release. I recall that Hans also wanted to keep the SCRUM > component > >>>>>>> in > >>>>>>> the release, as well as there were proponents for BIRT and other > >>>>>>> components. > >>>>>>> > >>>>>>> These are good additions to the feature set of OFBiz and may be in > use > >>>>>>> already by community members. It would be best that you solicit the > >>>>>>> advice > >>>>>>> of the entire community before a decision on excluding components > from > >>>>>>> any > >>>>>>> release is taken. This affects more participants in this project > than > >>>>>>> just > >>>>>>> you and the committers. > >>>>>>> > >>>>>>> Regards, > >>>>>>> > >>>>>>> Pierre Smits > >>>>>>> > >>>>>>> *ORRTIZ.COM <http://www.orrtiz.com>* > >>>>>>> Services & Solutions for Cloud- > >>>>>>> Based Manufacturing, Professional > >>>>>>> Services and Retail & Trade > >>>>>>> http://www.orrtiz.com > >>>>>>> > >>>>>>> On Tue, Sep 30, 2014 at 11:49 AM, Jacopo Cappellato < > >>>>>>> [hidden email]> wrote: > >>>>>>> > >>>>>>> Ok, got it. > >>>>>>> > >>>>>>>> The release process that the OFBiz community is following is > based on > >>>>>>>> a > >>>>>>>> feature freeze phase, that for the 13.07 branch started more than > one > >>>>>>>> > >>>>>>>> year > >>>>>>> ago, during which only bug fixes are backported. > >>>>>>>> This is done in order to stabilize the branch before an official > >>>>>>>> release > >>>>>>>> is done. Since the "projectmgr" component has never been part of > the > >>>>>>>> > >>>>>>>> 13.07 > >>>>>>> branch then it may be unsafe to include it now just before the > release > >>>>>>>> is > >>>>>>>> issued. It would be better to discuss its inclusion in the > upcoming > >>>>>>>> new > >>>>>>>> release branch where it could be stabilized and bug fixed. > >>>>>>>> > >>>>>>>> Regards, > >>>>>>>> > >>>>>>>> Jacopo > >>>>>>>> > >>>>>>>> > >>>>>>>> -- > >>>>> Ron Wheeler > >>>>> President > >>>>> Artifact Software Inc > >>>>> email: [hidden email] > >>>>> skype: ronaldmwheeler > >>>>> phone: 866-970-2435, ext 102 > >>>>> > >>>>> > >>>>> > >>> -- > >>> Ron Wheeler > >>> President > >>> Artifact Software Inc > >>> email: [hidden email] > >>> skype: ronaldmwheeler > >>> phone: 866-970-2435, ext 102 > >>> > >>> > > > > > > -- > > Ron Wheeler > > President > > Artifact Software Inc > > email: [hidden email] > > skype: ronaldmwheeler > > phone: 866-970-2435, ext 102 > > > > |
Re: [VOTE] PROJECTMGR in upcoming release
Administrator
|
Hi Pierre,
Sorry to say but it seems to me that you are beating a dead horse. By our policy, it's obvious you will not get the projectmgr component included in R13.07, despite all your arguments. You should better lobby for its inclusion in R14.10 as Jacopo proposed. For you customers you will have to handle the risk yourself for R13.07 Jacques Le 01/10/2014 08:56, Pierre Smits a écrit : > The excuse of using PROJECTMgr in an older branch (12.x, the latest stable > release) and testing it against trunk and therefor not including it in a > release of a newer branch, is a lame one. > > We are diligent about this, meaning that we do follow up against any > potential new release branch in order to be able to migrate to the newer > branch when there is something released. > > Pierre Smits > > *ORRTIZ.COM <http://www.orrtiz.com>* > Services & Solutions for Cloud- > Based Manufacturing, Professional > Services and Retail & Trade > http://www.orrtiz.com > > On Wed, Oct 1, 2014 at 7:45 AM, Jacopo Cappellato < > [hidden email]> wrote: > >> The fact that someone is using it in an older branch and testing it in >> trunk is not enough to guarantee it works well with 13.07; the trunk and >> 13.07 are very different codebases. >> Additionally, the "projectmgr" component has 0 unit tests; I am not sure >> about about its stability, but for example comments in code like the >> following don't make me feel super confident: >> >> <!-- temporary disabled because it caused a db lock with the >> checkProjectMembership in projectpermission services --> >> >> One more point to note: since the component has not been in the 13.07 >> branch, it didn't undergo the 1-year long stabilization phase where only >> bug-fixes are backported: for example, one month ago, with revision >> 1618313, it was modified by a big commit to replace a series of Freemarker >> built-ins operation that we decided to not backport to 13.07 but only keep >> in the trunk. >> >> Jacopo >> >> On Sep 30, 2014, at 11:19 PM, Ron Wheeler <[hidden email]> >> wrote: >> >>> So, as far as is known from Pierre's testing, there is no work required >> to "stabilize and bug fix" the module prior to including it in 13.07.01? >>> Anyone else have any comments on the work required to include it in >> 13.07.01? >>> Ron >>> >>> On 30/09/2014 5:13 PM, Pierre Smits wrote: >>>> Ron, All, >>>> >>>> We use the latest released branch, meaning 12.x. We don't expose our >>>> customers to an unstable unreleased branch, that is still undergoing >>>> significant changes. >>>> >>>> But, we test our solutions against trunk. This enables us to identify >>>> issues and register them in JIRA. And supply patches when workload >> allows >>>> it. >>>> >>>> So yes, PROJECTMGR, SCRUM, etc work also in r13.x >>>> >>>> Regards, >>>> >>>> Pierre Smits >>>> >>>> *ORRTIZ.COM <http://www.orrtiz.com>* >>>> Services & Solutions for Cloud- >>>> Based Manufacturing, Professional >>>> Services and Retail & Trade >>>> http://www.orrtiz.com >>>> >>>> On Tue, Sep 30, 2014 at 10:22 PM, Ron Wheeler < >>>> [hidden email]> wrote: >>>> >>>>> Are you using it with a 12.04 or 13.xx? >>>>> What work is required to get it into 13.07? >>>>> >>>>> Ron >>>>> On 30/09/2014 3:06 PM, Pierre Smits wrote: >>>>> >>>>>> Yes, I also have a vested interest in keeping this (PROJECTMGR) in the >>>>>> releases. It is part of our ORRTIZ:COM solution portfolio for our >>>>>> customers >>>>>> and we use it internally. And I have contributed to the improvement >> of the >>>>>> component. >>>>>> >>>>>> We, at ORRTIZ:COM, even use an extension to the code base to ensure >> that >>>>>> it >>>>>> also works for fixed price and internal projects. This extension >> includes >>>>>> generating the gl transactions regarding the cost price of each hour >>>>>> registered regarding a project. >>>>>> >>>>>> We also use the LDAP component to connect to our directory server >> (Apache >>>>>> Directory Server). >>>>>> >>>>>> Regards, >>>>>> >>>>>> Pierre Smits >>>>>> >>>>>> *ORRTIZ.COM <http://www.orrtiz.com>* >>>>>> Services & Solutions for Cloud- >>>>>> Based Manufacturing, Professional >>>>>> Services and Retail & Trade >>>>>> http://www.orrtiz.com >>>>>> >>>>>> On Tue, Sep 30, 2014 at 4:39 PM, Ron Wheeler >> <rwheeler@artifact-software. >>>>>> com >>>>>> >>>>>>> wrote: >>>>>>> It would be for me since it is one of the components that I want to >> use. >>>>>>> Perhaps the more knowledgeable people might want to share a bit more >> of >>>>>>> the background of the feature. >>>>>>> Is it in 12.xx.xx? >>>>>>> >>>>>>> Is it currently in the 13.07 branch and therefor currently part of >> the >>>>>>> 13.07 versions that people have put in production or is it just in >> the >>>>>>> trunk that people are putting into production? >>>>>>> >>>>>>> What are the issues that need to be addressed before it is >> "stabilized >>>>>>> and >>>>>>> bug fixed"? >>>>>>> Do any of these issues pose a significant risk to the stability of >> the >>>>>>> rest of the functionality? >>>>>>> >>>>>>> Is anyone using it in production? What are their opinions of the >> state of >>>>>>> the code and the degree of risk? >>>>>>> >>>>>>> Is anyone prepared to take on the task of getting it "stabilized and >> bug >>>>>>> fixed" to a point where it can be safely included? >>>>>>> What is the estimate of the minimum effort required? >>>>>>> >>>>>>> Ron >>>>>>> >>>>>>> >>>>>>> On 30/09/2014 9:58 AM, Mike wrote: >>>>>>> >>>>>>> Why not deploy it as another hot-deploy component? Is it >> considered a >>>>>>>> "core" ERP component? >>>>>>>> >>>>>>>> On Tue, Sep 30, 2014 at 2:59 AM, Pierre Smits < >> [hidden email]> >>>>>>>> wrote: >>>>>>>> >>>>>>>> Jacopo, >>>>>>>> >>>>>>>>> Back then there were already strong objections to excluding >> components >>>>>>>>> from >>>>>>>>> the release. I recall that Hans also wanted to keep the SCRUM >> component >>>>>>>>> in >>>>>>>>> the release, as well as there were proponents for BIRT and other >>>>>>>>> components. >>>>>>>>> >>>>>>>>> These are good additions to the feature set of OFBiz and may be in >> use >>>>>>>>> already by community members. It would be best that you solicit the >>>>>>>>> advice >>>>>>>>> of the entire community before a decision on excluding components >> from >>>>>>>>> any >>>>>>>>> release is taken. This affects more participants in this project >> than >>>>>>>>> just >>>>>>>>> you and the committers. >>>>>>>>> >>>>>>>>> Regards, >>>>>>>>> >>>>>>>>> Pierre Smits >>>>>>>>> >>>>>>>>> *ORRTIZ.COM <http://www.orrtiz.com>* >>>>>>>>> Services & Solutions for Cloud- >>>>>>>>> Based Manufacturing, Professional >>>>>>>>> Services and Retail & Trade >>>>>>>>> http://www.orrtiz.com >>>>>>>>> >>>>>>>>> On Tue, Sep 30, 2014 at 11:49 AM, Jacopo Cappellato < >>>>>>>>> [hidden email]> wrote: >>>>>>>>> >>>>>>>>> Ok, got it. >>>>>>>>> >>>>>>>>>> The release process that the OFBiz community is following is >> based on >>>>>>>>>> a >>>>>>>>>> feature freeze phase, that for the 13.07 branch started more than >> one >>>>>>>>>> year >>>>>>>>> ago, during which only bug fixes are backported. >>>>>>>>>> This is done in order to stabilize the branch before an official >>>>>>>>>> release >>>>>>>>>> is done. Since the "projectmgr" component has never been part of >> the >>>>>>>>>> 13.07 >>>>>>>>> branch then it may be unsafe to include it now just before the >> release >>>>>>>>>> is >>>>>>>>>> issued. It would be better to discuss its inclusion in the >> upcoming >>>>>>>>>> new >>>>>>>>>> release branch where it could be stabilized and bug fixed. >>>>>>>>>> >>>>>>>>>> Regards, >>>>>>>>>> >>>>>>>>>> Jacopo >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> -- >>>>>>> Ron Wheeler >>>>>>> President >>>>>>> Artifact Software Inc >>>>>>> email: [hidden email] >>>>>>> skype: ronaldmwheeler >>>>>>> phone: 866-970-2435, ext 102 >>>>>>> >>>>>>> >>>>>>> >>>>> -- >>>>> Ron Wheeler >>>>> President >>>>> Artifact Software Inc >>>>> email: [hidden email] >>>>> skype: ronaldmwheeler >>>>> phone: 866-970-2435, ext 102 >>>>> >>>>> >>> >>> -- >>> Ron Wheeler >>> President >>> Artifact Software Inc >>> email: [hidden email] >>> skype: ronaldmwheeler >>> phone: 866-970-2435, ext 102 >>> >> |
Re: [VOTE] PROJECTMGR in upcoming release
|
Administrator
|
In reply to this post by Ted Byers
Le 30/09/2014 17:20, Ted Byers a écrit :
> It may be useful to look at how R handles these issues. There is R-core, > and an R-core team, that is part of the main distribution (all packages > included in an installation of it), and then there is CRAN (similar in > concept to CPAN, for any Perl programmers out there - I hope it isn't > considered blasphemy to talk about Perl in this forum ;-) ), to which all > members of the R community can contribute their packages; analogous to > components in the context of an application like OFBiz. CRAN has a QA > protocol, which must be passed in order for an R package to be added to > CRAN; something that assures users that their system will not be trashed if > they instal a package available from CRAN. And, sometimes, the R core team > decides that one of the packages on CRAN is so important and useful that > they decide to add it to core (this doesn't happen often, but it does > happen). So then, in the context of OFBiz, the first question becomes, can > the hot-deploy support be used in a manner similar to a snadbox that > protext the rest of the system from badly behaved code (NB: I am not > implying anything about the code in the component in question now, but > rather thinking in general terms for any new component anyone may want to > contribute)? And then, the question becomes, what protocol can be used for > promoting components from the 'sandbox' to incorporation into the 'core > release'; whatever you want to call it? Hi Ted, it seems you were more thinking aloud :) but let me try to answer you In ASF project lazy consensus is used. In other words, it's discussed by the project community and if really people can't get to an agreement a vote is open. Then only PMC members have binding votes http://www.apache.org/foundation/voting.html. The issue about projectmanager Pierre raised has already been discussed and we decided to keep only ecommerce in specialpurpose. Before some components (projectmanager for instance) had been moved from applicationd to specialpurpose. It's maybe unfortunate. But, as Jacopo suggested, we (so far, Jacopo and I at least) are open to discuss this again and indeed projectmanager and few other components could get back to specialpurpose IMO. Adding Junit tests then would be a good thing. Note that, though Erwan (a PMC member, no longer an active committer) tried to install the whole flow, we don't have a mean to test the UI in the project. I know though this is done by some other service providers. I hope I answered you Jacques > > Cheers > > Ted |
Re: [VOTE] PROJECTMGR in upcoming release
|
|
In reply to this post by Jacopo Cappellato-4
"temorarily disabled..." Certainly seems like a note that should cause
some careful analysis. Did the author of the comment create a JIRA issue to address this problem? Is there any guidance about unit tests? Can a JIRA issue (or set of issues) be created describing the unit tests that must be done to get this into a stable release? On a more general note: It looks like there are a number of other modules in the same situation. Is there currently any way to track who is interested in working on these modules (code, docs, testing, etc.) so that modules do not disappear between releases. It is unsettling for a user community to have functionality disappear during an upgrade. It would certainly causes a loss of faith in the product if: a) you can not upgrade because modules you use in the current release are missing and b) at the same time, you see support being withdrawn from older versions. This raises a topic that came a few weeks ago while we were cleaning up the product description. There needs to be a clear statement of what OFBiz provides and what are modules that are not considered part of OFBiz but are extensions that someone other than the core OFBiz team provides as part of every release. It appears that PROJECTMGR falls into that second category and is not part of the official OFBiz product. This is not necessarily a bad thing but it needs to be stated very clearly. As I understand "The Apache Way", this would result in a set of sub-projects under OFBiz with sets of identified contributors who work on these sub-projects. This way, there are no orphans that no one supports. Unsupported projects would become dead projects whereby the end-users could use the code base with the understanding that they are solely responsible for maintaining changes to the code on their own SCM until such time as they are able to commit the code back with the permission of the PMC. There would be a clear understanding on the part of the user community that they are taking a risk by using the supported extensions since they may get caught in a dead end if the project dies or at a minimum a delay in being able to upgrade. They would at least know where they stand a bit better and the team working on the core product would have a clearer mandate. It should also force the main group and the maintainers of each sub-project to identify the interfacing points between each system so that the impact of changes to the OFBiz core would be understood a bit better. It would also provide a local incubation process where extensions could be proposed as sub-projects and the more successful (active team, many users) sub-projects could be elevated to the core. Ron On 01/10/2014 1:45 AM, Jacopo Cappellato wrote: > The fact that someone is using it in an older branch and testing it in trunk is not enough to guarantee it works well with 13.07; the trunk and 13.07 are very different codebases. > Additionally, the "projectmgr" component has 0 unit tests; I am not sure about about its stability, but for example comments in code like the following don't make me feel super confident: > > <!-- temporary disabled because it caused a db lock with the checkProjectMembership in projectpermission services --> > > One more point to note: since the component has not been in the 13.07 branch, it didn't undergo the 1-year long stabilization phase where only bug-fixes are backported: for example, one month ago, with revision 1618313, it was modified by a big commit to replace a series of Freemarker built-ins operation that we decided to not backport to 13.07 but only keep in the trunk. > > Jacopo > > On Sep 30, 2014, at 11:19 PM, Ron Wheeler <[hidden email]> wrote: > >> So, as far as is known from Pierre's testing, there is no work required to "stabilize and bug fix" the module prior to including it in 13.07.01? >> >> Anyone else have any comments on the work required to include it in 13.07.01? >> >> Ron >> >> On 30/09/2014 5:13 PM, Pierre Smits wrote: >>> Ron, All, >>> >>> We use the latest released branch, meaning 12.x. We don't expose our >>> customers to an unstable unreleased branch, that is still undergoing >>> significant changes. >>> >>> But, we test our solutions against trunk. This enables us to identify >>> issues and register them in JIRA. And supply patches when workload allows >>> it. >>> >>> So yes, PROJECTMGR, SCRUM, etc work also in r13.x >>> >>> Regards, >>> >>> Pierre Smits >>> >>> *ORRTIZ.COM <http://www.orrtiz.com>* >>> Services & Solutions for Cloud- >>> Based Manufacturing, Professional >>> Services and Retail & Trade >>> http://www.orrtiz.com >>> >>> On Tue, Sep 30, 2014 at 10:22 PM, Ron Wheeler < >>> [hidden email]> wrote: >>> >>>> Are you using it with a 12.04 or 13.xx? >>>> What work is required to get it into 13.07? >>>> >>>> Ron >>>> On 30/09/2014 3:06 PM, Pierre Smits wrote: >>>> >>>>> Yes, I also have a vested interest in keeping this (PROJECTMGR) in the >>>>> releases. It is part of our ORRTIZ:COM solution portfolio for our >>>>> customers >>>>> and we use it internally. And I have contributed to the improvement of the >>>>> component. >>>>> >>>>> We, at ORRTIZ:COM, even use an extension to the code base to ensure that >>>>> it >>>>> also works for fixed price and internal projects. This extension includes >>>>> generating the gl transactions regarding the cost price of each hour >>>>> registered regarding a project. >>>>> >>>>> We also use the LDAP component to connect to our directory server (Apache >>>>> Directory Server). >>>>> >>>>> Regards, >>>>> >>>>> Pierre Smits >>>>> >>>>> *ORRTIZ.COM <http://www.orrtiz.com>* >>>>> Services & Solutions for Cloud- >>>>> Based Manufacturing, Professional >>>>> Services and Retail & Trade >>>>> http://www.orrtiz.com >>>>> >>>>> On Tue, Sep 30, 2014 at 4:39 PM, Ron Wheeler <rwheeler@artifact-software. >>>>> com >>>>> >>>>>> wrote: >>>>>> It would be for me since it is one of the components that I want to use. >>>>>> >>>>>> Perhaps the more knowledgeable people might want to share a bit more of >>>>>> the background of the feature. >>>>>> Is it in 12.xx.xx? >>>>>> >>>>>> Is it currently in the 13.07 branch and therefor currently part of the >>>>>> 13.07 versions that people have put in production or is it just in the >>>>>> trunk that people are putting into production? >>>>>> >>>>>> What are the issues that need to be addressed before it is "stabilized >>>>>> and >>>>>> bug fixed"? >>>>>> Do any of these issues pose a significant risk to the stability of the >>>>>> rest of the functionality? >>>>>> >>>>>> Is anyone using it in production? What are their opinions of the state of >>>>>> the code and the degree of risk? >>>>>> >>>>>> Is anyone prepared to take on the task of getting it "stabilized and bug >>>>>> fixed" to a point where it can be safely included? >>>>>> What is the estimate of the minimum effort required? >>>>>> >>>>>> Ron >>>>>> >>>>>> >>>>>> On 30/09/2014 9:58 AM, Mike wrote: >>>>>> >>>>>> Why not deploy it as another hot-deploy component? Is it considered a >>>>>>> "core" ERP component? >>>>>>> >>>>>>> On Tue, Sep 30, 2014 at 2:59 AM, Pierre Smits <[hidden email]> >>>>>>> wrote: >>>>>>> >>>>>>> Jacopo, >>>>>>> >>>>>>>> Back then there were already strong objections to excluding components >>>>>>>> from >>>>>>>> the release. I recall that Hans also wanted to keep the SCRUM component >>>>>>>> in >>>>>>>> the release, as well as there were proponents for BIRT and other >>>>>>>> components. >>>>>>>> >>>>>>>> These are good additions to the feature set of OFBiz and may be in use >>>>>>>> already by community members. It would be best that you solicit the >>>>>>>> advice >>>>>>>> of the entire community before a decision on excluding components from >>>>>>>> any >>>>>>>> release is taken. This affects more participants in this project than >>>>>>>> just >>>>>>>> you and the committers. >>>>>>>> >>>>>>>> Regards, >>>>>>>> >>>>>>>> Pierre Smits >>>>>>>> >>>>>>>> *ORRTIZ.COM <http://www.orrtiz.com>* >>>>>>>> Services & Solutions for Cloud- >>>>>>>> Based Manufacturing, Professional >>>>>>>> Services and Retail & Trade >>>>>>>> http://www.orrtiz.com >>>>>>>> >>>>>>>> On Tue, Sep 30, 2014 at 11:49 AM, Jacopo Cappellato < >>>>>>>> [hidden email]> wrote: >>>>>>>> >>>>>>>> Ok, got it. >>>>>>>> >>>>>>>>> The release process that the OFBiz community is following is based on >>>>>>>>> a >>>>>>>>> feature freeze phase, that for the 13.07 branch started more than one >>>>>>>>> >>>>>>>>> year >>>>>>>> ago, during which only bug fixes are backported. >>>>>>>>> This is done in order to stabilize the branch before an official >>>>>>>>> release >>>>>>>>> is done. Since the "projectmgr" component has never been part of the >>>>>>>>> >>>>>>>>> 13.07 >>>>>>>> branch then it may be unsafe to include it now just before the release >>>>>>>>> is >>>>>>>>> issued. It would be better to discuss its inclusion in the upcoming >>>>>>>>> new >>>>>>>>> release branch where it could be stabilized and bug fixed. >>>>>>>>> >>>>>>>>> Regards, >>>>>>>>> >>>>>>>>> Jacopo >>>>>>>>> -- Ron Wheeler President Artifact Software Inc email: [hidden email] skype: ronaldmwheeler phone: 866-970-2435, ext 102 |
Re: [VOTE] PROJECTMGR in upcoming release
|
|
In reply to this post by Pierre Smits
What unit tests should it have?
It is hard to create a general rule about unit tests specially for software that is predominately UI. Does anyone have any concrete suggestions on PROJECTMGR ? Clearly, getting something into Release Candidates early gives the user community a chance to test the UI parts and identify deficiencies. There should be some objective list of criteria to decide when an extension is ready for inclusion in a Release Candidate. Could be as simple as having one person agree to test it and at least one person agree to fix any bugs found. Ron On 01/10/2014 2:43 AM, Pierre Smits wrote: > That a component doesn't have any unit-tests is unfortunate, but can hardly > be regarded as a show stopper. A lot of code isn't covered with test cases. > Getting unit-tests is a catch-up game in this project. Even new additions > to a code get in to trunk and releases without those tests. > Even more so, the entire HUMANRES component doesn't have any unit tests and > is in the release. > > As for code undergoing the 1-year long stabilization phase, when looking at > the HUMANRES component (see here: > http://svn.apache.org/viewvc/ofbiz/branches/release13.07/applications/humanres/) > you'll see that it got (approx) the same amount of love as the PROJECTMGR > component. > > > > Pierre Smits > > *ORRTIZ.COM <http://www.orrtiz.com>* > Services & Solutions for Cloud- > Based Manufacturing, Professional > Services and Retail & Trade > http://www.orrtiz.com > > On Wed, Oct 1, 2014 at 7:45 AM, Jacopo Cappellato < > [hidden email]> wrote: > >> The fact that someone is using it in an older branch and testing it in >> trunk is not enough to guarantee it works well with 13.07; the trunk and >> 13.07 are very different codebases. >> Additionally, the "projectmgr" component has 0 unit tests; I am not sure >> about about its stability, but for example comments in code like the >> following don't make me feel super confident: >> >> <!-- temporary disabled because it caused a db lock with the >> checkProjectMembership in projectpermission services --> >> >> One more point to note: since the component has not been in the 13.07 >> branch, it didn't undergo the 1-year long stabilization phase where only >> bug-fixes are backported: for example, one month ago, with revision >> 1618313, it was modified by a big commit to replace a series of Freemarker >> built-ins operation that we decided to not backport to 13.07 but only keep >> in the trunk. >> >> Jacopo >> >> On Sep 30, 2014, at 11:19 PM, Ron Wheeler <[hidden email]> >> wrote: >> >>> So, as far as is known from Pierre's testing, there is no work required >> to "stabilize and bug fix" the module prior to including it in 13.07.01? >>> Anyone else have any comments on the work required to include it in >> 13.07.01? >>> Ron >>> >>> On 30/09/2014 5:13 PM, Pierre Smits wrote: >>>> Ron, All, >>>> >>>> We use the latest released branch, meaning 12.x. We don't expose our >>>> customers to an unstable unreleased branch, that is still undergoing >>>> significant changes. >>>> >>>> But, we test our solutions against trunk. This enables us to identify >>>> issues and register them in JIRA. And supply patches when workload >> allows >>>> it. >>>> >>>> So yes, PROJECTMGR, SCRUM, etc work also in r13.x >>>> >>>> Regards, >>>> >>>> Pierre Smits >>>> >>>> *ORRTIZ.COM <http://www.orrtiz.com>* >>>> Services & Solutions for Cloud- >>>> Based Manufacturing, Professional >>>> Services and Retail & Trade >>>> http://www.orrtiz.com >>>> >>>> On Tue, Sep 30, 2014 at 10:22 PM, Ron Wheeler < >>>> [hidden email]> wrote: >>>> >>>>> Are you using it with a 12.04 or 13.xx? >>>>> What work is required to get it into 13.07? >>>>> >>>>> Ron >>>>> On 30/09/2014 3:06 PM, Pierre Smits wrote: >>>>> >>>>>> Yes, I also have a vested interest in keeping this (PROJECTMGR) in the >>>>>> releases. It is part of our ORRTIZ:COM solution portfolio for our >>>>>> customers >>>>>> and we use it internally. And I have contributed to the improvement >> of the >>>>>> component. >>>>>> >>>>>> We, at ORRTIZ:COM, even use an extension to the code base to ensure >> that >>>>>> it >>>>>> also works for fixed price and internal projects. This extension >> includes >>>>>> generating the gl transactions regarding the cost price of each hour >>>>>> registered regarding a project. >>>>>> >>>>>> We also use the LDAP component to connect to our directory server >> (Apache >>>>>> Directory Server). >>>>>> >>>>>> Regards, >>>>>> >>>>>> Pierre Smits >>>>>> >>>>>> *ORRTIZ.COM <http://www.orrtiz.com>* >>>>>> Services & Solutions for Cloud- >>>>>> Based Manufacturing, Professional >>>>>> Services and Retail & Trade >>>>>> http://www.orrtiz.com >>>>>> >>>>>> On Tue, Sep 30, 2014 at 4:39 PM, Ron Wheeler >> <rwheeler@artifact-software. >>>>>> com >>>>>> >>>>>>> wrote: >>>>>>> It would be for me since it is one of the components that I want to >> use. >>>>>>> Perhaps the more knowledgeable people might want to share a bit more >> of >>>>>>> the background of the feature. >>>>>>> Is it in 12.xx.xx? >>>>>>> >>>>>>> Is it currently in the 13.07 branch and therefor currently part of >> the >>>>>>> 13.07 versions that people have put in production or is it just in >> the >>>>>>> trunk that people are putting into production? >>>>>>> >>>>>>> What are the issues that need to be addressed before it is >> "stabilized >>>>>>> and >>>>>>> bug fixed"? >>>>>>> Do any of these issues pose a significant risk to the stability of >> the >>>>>>> rest of the functionality? >>>>>>> >>>>>>> Is anyone using it in production? What are their opinions of the >> state of >>>>>>> the code and the degree of risk? >>>>>>> >>>>>>> Is anyone prepared to take on the task of getting it "stabilized and >> bug >>>>>>> fixed" to a point where it can be safely included? >>>>>>> What is the estimate of the minimum effort required? >>>>>>> >>>>>>> Ron >>>>>>> >>>>>>> >>>>>>> On 30/09/2014 9:58 AM, Mike wrote: >>>>>>> >>>>>>> Why not deploy it as another hot-deploy component? Is it >> considered a >>>>>>>> "core" ERP component? >>>>>>>> >>>>>>>> On Tue, Sep 30, 2014 at 2:59 AM, Pierre Smits < >> [hidden email]> >>>>>>>> wrote: >>>>>>>> >>>>>>>> Jacopo, >>>>>>>> >>>>>>>>> Back then there were already strong objections to excluding >> components >>>>>>>>> from >>>>>>>>> the release. I recall that Hans also wanted to keep the SCRUM >> component >>>>>>>>> in >>>>>>>>> the release, as well as there were proponents for BIRT and other >>>>>>>>> components. >>>>>>>>> >>>>>>>>> These are good additions to the feature set of OFBiz and may be in >> use >>>>>>>>> already by community members. It would be best that you solicit the >>>>>>>>> advice >>>>>>>>> of the entire community before a decision on excluding components >> from >>>>>>>>> any >>>>>>>>> release is taken. This affects more participants in this project >> than >>>>>>>>> just >>>>>>>>> you and the committers. >>>>>>>>> >>>>>>>>> Regards, >>>>>>>>> >>>>>>>>> Pierre Smits >>>>>>>>> >>>>>>>>> *ORRTIZ.COM <http://www.orrtiz.com>* >>>>>>>>> Services & Solutions for Cloud- >>>>>>>>> Based Manufacturing, Professional >>>>>>>>> Services and Retail & Trade >>>>>>>>> http://www.orrtiz.com >>>>>>>>> >>>>>>>>> On Tue, Sep 30, 2014 at 11:49 AM, Jacopo Cappellato < >>>>>>>>> [hidden email]> wrote: >>>>>>>>> >>>>>>>>> Ok, got it. >>>>>>>>> >>>>>>>>>> The release process that the OFBiz community is following is >> based on >>>>>>>>>> a >>>>>>>>>> feature freeze phase, that for the 13.07 branch started more than >> one >>>>>>>>>> year >>>>>>>>> ago, during which only bug fixes are backported. >>>>>>>>>> This is done in order to stabilize the branch before an official >>>>>>>>>> release >>>>>>>>>> is done. Since the "projectmgr" component has never been part of >> the >>>>>>>>>> 13.07 >>>>>>>>> branch then it may be unsafe to include it now just before the >> release >>>>>>>>>> is >>>>>>>>>> issued. It would be better to discuss its inclusion in the >> upcoming >>>>>>>>>> new >>>>>>>>>> release branch where it could be stabilized and bug fixed. >>>>>>>>>> >>>>>>>>>> Regards, >>>>>>>>>> >>>>>>>>>> Jacopo >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> -- Ron Wheeler President Artifact Software Inc email: [hidden email] skype: ronaldmwheeler phone: 866-970-2435, ext 102 |
Re: [VOTE] PROJECTMGR in upcoming release
|
|
In reply to this post by Pierre Smits
A defined method of deciding what moves from the trunk to a release
would solve this. Back to my previous comment about 1 person to test and 1 person to fix bugs (could be the same person I suppose) would be a good starting minimum. Ron On 01/10/2014 2:56 AM, Pierre Smits wrote: > The excuse of using PROJECTMgr in an older branch (12.x, the latest stable > release) and testing it against trunk and therefor not including it in a > release of a newer branch, is a lame one. > > We are diligent about this, meaning that we do follow up against any > potential new release branch in order to be able to migrate to the newer > branch when there is something released. > > Pierre Smits > > *ORRTIZ.COM <http://www.orrtiz.com>* > Services & Solutions for Cloud- > Based Manufacturing, Professional > Services and Retail & Trade > http://www.orrtiz.com > > On Wed, Oct 1, 2014 at 7:45 AM, Jacopo Cappellato < > [hidden email]> wrote: > >> The fact that someone is using it in an older branch and testing it in >> trunk is not enough to guarantee it works well with 13.07; the trunk and >> 13.07 are very different codebases. >> Additionally, the "projectmgr" component has 0 unit tests; I am not sure >> about about its stability, but for example comments in code like the >> following don't make me feel super confident: >> >> <!-- temporary disabled because it caused a db lock with the >> checkProjectMembership in projectpermission services --> >> >> One more point to note: since the component has not been in the 13.07 >> branch, it didn't undergo the 1-year long stabilization phase where only >> bug-fixes are backported: for example, one month ago, with revision >> 1618313, it was modified by a big commit to replace a series of Freemarker >> built-ins operation that we decided to not backport to 13.07 but only keep >> in the trunk. >> >> Jacopo >> >> On Sep 30, 2014, at 11:19 PM, Ron Wheeler <[hidden email]> >> wrote: >> >>> So, as far as is known from Pierre's testing, there is no work required >> to "stabilize and bug fix" the module prior to including it in 13.07.01? >>> Anyone else have any comments on the work required to include it in >> 13.07.01? >>> Ron >>> >>> On 30/09/2014 5:13 PM, Pierre Smits wrote: >>>> Ron, All, >>>> >>>> We use the latest released branch, meaning 12.x. We don't expose our >>>> customers to an unstable unreleased branch, that is still undergoing >>>> significant changes. >>>> >>>> But, we test our solutions against trunk. This enables us to identify >>>> issues and register them in JIRA. And supply patches when workload >> allows >>>> it. >>>> >>>> So yes, PROJECTMGR, SCRUM, etc work also in r13.x >>>> >>>> Regards, >>>> >>>> Pierre Smits >>>> >>>> *ORRTIZ.COM <http://www.orrtiz.com>* >>>> Services & Solutions for Cloud- >>>> Based Manufacturing, Professional >>>> Services and Retail & Trade >>>> http://www.orrtiz.com >>>> >>>> On Tue, Sep 30, 2014 at 10:22 PM, Ron Wheeler < >>>> [hidden email]> wrote: >>>> >>>>> Are you using it with a 12.04 or 13.xx? >>>>> What work is required to get it into 13.07? >>>>> >>>>> Ron >>>>> On 30/09/2014 3:06 PM, Pierre Smits wrote: >>>>> >>>>>> Yes, I also have a vested interest in keeping this (PROJECTMGR) in the >>>>>> releases. It is part of our ORRTIZ:COM solution portfolio for our >>>>>> customers >>>>>> and we use it internally. And I have contributed to the improvement >> of the >>>>>> component. >>>>>> >>>>>> We, at ORRTIZ:COM, even use an extension to the code base to ensure >> that >>>>>> it >>>>>> also works for fixed price and internal projects. This extension >> includes >>>>>> generating the gl transactions regarding the cost price of each hour >>>>>> registered regarding a project. >>>>>> >>>>>> We also use the LDAP component to connect to our directory server >> (Apache >>>>>> Directory Server). >>>>>> >>>>>> Regards, >>>>>> >>>>>> Pierre Smits >>>>>> >>>>>> *ORRTIZ.COM <http://www.orrtiz.com>* >>>>>> Services & Solutions for Cloud- >>>>>> Based Manufacturing, Professional >>>>>> Services and Retail & Trade >>>>>> http://www.orrtiz.com >>>>>> >>>>>> On Tue, Sep 30, 2014 at 4:39 PM, Ron Wheeler >> <rwheeler@artifact-software. >>>>>> com >>>>>> >>>>>>> wrote: >>>>>>> It would be for me since it is one of the components that I want to >> use. >>>>>>> Perhaps the more knowledgeable people might want to share a bit more >> of >>>>>>> the background of the feature. >>>>>>> Is it in 12.xx.xx? >>>>>>> >>>>>>> Is it currently in the 13.07 branch and therefor currently part of >> the >>>>>>> 13.07 versions that people have put in production or is it just in >> the >>>>>>> trunk that people are putting into production? >>>>>>> >>>>>>> What are the issues that need to be addressed before it is >> "stabilized >>>>>>> and >>>>>>> bug fixed"? >>>>>>> Do any of these issues pose a significant risk to the stability of >> the >>>>>>> rest of the functionality? >>>>>>> >>>>>>> Is anyone using it in production? What are their opinions of the >> state of >>>>>>> the code and the degree of risk? >>>>>>> >>>>>>> Is anyone prepared to take on the task of getting it "stabilized and >> bug >>>>>>> fixed" to a point where it can be safely included? >>>>>>> What is the estimate of the minimum effort required? >>>>>>> >>>>>>> Ron >>>>>>> >>>>>>> >>>>>>> On 30/09/2014 9:58 AM, Mike wrote: >>>>>>> >>>>>>> Why not deploy it as another hot-deploy component? Is it >> considered a >>>>>>>> "core" ERP component? >>>>>>>> >>>>>>>> On Tue, Sep 30, 2014 at 2:59 AM, Pierre Smits < >> [hidden email]> >>>>>>>> wrote: >>>>>>>> >>>>>>>> Jacopo, >>>>>>>> >>>>>>>>> Back then there were already strong objections to excluding >> components >>>>>>>>> from >>>>>>>>> the release. I recall that Hans also wanted to keep the SCRUM >> component >>>>>>>>> in >>>>>>>>> the release, as well as there were proponents for BIRT and other >>>>>>>>> components. >>>>>>>>> >>>>>>>>> These are good additions to the feature set of OFBiz and may be in >> use >>>>>>>>> already by community members. It would be best that you solicit the >>>>>>>>> advice >>>>>>>>> of the entire community before a decision on excluding components >> from >>>>>>>>> any >>>>>>>>> release is taken. This affects more participants in this project >> than >>>>>>>>> just >>>>>>>>> you and the committers. >>>>>>>>> >>>>>>>>> Regards, >>>>>>>>> >>>>>>>>> Pierre Smits >>>>>>>>> >>>>>>>>> *ORRTIZ.COM <http://www.orrtiz.com>* >>>>>>>>> Services & Solutions for Cloud- >>>>>>>>> Based Manufacturing, Professional >>>>>>>>> Services and Retail & Trade >>>>>>>>> http://www.orrtiz.com >>>>>>>>> >>>>>>>>> On Tue, Sep 30, 2014 at 11:49 AM, Jacopo Cappellato < >>>>>>>>> [hidden email]> wrote: >>>>>>>>> >>>>>>>>> Ok, got it. >>>>>>>>> >>>>>>>>>> The release process that the OFBiz community is following is >> based on >>>>>>>>>> a >>>>>>>>>> feature freeze phase, that for the 13.07 branch started more than >> one >>>>>>>>>> year >>>>>>>>> ago, during which only bug fixes are backported. >>>>>>>>>> This is done in order to stabilize the branch before an official >>>>>>>>>> release >>>>>>>>>> is done. Since the "projectmgr" component has never been part of >> the >>>>>>>>>> 13.07 >>>>>>>>> branch then it may be unsafe to include it now just before the >> release >>>>>>>>>> is >>>>>>>>>> issued. It would be better to discuss its inclusion in the >> upcoming >>>>>>>>>> new >>>>>>>>>> release branch where it could be stabilized and bug fixed. >>>>>>>>>> >>>>>>>>>> Regards, >>>>>>>>>> >>>>>>>>>> Jacopo >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> -- Ron Wheeler President Artifact Software Inc email: [hidden email] skype: ronaldmwheeler phone: 866-970-2435, ext 102 |
Re: [VOTE] PROJECTMGR in upcoming release
|
|
Ron,
In the past there was a WIKI page decribing who was interested and who was willing to work on what. I don't know whether that page still exists. In the past we also had a system of having committers dedicated and committed to a subset of the trunk. This should still be feasible. But for that you need more committers. And to get more committers, this project needs to solicit and accept more. Regards, Pierre Smits *ORRTIZ.COM <http://www.orrtiz.com>* Services & Solutions for Cloud- Based Manufacturing, Professional Services and Retail & Trade http://www.orrtiz.com On Wed, Oct 1, 2014 at 4:10 PM, Ron Wheeler <[hidden email]> wrote: > A defined method of deciding what moves from the trunk to a release would > solve this. > Back to my previous comment about 1 person to test and 1 person to fix > bugs (could be the same person I suppose) would be a good starting minimum. > > Ron > > On 01/10/2014 2:56 AM, Pierre Smits wrote: > >> The excuse of using PROJECTMgr in an older branch (12.x, the latest stable >> release) and testing it against trunk and therefor not including it in a >> release of a newer branch, is a lame one. >> >> We are diligent about this, meaning that we do follow up against any >> potential new release branch in order to be able to migrate to the newer >> branch when there is something released. >> >> Pierre Smits >> >> *ORRTIZ.COM <http://www.orrtiz.com>* >> Services & Solutions for Cloud- >> Based Manufacturing, Professional >> Services and Retail & Trade >> http://www.orrtiz.com >> >> On Wed, Oct 1, 2014 at 7:45 AM, Jacopo Cappellato < >> [hidden email]> wrote: >> >> The fact that someone is using it in an older branch and testing it in >>> trunk is not enough to guarantee it works well with 13.07; the trunk and >>> 13.07 are very different codebases. >>> Additionally, the "projectmgr" component has 0 unit tests; I am not sure >>> about about its stability, but for example comments in code like the >>> following don't make me feel super confident: >>> >>> <!-- temporary disabled because it caused a db lock with the >>> checkProjectMembership in projectpermission services --> >>> >>> One more point to note: since the component has not been in the 13.07 >>> branch, it didn't undergo the 1-year long stabilization phase where only >>> bug-fixes are backported: for example, one month ago, with revision >>> 1618313, it was modified by a big commit to replace a series of >>> Freemarker >>> built-ins operation that we decided to not backport to 13.07 but only >>> keep >>> in the trunk. >>> >>> Jacopo >>> >>> On Sep 30, 2014, at 11:19 PM, Ron Wheeler <rwheeler@artifact-software. >>> com> >>> wrote: >>> >>> So, as far as is known from Pierre's testing, there is no work required >>>> >>> to "stabilize and bug fix" the module prior to including it in 13.07.01? >>> >>>> Anyone else have any comments on the work required to include it in >>>> >>> 13.07.01? >>> >>>> Ron >>>> >>>> On 30/09/2014 5:13 PM, Pierre Smits wrote: >>>> >>>>> Ron, All, >>>>> >>>>> We use the latest released branch, meaning 12.x. We don't expose our >>>>> customers to an unstable unreleased branch, that is still undergoing >>>>> significant changes. >>>>> >>>>> But, we test our solutions against trunk. This enables us to identify >>>>> issues and register them in JIRA. And supply patches when workload >>>>> >>>> allows >>> >>>> it. >>>>> >>>>> So yes, PROJECTMGR, SCRUM, etc work also in r13.x >>>>> >>>>> Regards, >>>>> >>>>> Pierre Smits >>>>> >>>>> *ORRTIZ.COM <http://www.orrtiz.com>* >>>>> Services & Solutions for Cloud- >>>>> Based Manufacturing, Professional >>>>> Services and Retail & Trade >>>>> http://www.orrtiz.com >>>>> >>>>> On Tue, Sep 30, 2014 at 10:22 PM, Ron Wheeler < >>>>> [hidden email]> wrote: >>>>> >>>>> Are you using it with a 12.04 or 13.xx? >>>>>> What work is required to get it into 13.07? >>>>>> >>>>>> Ron >>>>>> On 30/09/2014 3:06 PM, Pierre Smits wrote: >>>>>> >>>>>> Yes, I also have a vested interest in keeping this (PROJECTMGR) in >>>>>>> the >>>>>>> releases. It is part of our ORRTIZ:COM solution portfolio for our >>>>>>> customers >>>>>>> and we use it internally. And I have contributed to the improvement >>>>>>> >>>>>> of the >>> >>>> component. >>>>>>> >>>>>>> We, at ORRTIZ:COM, even use an extension to the code base to ensure >>>>>>> >>>>>> that >>> >>>> it >>>>>>> also works for fixed price and internal projects. This extension >>>>>>> >>>>>> includes >>> >>>> generating the gl transactions regarding the cost price of each hour >>>>>>> registered regarding a project. >>>>>>> >>>>>>> We also use the LDAP component to connect to our directory server >>>>>>> >>>>>> (Apache >>> >>>> Directory Server). >>>>>>> >>>>>>> Regards, >>>>>>> >>>>>>> Pierre Smits >>>>>>> >>>>>>> *ORRTIZ.COM <http://www.orrtiz.com>* >>>>>>> Services & Solutions for Cloud- >>>>>>> Based Manufacturing, Professional >>>>>>> Services and Retail & Trade >>>>>>> http://www.orrtiz.com >>>>>>> >>>>>>> On Tue, Sep 30, 2014 at 4:39 PM, Ron Wheeler >>>>>>> >>>>>> <rwheeler@artifact-software. >>> >>>> com >>>>>>> >>>>>>> wrote: >>>>>>>> It would be for me since it is one of the components that I want to >>>>>>>> >>>>>>> use. >>> >>>> Perhaps the more knowledgeable people might want to share a bit more >>>>>>>> >>>>>>> of >>> >>>> the background of the feature. >>>>>>>> Is it in 12.xx.xx? >>>>>>>> >>>>>>>> Is it currently in the 13.07 branch and therefor currently part of >>>>>>>> >>>>>>> the >>> >>>> 13.07 versions that people have put in production or is it just in >>>>>>>> >>>>>>> the >>> >>>> trunk that people are putting into production? >>>>>>>> >>>>>>>> What are the issues that need to be addressed before it is >>>>>>>> >>>>>>> "stabilized >>> >>>> and >>>>>>>> bug fixed"? >>>>>>>> Do any of these issues pose a significant risk to the stability of >>>>>>>> >>>>>>> the >>> >>>> rest of the functionality? >>>>>>>> >>>>>>>> Is anyone using it in production? What are their opinions of the >>>>>>>> >>>>>>> state of >>> >>>> the code and the degree of risk? >>>>>>>> >>>>>>>> Is anyone prepared to take on the task of getting it "stabilized and >>>>>>>> >>>>>>> bug >>> >>>> fixed" to a point where it can be safely included? >>>>>>>> What is the estimate of the minimum effort required? >>>>>>>> >>>>>>>> Ron >>>>>>>> >>>>>>>> >>>>>>>> On 30/09/2014 9:58 AM, Mike wrote: >>>>>>>> >>>>>>>> Why not deploy it as another hot-deploy component? Is it >>>>>>>> >>>>>>> considered a >>> >>>> "core" ERP component? >>>>>>>>> >>>>>>>>> On Tue, Sep 30, 2014 at 2:59 AM, Pierre Smits < >>>>>>>>> >>>>>>>> [hidden email]> >>> >>>> wrote: >>>>>>>>> >>>>>>>>> Jacopo, >>>>>>>>> >>>>>>>>> Back then there were already strong objections to excluding >>>>>>>>>> >>>>>>>>> components >>> >>>> from >>>>>>>>>> the release. I recall that Hans also wanted to keep the SCRUM >>>>>>>>>> >>>>>>>>> component >>> >>>> in >>>>>>>>>> the release, as well as there were proponents for BIRT and other >>>>>>>>>> components. >>>>>>>>>> >>>>>>>>>> These are good additions to the feature set of OFBiz and may be in >>>>>>>>>> >>>>>>>>> use >>> >>>> already by community members. It would be best that you solicit the >>>>>>>>>> advice >>>>>>>>>> of the entire community before a decision on excluding components >>>>>>>>>> >>>>>>>>> from >>> >>>> any >>>>>>>>>> release is taken. This affects more participants in this project >>>>>>>>>> >>>>>>>>> than >>> >>>> just >>>>>>>>>> you and the committers. >>>>>>>>>> >>>>>>>>>> Regards, >>>>>>>>>> >>>>>>>>>> Pierre Smits >>>>>>>>>> >>>>>>>>>> *ORRTIZ.COM <http://www.orrtiz.com>* >>>>>>>>>> Services & Solutions for Cloud- >>>>>>>>>> Based Manufacturing, Professional >>>>>>>>>> Services and Retail & Trade >>>>>>>>>> http://www.orrtiz.com >>>>>>>>>> >>>>>>>>>> On Tue, Sep 30, 2014 at 11:49 AM, Jacopo Cappellato < >>>>>>>>>> [hidden email]> wrote: >>>>>>>>>> >>>>>>>>>> Ok, got it. >>>>>>>>>> >>>>>>>>>> The release process that the OFBiz community is following is >>>>>>>>>>> >>>>>>>>>> based on >>> >>>> a >>>>>>>>>>> feature freeze phase, that for the 13.07 branch started more than >>>>>>>>>>> >>>>>>>>>> one >>> >>>> year >>>>>>>>>>> >>>>>>>>>> ago, during which only bug fixes are backported. >>>>>>>>>> >>>>>>>>>>> This is done in order to stabilize the branch before an official >>>>>>>>>>> release >>>>>>>>>>> is done. Since the "projectmgr" component has never been part of >>>>>>>>>>> >>>>>>>>>> the >>> >>>> 13.07 >>>>>>>>>>> >>>>>>>>>> branch then it may be unsafe to include it now just before the >>>>>>>>>> >>>>>>>>> release >>> >>>> is >>>>>>>>>>> issued. It would be better to discuss its inclusion in the >>>>>>>>>>> >>>>>>>>>> upcoming >>> >>>> new >>>>>>>>>>> release branch where it could be stabilized and bug fixed. >>>>>>>>>>> >>>>>>>>>>> Regards, >>>>>>>>>>> >>>>>>>>>>> Jacopo >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> > > -- > Ron Wheeler > President > Artifact Software Inc > email: [hidden email] > skype: ronaldmwheeler > phone: 866-970-2435, ext 102 > > |
Re: [VOTE] PROJECTMGR in upcoming release
|
|
The sub-project is a very useful Apache tool for helping projects grow.
http://db.apache.org/newproject.html is interesting reading. http://ant.apache.org/antlibs/ very minimal description about Ant sub-projects but we all use their work. http://lucene.472066.n3.nabble.com/Close-of-Apache-Lucene-s-Open-Relevance-sub-project-td4141160.html a note about the official closure of a sub-project - very clear about why and what closure means. http://en.wikipedia.org/wiki/Apache_Ivy another popular sub-project. Description implies that it started in incubation and graduated to a top-level package and then became a sub-project of Ant. http://icodebythesea.blogspot.ca/2009/04/apache-servicemix-kernel-subproject.html is an example of a sub-project moving between two top-level projects. The sub-project structure allows for more specialization within the project resources so that people who are wizards with databases, kernels, etc get to worry about data access, performance, scalability, reliability, security while others who have more domain interest get to worry about features, usability, graphic design, workflow, reporting without getting in each other's hair. It also ensures a clearer demarcation between framework, core ERP and modules. I suspect that it would clean up project communication since people could subscribe to the sub-project lists that pertained to their interests. It might be easier for the existing community to accept new committers if the new people were part of a sub-project and were not committing to the particular codebase (framework, core, etc.) that the current committers are working on. It probably would help clarify the documentation since there would be a much clearer separation of framework from core from modules since each sub-project would have its own section in the project documentation. Each sub-project would have a much better defined target audience so writing docs would be a bit simpler and the language and terminology could be more relevant to the target audience. Ron On 01/10/2014 10:17 AM, Pierre Smits wrote: > Ron, > > In the past there was a WIKI page decribing who was interested and who > was willing to work on what. I don't know whether that page still exists. > > In the past we also had a system of having committers dedicated and > committed to a subset of the trunk. This should still be feasible. But > for that you need more committers. And to get more committers, this > project needs to solicit and accept more. > > Regards, > > Pierre Smits > > *ORRTIZ.COM <http://www.orrtiz.com>* > Services & Solutions for Cloud- > Based Manufacturing, Professional > Services and Retail & Trade > http://www.orrtiz.com <http://www.orrtiz.com/> > > On Wed, Oct 1, 2014 at 4:10 PM, Ron Wheeler > <[hidden email] > <mailto:[hidden email]>> wrote: > > A defined method of deciding what moves from the trunk to a > release would solve this. > Back to my previous comment about 1 person to test and 1 person to > fix bugs (could be the same person I suppose) would be a good > starting minimum. > > Ron > > On 01/10/2014 2:56 AM, Pierre Smits wrote: > > The excuse of using PROJECTMgr in an older branch (12.x, the > latest stable > release) and testing it against trunk and therefor not > including it in a > release of a newer branch, is a lame one. > > We are diligent about this, meaning that we do follow up > against any > potential new release branch in order to be able to migrate to > the newer > branch when there is something released. > > Pierre Smits > > *ORRTIZ.COM <http://ORRTIZ.COM> <http://www.orrtiz.com>* > Services & Solutions for Cloud- > Based Manufacturing, Professional > Services and Retail & Trade > http://www.orrtiz.com > > On Wed, Oct 1, 2014 at 7:45 AM, Jacopo Cappellato < > [hidden email] > <mailto:[hidden email]>> wrote: > > The fact that someone is using it in an older branch and > testing it in > trunk is not enough to guarantee it works well with 13.07; > the trunk and > 13.07 are very different codebases. > Additionally, the "projectmgr" component has 0 unit tests; > I am not sure > about about its stability, but for example comments in > code like the > following don't make me feel super confident: > > <!-- temporary disabled because it caused a db lock with the > checkProjectMembership in projectpermission services --> > > One more point to note: since the component has not been > in the 13.07 > branch, it didn't undergo the 1-year long stabilization > phase where only > bug-fixes are backported: for example, one month ago, with > revision > 1618313, it was modified by a big commit to replace a > series of Freemarker > built-ins operation that we decided to not backport to > 13.07 but only keep > in the trunk. > > Jacopo > > On Sep 30, 2014, at 11:19 PM, Ron Wheeler > <[hidden email] > <mailto:[hidden email]>> > wrote: > > So, as far as is known from Pierre's testing, there is > no work required > > to "stabilize and bug fix" the module prior to including > it in 13.07.01? > > Anyone else have any comments on the work required to > include it in > > 13.07.01? > > Ron > > On 30/09/2014 5:13 PM, Pierre Smits wrote: > > Ron, All, > > We use the latest released branch, meaning 12.x. > We don't expose our > customers to an unstable unreleased branch, that > is still undergoing > significant changes. > > But, we test our solutions against trunk. This > enables us to identify > issues and register them in JIRA. And supply > patches when workload > > allows > > it. > > So yes, PROJECTMGR, SCRUM, etc work also in r13.x > > Regards, > > Pierre Smits > > *ORRTIZ.COM <http://ORRTIZ.COM> > <http://www.orrtiz.com>* > Services & Solutions for Cloud- > Based Manufacturing, Professional > Services and Retail & Trade > http://www.orrtiz.com > > On Tue, Sep 30, 2014 at 10:22 PM, Ron Wheeler < > [hidden email] > <mailto:[hidden email]>> wrote: > > Are you using it with a 12.04 or 13.xx? > What work is required to get it into 13.07? > > Ron > On 30/09/2014 3:06 PM, Pierre Smits wrote: > > Yes, I also have a vested interest in > keeping this (PROJECTMGR) in the > releases. It is part of our ORRTIZ:COM > solution portfolio for our > customers > and we use it internally. And I have > contributed to the improvement > > of the > > component. > > We, at ORRTIZ:COM, even use an extension > to the code base to ensure > > that > > it > also works for fixed price and internal > projects. This extension > > includes > > generating the gl transactions regarding > the cost price of each hour > registered regarding a project. > > We also use the LDAP component to connect > to our directory server > > (Apache > > Directory Server). > > Regards, > > Pierre Smits > > *ORRTIZ.COM <http://ORRTIZ.COM> > <http://www.orrtiz.com>* > Services & Solutions for Cloud- > Based Manufacturing, Professional > Services and Retail & Trade > http://www.orrtiz.com > > On Tue, Sep 30, 2014 at 4:39 PM, Ron Wheeler > > <rwheeler@artifact-software. > > com > > wrote: > It would be for me since it is one of > the components that I want to > > use. > > Perhaps the more knowledgeable people > might want to share a bit more > > of > > the background of the feature. > Is it in 12.xx.xx? > > Is it currently in the 13.07 branch > and therefor currently part of > > the > > 13.07 versions that people have put in > production or is it just in > > the > > trunk that people are putting into > production? > > What are the issues that need to be > addressed before it is > > "stabilized > > and > bug fixed"? > Do any of these issues pose a > significant risk to the stability of > > the > > rest of the functionality? > > Is anyone using it in production? What > are their opinions of the > > state of > > the code and the degree of risk? > > Is anyone prepared to take on the task > of getting it "stabilized and > > bug > > fixed" to a point where it can be > safely included? > What is the estimate of the minimum > effort required? > > Ron > > > On 30/09/2014 9:58 AM, Mike wrote: > > Why not deploy it as another > hot-deploy component? Is it > > considered a > > "core" ERP component? > > On Tue, Sep 30, 2014 at 2:59 AM, > Pierre Smits < > > [hidden email] <mailto:[hidden email]>> > > wrote: > > Jacopo, > > Back then there were already > strong objections to excluding > > components > > from > the release. I recall that > Hans also wanted to keep the SCRUM > > component > > in > the release, as well as there > were proponents for BIRT and other > components. > > These are good additions to > the feature set of OFBiz and > may be in > > use > > already by community members. > It would be best that you > solicit the > advice > of the entire community before > a decision on excluding components > > from > > any > release is taken. This affects > more participants in this project > > than > > just > you and the committers. > > Regards, > > Pierre Smits > > *ORRTIZ.COM > <http://ORRTIZ.COM> > <http://www.orrtiz.com>* > Services & Solutions for Cloud- > Based Manufacturing, Professional > Services and Retail & Trade > http://www.orrtiz.com > > On Tue, Sep 30, 2014 at 11:49 > AM, Jacopo Cappellato < > [hidden email] > <mailto:[hidden email]>> > wrote: > > Ok, got it. > > The release process that > the OFBiz community is > following is > > based on > > a > feature freeze phase, that > for the 13.07 branch > started more than > > one > > year > > ago, during which only bug > fixes are backported. > > This is done in order to > stabilize the branch > before an official > release > is done. Since the > "projectmgr" component has > never been part of > > the > > 13.07 > > branch then it may be unsafe > to include it now just before the > > release > > is > issued. It would be better > to discuss its inclusion > in the > > upcoming > > new > release branch where it > could be stabilized and > bug fixed. > > Regards, > > Jacopo > > > > > > -- > Ron Wheeler > President > Artifact Software Inc > email: [hidden email] > <mailto:[hidden email]> > skype: ronaldmwheeler > phone: 866-970-2435, ext 102 > > -- Ron Wheeler President Artifact Software Inc email: [hidden email] skype: ronaldmwheeler phone: 866-970-2435, ext 102 |
«
Return to OFBiz - User
|
1 view|%1 views
| Free forum by Nabble | Edit this page |