[MGNLRSSAGG-101] Make RSS Aggregator module compatible with Magnolia 5. Created: 09/Oct/13  Updated: 21/Nov/13  Resolved: 18/Nov/13

Status: Closed
Project: Magnolia RSS Aggregator Module
Component/s: None
Affects Version/s: 2.1
Fix Version/s: 2.2

Type: Task Priority: Critical
Reporter: Aleksandr Pchelintcev Assignee: Aleksandr Pchelintcev
Resolution: Fixed Votes: 0
Labels: None
Σ Remaining Estimate: Not Specified Remaining Estimate: Not Specified
Σ Time Spent: Not Specified Time Spent: Not Specified
Σ Original Estimate: Not Specified Original Estimate: Not Specified

Issue Links:
relation
is related to MGNLSTK-1258 Update RSS Aggregator module dependen... Closed
Sub-Tasks:
Key
Summary
Type
Status
Assignee
MGNLRSSAGG-102 Create a separate workspace and nodet... Sub-task Closed Aleksandr Pchelintcev  
MGNLRSSAGG-103 Migrate Dialogs and controls to Magno... Sub-task Closed Aleksandr Pchelintcev  
MGNLRSSAGG-104 Develop RSSAggregator app. Sub-task Closed Aleksandr Pchelintcev  
MGNLRSSAGG-105 Migrate RSSAggregator-related templat... Sub-task Closed Aleksandr Pchelintcev  
MGNLRSSAGG-106 Migrate RSS Importer to Magnolia 5. Sub-task Closed Aleksandr Pchelintcev  
MGNLRSSAGG-107 Migrate RSS generators to Magnolia 5 Sub-task Closed Aleksandr Pchelintcev  
MGNLRSSAGG-110 Use new i18n framework for RSSAggregator Sub-task Closed Aleksandr Pchelintcev  
MGNLRSSAGG-111 Update RSSAggregator module installat... Sub-task Closed Roman Kovařík  
MGNLRSSAGG-115 Fix test failures caused by migration... Sub-task Closed Aleksandr Pchelintcev  
Template:
Acceptance criteria:
Empty
Task DoR:
Empty
Release notes required:
Yes
Date of First Response:
Epic Link: RSS Aggregator 2.2
Sprint: 5.2-rc2

 Comments   
Comment by Mikaël Geljić [ 06/Nov/13 ]

Not all subtasks are resolved, either keep this parent issue open/in progress till 2.2 final, either move remaining subtask to another version

Comment by Daniel Lipp [ 14/Nov/13 ]

reopened because a subtask had been reopened - pls re-resolve together with that subtask

Generated at Mon Feb 12 07:05:33 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.