[MAGNOLIA-5703] Make sure Content2Bean can be dropped one day Created: 28/Feb/14 Updated: 06/May/14 Resolved: 24/Mar/14 |
|
| Status: | Closed |
| Project: | Magnolia |
| Component/s: | content2bean |
| Affects Version/s: | 4.5.17, 5.2.3 |
| Fix Version/s: | 4.5.18, 5.2.4 |
| Type: | Task | Priority: | Neutral |
| Reporter: | Daniel Lipp | Assignee: | Daniel Lipp |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | quickwin | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Template: |
|
||||||||
| Acceptance criteria: |
Empty
|
||||||||
| Task DoR: |
Empty
|
||||||||
| Date of First Response: | |||||||||
| Description |
|
Node2Bean is there to replace Content2Bean (since |
| Comments |
| Comment by Milan Divilek [ 03/Mar/14 ] |
|
5.2.3 is coming out in next few days and is currently being closed down, it is not possible to squeeze this ticket in one the last moment. Moved to 5.2.4. |
| Comment by Milan Divilek [ 18/Mar/14 ] |
|
Reopen: instead.". I think in both it should be deprecated since 4.5.18 |
| Comment by Daniel Lipp [ 24/Mar/14 ] |
|
thx for spotting 1.) + 2.) -> fixed now. Didn't fix 3.) as discussed - IMHO that would be wrong. When fixing 1.) (porting to 5.2.x branch) I cherry picked single commits instead of doing all those in one in order to ease review or diffing 5.2.x to master. |