Documentation #1437

Feature #418: === Configuration & Build ===

Feature #1686: == Release procedures and pre-release actions ==

Release requirement: Update example scripts

Added by wuttke about 3 years ago. Updated almost 2 years ago.

Status:RejectedStart date:30 May 2016
Priority:NormalDue date:
Assignee:-% Done:

0%

Category:-
Target version:-

Description

During a sprint, examples are updated in Examples/python/...

Upon release, they need to be moved to the Drupal site.

An elegant solution may require some directory reorganization. This, in turn, is also related to the backup issue #1263

History

#1 Updated by wuttke about 3 years ago

  • Subject changed from automatically update example scripts upon library release to Release requirement: Update example scripts

There is no simple way to automatize this. We may need to write a script that directly accesses the MySQL data base.

#2 Updated by herck about 3 years ago

From https://www.drupal.org/node/811950

There is very rarely any justification for directly interacting with the database. Drupal provides an API and high-level functionality for storing and retrieving node content. Authors of contrib modules have created tools for importing delimited data and XML in many common formats. You should exhaust all of those avenues before you consider directly interacting with the database, and if you do, you should first have a thorough understanding of where and how Drupal stores data.

I agree that with that viewpoint. We should not start messing with the database directly, but implement this in the drupal-way (using the Drupal API for accessing the database)

#3 Updated by wuttke about 3 years ago

Under Drupal 8 (#1451), we might use RESTful services, described at https://drupalize.me/blog/201401/introduction-restful-web-services-drupal-8

#4 Updated by herck about 3 years ago

  • Status changed from Sprint to Backlog
  • Target version deleted (Sprint 31)

Postponed until we decide what to do with #1451

#5 Updated by wuttke about 3 years ago

Depends. If we do the big form factor renaming (#1065), then we need to update many examples. If no automatism is available, we need to do it by hand.

#6 Updated by herck about 3 years ago

Doing it by hand once will always be less work than providing an automatic way. So implementing the automatic way only makes sense if we don't have to redo it a month later.

#7 Updated by wuttke over 2 years ago

  • Parent task changed from #1301 to #1686

#8 Updated by pospelov almost 2 years ago

  • Status changed from Backlog to Rejected

Rejected, see #1823

Also available in: Atom PDF