What we could do is still support it but don't link it from main site and such
Because it's very convenient for committers to have another running trunk system
Jacques
From: "Pierre Smits" <[email protected]>
I agree.
Demo environments is not for OFBiz developers.
If you want to have an OFBiz developer to have a viewpoint on trunk where
they can experience what has been changed in trunk I believe that there are
betters means available and in place already (SVN, CI reports, etc)
As far as I can see it, a demo environment of trunk needs to have a regular
(daily?) deployment of code and demo data. This could potentially lead to
having an upload being done to the demo location at just the moment that a
OFBiz committer has partially uploaded his commits to trunk and the demo
breaks during build and anyone (not only OFBiz developers) experiences a
broken demo. Giving the community unnecessary headaches about fixing the
demo environment than OFBiz.
Look at how often Jacques had to step in to look at why demo-trunk had been
broken.
This is not something we should want to have...
Regards,
Pierre
Op 23 april 2012 09:27 schreef Jacopo Cappellato <
[email protected]> het volgende:
On Apr 23, 2012, at 9:21 AM, Pierre Smits wrote:
> I also believe that Jacopo said that something is in the rules,
regulations
> and/or guidelines of the ASF about the same issue.
We simply have to make sure it is always clear when a resource is
unreleased and intended for OFBiz developers only or released and intended
for larger audience.
Jacopo
