Feature #772

easySDI extensions definition

Added by Magoni Bruno over 5 years ago. Updated over 4 years ago.

Status:AcceptedStart date:
Priority:NormalDue date:
Assignee:-% Done:

0%

Category:-
Target version:Unplanned
Sponsor: Ergonomic impact:
Functional impact:

Description

1. Versions' name are managed uniformly in all easySDI Joomla extensions (name is strictly the same and is driven by build scripts). Here are some proposal for uniform and industrialized extensions' definition:
  • version should follow Semantic Versionning rules as explained in http://semver.org (i.e. 4.2.0-beta.3+[build number])
  • date should be also defined automatically with build script using the current date; <creationDate> in manifest xml file must be used to store date of creation/release of the extension instead of <releaseDate> which is not displayed in backoffice extensions management interface and should be removed from easySDI manifest files
  • author should be a "constant" which is "easySDI Community" (easySDI mark starts lower case and not upper case)

2. Adding to this, naming review of easySDI extensions is proposed. I would also propose to simplify numerous extensions which was initially performed for bringing backoffice templating and indicators plugin by removing them (are such plugin really indispensable as it need one specific plugin for each desired indicator ?).

Name Location Type
easySDI Site Package
easySDI Basket Site Module
easySDI Monitor Site Plugin
easySDI Catalog Administrator Component
easySDI Contact Administrator Component
easySDI Map Administrator Component
easySDI Monitor Administrator Component
easySDI Service Administrator Component
easySDI Dashboard Administrator Component
easySDI plugin Button : Orders Site Plugin
easySDI plugin Button : Users Site Plugin
easySDI Contact Site Plugin
easySDI plugin Info : Downloadable ressources Site Plugin
easySDI plugin Info : Downloads Site Plugin
easySDI plugin Info : Extractables ressources Site Plugin
easySDI plugin Info : Extractions Site Plugin
easySDI plugin Info : Order Response time Site Plugin
easySDI plugin Info : Organisms Site Plugin
easySDI plugin Info : Resources Site Plugin
easySDI plugin Info : Users Site Plugin
easySDI Service Site Plugin
easySDI Admin Positions Administrator Template
easySDI Shop Administrator Component
easySDI - Administration Buttons Administrator Module
easySDI - Administration Information Administrator Module
easySDI Core Administrator Component

easysdi_extensions.png (43.2 KB) Magoni Bruno, 07/06/2014 10:06 PM

History

#1 Updated by Magoni Bruno over 5 years ago

  • File easysdi_extensions.png added
  • Description updated (diff)

#2 Updated by Magoni Bruno over 5 years ago

  • File deleted (easysdi_extensions.png)

#4 Updated by Magoni Bruno over 5 years ago

  • Description updated (diff)

#5 Updated by Magoni Bruno over 5 years ago

  • Description updated (diff)

#6 Updated by Magoni Bruno over 5 years ago

  • Description updated (diff)

#7 Updated by Magoni Bruno over 5 years ago

  • Subject changed from Versions' date and author to easySDI extensions definition
  • Description updated (diff)
  • Status changed from New to Request For Comments
  • Assignee changed from Magoni Bruno to Technical Committee

#8 Updated by Magoni Bruno about 5 years ago

  • Status changed from Request For Comments to Request For Votes
  • Assignee changed from Technical Committee to Steering Committee

1. Verifying if semantic version is compliant with PHP API (without build number) and to add build number inside extensions description + recovering servlets versions from POM into servlet display name
2. Be aware that translation terms must follow same logical

Accepted by everyone...

#9 Updated by Magoni Bruno about 5 years ago

+1

#10 Updated by Mérour Xavier about 5 years ago

+1

#11 Updated by Teixeira Jérôme about 5 years ago

+ 1

#12 Updated by Magoni Bruno about 5 years ago

  • Status changed from Request For Votes to Accepted
  • Assignee deleted (Steering Committee)

#14 Updated by Van Hoecke Hélène about 5 years ago

In 4.2.0 rc1 :

date should be also defined automatically with build script using the current date; <creationDate> in manifest xml file must be used to store date of creation/release of the extension instead of <releaseDate> which is not displayed in backoffice extensions management interface and should be removed from easySDI manifest files

#15 Updated by Magoni Bruno almost 5 years ago

  • Target version set to Unplanned

#16 Updated by Magoni Bruno over 4 years ago

  • Target version deleted (Unplanned)

#17 Updated by Magoni Bruno over 4 years ago

  • Target version set to Unplanned

Also available in: Atom PDF