Support from Acquia helps fund testing for Drupal Acquia logo

Comments

kruhak created an issue. See original summary.

kruhak’s picture

Issue summary: View changes
kruhak’s picture

Issue summary: View changes
kruhak’s picture

Issue summary: View changes
kruhak’s picture

Issue summary: View changes
kruhak’s picture

Issue summary: View changes
Bwolf’s picture

Hi What is the status of a the Beta version of this module?

Cheers, Brian.

antongp’s picture

Issue summary: View changes
antongp’s picture

Issue summary: View changes
Bwolf’s picture

Hi Just checking in.. What is the status of a the Beta version of this module?

antongp’s picture

Issue summary: View changes

Majority of tickets which were in beta1 plan before, are included in alpha5 release: https://www.drupal.org/project/bibcite/releases/8.x-1.0-alpha5

antongp’s picture

Title: [meta] Roadmap track (1.0-beta1) » [meta] 8.x-1.0-beta1
antongp’s picture

Issue summary: View changes
antongp’s picture

Issue summary: View changes
Bwolf’s picture

Hi Just checking in.. What is the status of a the Beta version of this module?

AardWolf’s picture

@bwolf Hi.
In this moment we have some sort of finished:
Footnotes integration module.
PubMed module.
And Crossref.

All of it not 100% completed. But working.
We have some bugs.
Major bug about rest: #2983288 for example.
And there is a lot of work.

Please be patient ))

antongp’s picture

Issue summary: View changes
Bwolf’s picture

It looks like things are moving forward on the module!

It there anything others can do to help with beta testing etc.

Thanks for all the hard work on this project.

antongp’s picture

Hello @Bwolf.

I think, for the moment it's compatibility with Drupal 8.7.x. We released alpha9 with compatibility fixes, but could miss something minor. So, feel free to report about any other issues.

Also, it would be nice to know about real examples of using BibCite with RESTful Web Services. References are Drupal's entities, import/export is built with use of core's Serialization. So, by design it's possible to expose BibCite data with core's RESTful Web Services and even render in BibTeX and other formats, but we haven't paid much attention to this yet.

From upcoming changes, revisions support is probably most major change and it would be nice to get a feedback once it's committed.

Thanks!

mtift’s picture

I see this has not been updated since 14 May 2019. Is this list of issues still accurate for determining the Beta release?

(I'm trying to figure out where I can best help to get this module to Beta.)

antongp’s picture

Issue summary: View changes

Hi @mtift

Is this list of issues still accurate for determining the Beta release?

- Nope. It's time to update the roadmap.

So, reference entities are revisionable and support editorial workflows already (in dev).

We also made contributor and keyword entities fieldable:
#3068783: Make Contributor entities fieldable
#3070474: Make Keyword entities fieldable
and also added default views for them to show related references on their pages:
#2947908: Link author to contributor entities and see their publications
#2951081: Keywords and link between references

We also noticeably restructured routing/pages and made smaller improvements within
#3066382: [meta] UI improvements
(a few issues are remaining but they're in progress)

Full list of changes and important notices can be found in the changelog

We decided to not depend on documentation readiness in this release and probably in any other release. We also do not consider deprecated packages as blocker for beta1 release anymore (more probably it'll be handled later). And we do not focus on RESTful Web Services support fixes within this release (there are issues in some use cases).

Most major changes for beta1 are already done in dev. Most major from remaining is Footnotes integration, but first we need to add auto-generation functionality for Citekey field. Plus a few smaller issues to resolve.

Any feedback for latest dev will be helpful.

Thanks!

hunterbuchanan’s picture

Since it's been about a year since the release of 1.0-Alpha10, and with Drupal 9 release approaching soon, it might be a good time to revisit this. Many helpful fixes and changes have been committed to dev. Is a 1.0-Beta1 release on the horizon, or can we at least wrap the commits up until now into an Alpha11 release?

jurveen’s picture

Is there an update on the Bibcite beta? It's been very quiet in the last months.

Rhodungeon’s picture

I'm also waiting for the beta version. This module could improve drastically my future website.

johnnny83’s picture

Same here

TLWatson’s picture

+1

hxdef’s picture

Hi @hunterbuchanan

Is a 1.0-Beta1 release on the horizon, or can we at least wrap the commits up until now into an Alpha11 release?

We're going to focus on a 1.0-Beta1 release rather than working on the alpha versions. Some features from the rodmap still need attention.

Thank you all for your interest in the development of the project! I hope that in the near future we will be able to get things off the ground.

hopfrog’s picture

Good job. We look forward to

hunterbuchanan’s picture

@hxdef I appreciate the response! At this point, we're a few months away from Drupal 8 going EOL, and more folks are interested in a stable D9 release:

#3222643: Create a stable D9 release?

It looks like there are only two tasks keeping the module from a beta release, but they haven't been touched in quite a while:

#2959818: Footnotes integration
#3006180: Editors and other roles shown as authors

It looks like the bug fix in question is fixed for the vast majority of users on the dev branch, and while the feature request might be nice to have, I'm not convinced it's required for beta1. Would it be feasible to commit to some sort of stable D9 release between now and when D8 goes EOL? Maybe these tasks can be completed by then, or they can be left out of the beta1 release, or we'd be happy with an alpha11 release in the meantime.

I don't mean to be pushy, we're very appreciative of the work that's been done for this module! We've all been using the dev branch on production sites without issue for a long time, and it would be a bummer to not have a D9-compatible release for this module by the time D8 is gone. Thanks in advance!

hxdef’s picture

Issue summary: View changes

Hello everyone!
@hunterbuchanan thanks for your feedback. Let me provide some updates about the beta release status.

Current plan should be modified a bit:
- Remove #2959818: Footnotes integration - In fact the work is almost done, but we decided to add this as a separate module. So, it won't delay the release. Follow updates in the corresponding issue.
- Remove #3006180: Editors and other roles shown as authors - It's still looks like a complex task. At the same time this is not critical to resolve it for the new beta release and we decided to postpone it for a while.
- Add #2992234: Deprecated packages in dependencies - this is the major problem that must be resolved before the release. Actually this task takes most of our time.

I updated the release plan. Thank you for your patience!

hxdef’s picture

Status: Active » Fixed

Hello everyone! Beta1 release is finally here and I would like to thank everyone involved 🎉
Without your help, progress would have been much less.

For this release we were unable to add changes related to #2992234: Deprecated packages in dependencies. The decisive factor was the end of the life of Drupal 8 (November 2021). To provide an ability for users to switch to the new version of the module up to this point, the priority was given to creating a new release.

As for the issue itself, in this case it all depends on a third-party library, so it is rather difficult to predict when we will get a suitable result. However, I think we already have some good progress. Follow the issue to see updates.

Thank you!

robcarr’s picture

Thanks for all the work on the new Beta release.

However, cannot install 2.0.0-beta1 via Composer in Drupal 9 due to dependency on audiolabs/bibtexparser dev. #3212586: Require audiolabs/bibtexparser:^1.0 instead of audiolabs/bibtexparser:dev-master

hxdef’s picture

Hello @robcarr

Thanks for bringing this issue to the attention. All the necessary changes have already been added to the dev-branch.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.