Hi Pierre,
Before answering, we have 1st to change the current situation. We decided to rather use a next than old demo*. For now I'll simply use R17 as old and
R18 as stable.
* https://markmail.org/message/j3am5umycuzdixzs
Le 04/11/2021 à 16:16, Pierre Smits a écrit :
HI all,
Currently we have:
- demo-trunk.ofbiz.a.o: sporting the latest commit (and refreshed every
day) in trunk, intended for contributors who want to check what differs
between the latest merged commit in trunk and the development
(feature/bugfix) branch in their own environment;
- dem-latest.ofbiz.a.o: sported the latest commit (and refreshed every
day) of the latest release branch (currently at 17.12), intended for
contributors who want to check what differs between the latest commit in
the release branch and the development (feature/bugfix) branch in their own
environment.
As both can change overnight, potential adopters can have a hard time
keeping track of the changes when evaluating OFBiz on its merits. Often
adopters won't go for what the latest is in a branch, and we don't
encourage them to do so but rather use a release.
Would it therefore not be prudent to show them a demo that is based on an
actual release?
We could use demo.ofbiz.a.o for that. Which only changes when a new release
has been made available.
Having that in play we also provide our contributors with an extra means to
check the development (feature/bugfix) branch in their own environment
against.
What are your thoughts?
Met vriendelijke groet,
Pierre Smits
*Proud* *contributor** of* Apache OFBiz <https://ofbiz.apache.org/> since
2008 (without privileges)
Proud contributor to the ASF since 2006
*Apache Directory <https://directory.apache.org>, PMC Member*
