Alfresco Wiki Versioning section "Version meta-data, version numbers and version labels":
The generation of the version label
can be customized by creating a
version label policy behaviour and
registering it in place of the default
version label policy.
Where is this documented?
Related
I'm working on my project's versioning and I want to adopt the guidelines from here.
I just have one question that either I didn't get or the material didn't cover. How should the release version look?
My understanding is that having a pre-release label is for internal development, as well as the build metadata. When building the artifacts for a release version, should you strip all the labels and keeping only the version core, i.e.: major.minor.patch? What label could get into source control and which must never do?
In the spec, there are release and prerelease versions. A release version does not have zero for the major field or have a prerelease tag attached. You are free to do whatever you like with regards to build-meta.
In the real world, a "release" is anything you've published, such that it is publicly available. So for internal use, do what you want, but for external use, follow the spec. In other words, you can release a prerelease version by publishing it.
Is it possible to use charts in ExtJS 6.6 Community Edition?
I try to add them as I usually do in my app, based on ExtJS 6.2 GPL version, but it does not work. Perhaps packages need to be somehow explicitly added via npm?
In addition, in the documentation for ExtJS 6.6 CE I do not see the description of the corresponding classes.
Unfortunately charts are not available in the CE edition. Here is an excerpt from the Sencha Software License Agreement, and specifically the "8. ADDITIONAL LICENSE TERMS APPLICABLE TO THE COMMUNITY EDITION" section (emphasis mine):
In the event You have obtained a Sencha Ext JS Standard Community
Edition license (the “Community Edition”), the following terms apply
in addition to the General Terms described in Section 2 above. Please
note that the Community Edition does not include all the software
packages that Sencha Ext JS includes, and in particular does not
include Ext JS Classic, Ext JS Charts, and many Ext JS fonts and
themes.
I found this on the hippo cms licence page.
All included libraries are distributed either under the Apache
Software License 2.0 or a compatible license, with the exception of
the Sencha ExtJS library. Sencha ExtJS is distributed under GPL v3,
with an Open Source License Exception for Applications. If you
customise or redistribute Hippo Community Edition code that uses ExtJS
components, then you must comply to their open source licenses - or
buy an appropriate developer license from Sencha.
As I want to distribute my product I would like to exclude everything that use Sencha ExtJS to keep the product in Apache 2.0 licence.
So my question is, which parts of HippoCMS need Sencha ExtJS to work ?
Because, for example if we can't create date without ExtJS, it's really bad because I (and the client) would like to use it, so that's why I am asking you.
Check out this discussion on our Community forum .
https://groups.google.com/forum/embed/?place=forum/hippo-community&showsearch=true&showpopout=true&showtabs=false&parenturl=http://www.onehippo.org/7_8/library/about/cms-forums.html#!searchin/hippo-community/Sencha$20ExtJs$20/hippo-community/DWbI32Mw5Rk/dXvqZa-dgdQJ
Yesterday I downloaded the new Agile Toolkit 4.3 and found that the licensing and subscription model has been changed. Additionally a "developer sandbox" has been included which launches when the toolkit is first run and requires me to login with a registered account.
While I understand the reasons for these changes, and I'm fully supportive, the sandbox appears to be unnecessarily restrictive. However, there seems to be no easy way to bypass the sandbox, and logging in to the sandbox in a vanilla install of 4.3 leads to a screen where you are forced to choose between a pre-canned Admin or Frontend site.
The key reason for me to upgrade from 4.2 to 4.3 is the introduction of an Application class to support RESTful services. I have no need for either an Admin, nor a Frontend web user interface and yet the sandbox does not provide this option.
Is it possible to bypass the sandbox setup process and, if so, how would one go about doing this?
Looking at this in a different way, the folder structure of the ATK4 library seems to have changed under 4.3. Version 4.2 included documentation on the folder structure and how a developer should setup their application in relation to that structure. I have been unable to find corresponding documentation for Version 4.3 which would give clear guidance on how to build an application around the toolkit without relying on the included sandbox.
Hi Tim (i'm author of Agile Toolkit)
Agile Toolkit framework will continue to be available on github. You will find link to github on the bottom of the page, simply select branch 4.3. All of the documentation still applies and you can use the framework (you still need to respect the license). Github does not contain "admin" or "frontend", it is included for the convenience of new users.
The licensing terms has slightly changed, Agile Toolkit has always used AGPL and Commercial licensing. The reason to introduce the sandbox is because developers were not respecting the license terms. I also wanted to give easier ability to deploy projects for new PHP developers and for security it can only be done through sandbox.
Here is a blog-post outlining all of the changes: http://www4.agiletoolkit.org/blog/rebooting-agile-toolkit
The folder structure have changed, but it must still be compatible with the 4.2 branch. I've adopted the usage of "public" folders for improved security, but please do look into PathFinder documentation on how to customise folder structure.
I installed the latest version of MediaWiki (1.23.1) and was surprised not having a responsive design as Wikipedia has. Is there a way to enable such feature (if it exists) or should I switch to another wiki engine?
To get the same responsiveness as Wikipedia have, you need to install Extension:Mobile Frontend.