Port Blog API to Drupal 8 [#2696279]

Comment #1

29 March 2016 at 16:25

zacpod created an issue. See original summary.

Log in or register to post comments

Comment #2

cweagans

He/Him

English

Boise, ID, USA

CreditAttribution: cweagans as a volunteer commented 29 March 2016 at 16:27

I have no plans to port it myself. New maintainers are welcome.

Log in or register to post comments

Comment #3

alecsmrekar CreditAttribution: alecsmrekar commented 24 January 2017 at 20:48

I'm preparing a port over here: https://bitbucket.org/alecsmrekar/blogapi

Log in or register to post comments

Comment #4

alecsmrekar CreditAttribution: alecsmrekar commented 20 March 2017 at 10:13

Status:

Active

» Fixed

We have a new D8 release.

Log in or register to post comments

Comment #5

DamienMcKenna

NH, USA

CreditAttribution: DamienMcKenna at Mediacurrent commented 23 March 2017 at 00:57

Title:	Drupal 8	» Port Blog API to Drupal 8
Version:	7.x-2.0-rc1	» 8.x-1.x-dev
Status:	Fixed	» Active

@alecsmrekar: Excellent work!

BTW you should tag a release on the 8.x-1.x branch so that there's something solid for people to test with.

Log in or register to post comments

Comment #6

alecsmrekar CreditAttribution: alecsmrekar commented 23 March 2017 at 13:59

@DamienMcKenna

Good idea, I created an alpha release!

BTW can you help me opt-in on the security advisory coverage at least for the D8 branch? I don't have the permissions needed to edit the actual module.

Log in or register to post comments

Comment #7

DamienMcKenna

NH, USA

CreditAttribution: DamienMcKenna at Mediacurrent commented 30 March 2017 at 21:59

Status:

Active

» Fixed

You cannot opt-in an alpha, beta or rc-release module, only stable releases.

That said, now that there's an alpha release I think this can be fixed and everything else created as separate issues.

You might create a new issue for planning the 8.x-1.0 release and then use the "parent issue" field to indicate what needs to be completed, then add issues for documentation, etc.