Wiki: 2.0 Production Release Notification

[tylerjgarland]

Is there any chance you can use this or something else to send a notification to people interested that 2.0 is ready to go? I check github from time to time, but I just though people might like something that can subscribe to when 2.0 is ready and there's an upgrade path for 1.0 users.

I am aware of the blog, but I'm just envisioning an email when 2.0 is stable. If your blog can support that, that works too!

[NGPixel]

This is a good idea.

Use wiki.requarks.io/newsletter to subscribe!

[tylerjgarland]

Thanks @NGPixel !

[TatriX]

Any ETA on the release? Is it safe to make a new wiki with 2.0 or should I wait for the final release?

[tylerjgarland]

@TatriX , it's still in beta, not production ready yet.

[fourgates]

I would also be interested in knowing if there is a rough estimate for when 2.0 will be stable. My company is interested in using Wiki.js for a project and we have a deadline of May 30th, 2019. Would you recommend we wait for 2.0 or use 1.x?

[tylerjgarland]

@fourgates , 1.0 works great for production. I use it now. 2.0 once released will have an upgrade path so you don't have to worry.

[FranklinYu]

@tylerjgarland How long will 1.x be supported after release of 2.x? It takes time to migrate.

[tylerjgarland]

I believe features are no longer being developed for 1.x

[NGPixel]

@FranklinYu 1.x is no longer being maintained, with the exception of critical security issues.

[FranklinYu]

@NGPixel @tylerjgarland So non-security bug fix (such as Requarks/wiki-v1#36) won’t be fixed? v1.0.117 will be the last release?

[NGPixel]

Unless someone else wants to fix it and make a PR, I'm no longer working on 1.x.

[mitchellknight]

Best guess for a stable 2.0? Days, weeks, months, years? I have a few projects that I would like to start on 2.0 and I'm just deciding if these projects should wait or if I should find another solution. I've had major issues with 1.x that I hope will be resolved with 2.x.

[NGPixel]

@mitchellknight This summer.

[ewaycorp]

Hi @NGPixel We are also planning to use your 2.x version as we are willing to deploy it using mysql. Please let us know how soon you will release this version and we can start using this. Currently we are trying your 2.x version and facing issue on Media Upload section. Is there any patch update for Media Upload fix. Please let us know. We are eagerly waiting for your response.
Thanks
Joydeep

[FranklinYu]

@ewaycorp I think issue for Media Upload should be discussed in a separate issue instead of here.

[NGPixel]

@ewaycorp Media Upload is not yet available. Look for future beta releases with that functionality.

[TautFlorian]

Are we going to see the Release soon @NGPixel ?
As we can see your going fast with development 👍

[tylerjgarland]

@TautFlorian , this summer.

[BrendanBall]

I just tried out the latest 2.0 using docker, and it feels like an alpha product, not a beta. I can almost not do anything. Most of the core features are greyed out or broken.

[NGPixel]

[aiveras]

We are very excited about the new version, when will it be released, can you estimate it better now that the summer is about to end?

[tylerjgarland]

Don't forget summer in the southern hemisphere is in December.

On Fri, Aug 16, 2019 at 1:18 AM aiveras [e-mail] wrote:

We are very excited about the new version, when will it be released, can
you estimate it better now that the summer is about to end?

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/Requarks/wiki/issues/755?email_source=notifications&email_token=AIDWKXTXBVWSMO2QMNWBNS3QEZPDZA5CNFSM4GWOEMDKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD4N74GQ#issuecomment-521928218,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AIDWKXXXKND73D6N5UWBUCTQEZPDZANCNFSM4GWOEMDA
.

[FranklinYu]

At least this is better than releasing a beta-quality version in stable channel. If I have to choose, I prefer to stay in the safe side (or I can just use the beta release).

[herrlich10]

Very excited to see the rapid progress and appreciated the hardworking of the maintainer.
Is it possible to release an upgrader from 1.0.x to current beta version, so that users experiencing issues with v1 (which is no longer maintained) can at least try the new beta version (of course, at their own risk) and, if with luck, continue working with wiki.js in their projects. I believe this will also speed up the testing process of the new version.
Many thanks for providing this amazing tool!

[tylerjgarland]

Yeah, we've been waiting for someone to create a PR for the upgrade tool
but no takers yet. Know anyone?

On Tue, Sep 10, 2019, 7:59 PM herrlich10 [e-mail] wrote:

Very excited to see the rapid progress and appreciated the hardworking of
the maintainer.
Is it possible to release an upgrader from 1.0.x to current beta version,
so that users experiencing issues with v1 (which is no longer maintained)
can at least try the new beta version (of course, at their own risk) and,
if with luck, continue working with wiki.js in their projects. I believe
this will also speed up the testing process of the new version.
Many thanks for providing this amazing tools!

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/Requarks/wiki/issues/755?email_source=notifications&email_token=AIDWKXSGG7CKR7EOILKV3D3QJBNKBA5CNFSM4GWOEMDKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD6NDCYQ#issuecomment-530198882,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AIDWKXR74W35IY3ARAIQYMDQJBNKBANCNFSM4GWOEMDA
.

[another-guy]

I am currently conducting a comparative review of Wiki.js (2.0), Confluence, xwiki, Notion.so, and MediaWiki.

Wiki.js and xWiki are the most appealing systems I'm going to recommend my company to pick from. However, without at least a tentative release date it's going to be very hard to "sell" Wiki.js to the upper management.

Am I looking at the right place for the milestones? If so, the release is already significantly behind (which I am fine with) — correct me if I'm wrong. I mean, we're past _summer_, and no update is made in this issue.

Don't get me wrong. I'm all for "it takes what it takes" to release a stable product or service. Yet, I'm also all for the clear communication of the timeline/date.

P.S. I am well-aware it's open source and people don't get payed for their work here. Thus, please don't interpret my message as a demanding one.
Thank you for all of your work Wiki.js contributors! 👏 👏 👏

[aam1r]

The latest update that I saw was on Twitter: https://twitter.com/requarks/status/1183958286581878784

And also this tweet: https://twitter.com/requarks/status/1184444172088102912

No specific dates though, but good progress being made it seems 🙂

[another-guy]

The latest update that I saw was on Twitter: https://twitter.com/requarks/status/1183958286581878784

And also this tweet: https://twitter.com/requarks/status/1184444172088102912

No specific dates though, but good progress being made it seems 🙂

Thank you for these references! I think, our organization will need to pass on wiki.js for now. Hopefully, we're going to give it a chance some time later.

[jonathanrbowman]

Thanks so much for all the work on this project - excited to see the rc hit the scene!

Is there already a docker image for it, or has that not been posted up yet?

[aiveras]

You can download it from the dockerhub: https://hub.docker.com/r/requarks/wiki/tags
The tag is still the beta one, but it's already the new release candidate, as you can see on the creation date.

[tylucaskelley]

Is there a place to see a roadmap / remaining backlog of issues? Deployed the latest release candidate just now but noticed a ton of things still grayed out in the admin dashboard and missing features like profiles editing, logging, etc.

Don't interpret this as me being pushy or demanding - I think this is a great effort and once done it'll be the obvious go-to for the organization I work with! Just want to get an idea of where things are at and what should be expected for the initial 2.0 release.

[NGPixel]

Final 2.0 release will be available in the coming days. No new features will be introduced until that release. The focus right now is on fixing bugs.

[Cylix]

For people who are looking into switching to the v2, just sharing my experience.

We are using wiki v1 for our company. We have about 30 users and 300 pages so that you have an idea of our scale.

I switched to the v2 today. Overall, I'm satisfied with the result though there are a few issues and the transition requires a bit of manual work to fully get it done.

I listed the issues I encountered in https://github.com/Requarks/wiki/issues/1174.

In particular:

• some links may be broken due to some incompatibilities between v1 and v2 if your internal links contain underscores/dots, so may need to manually fix these links
• permissions are not working as expected, there is some glitch somewhere. Our team being small, that's less of a problem for us for now, but this part is not as solid as the v1 for now
• there is some page content size limitation due to the DB config. If you currently have some pages with a looooot of content (I don't know the limit, but it is pretty large), they will not make it all the way through to the v2 and you will have to break them down.

My team will start using the v2 next week, so I'll keep an eye on whether there are more issues or if it is smooth, but so far it looks good on my end besides what's listed above.

[NGPixel]

Stable 2.0.1 is now available! A detailed blog post and a newsletter is coming in the next few days.

[zhinuok]

Stable 2.0.1 Search function is yet dose not work? The search function seem still doesn't to work often when I use.

[FranklinYu]

@zhinuok Please create a new issue.