Skip to content

v30 oldstable#819

Open
zamentur wants to merge 98 commits intomasterfrom
v30
Open

v30 oldstable#819
zamentur wants to merge 98 commits intomasterfrom
v30

Conversation

@zamentur
Copy link
Copy Markdown
Contributor

You can use this branch to upgrade onto oldstable branch.

We are planning to make master to be on oldstable branch by default, after that there will be a stable branch dedicated to latest version. A mechanism should be added in yunohost core to manage several channel of sources.

So it's a temporary branch.

PR Status

  • Code finished and ready to be reviewed/tested
  • The fix/enhancement were manually tested (if applicable)

Automatic tests

Automatic tests can be triggered on https://ci-apps-dev.yunohost.org/ after creating the PR, by commenting "!testme", "!gogogadgetoci" or "By the power of systemd, I invoke The Great App CI to test this Pull Request!". (N.B. : for this to work you need to be a member of the Yunohost-Apps organization)

alexAubin and others added 9 commits June 17, 2025 12:49
* Manage oldstable version (#714)

* [enh] channel wording

* [fix] Bad source_id and repeated lines

* [fix] Why remove maintenance:repair ???

* [fix] Stay on oldstable if it was not on last major version

* [fix] Patches on oldstable setup

* [fix] Old helpers key

* [enh] oldstable as the default version

* [enh] Auto update after channel change

---------

Co-authored-by: Kayou <pierre@kayou.io>
@zamentur
Copy link
Copy Markdown
Contributor Author

!testme

@yunohost-bot
Copy link
Copy Markdown
Contributor

🚀
Test Badge

@zamentur
Copy link
Copy Markdown
Contributor Author

!testme

@yunohost-bot
Copy link
Copy Markdown
Contributor

🚀
Test Badge

@tomdereub
Copy link
Copy Markdown
Contributor

On webadmin, update says this :
image
But nextcloud is actually 30.0.13.

@rodinux
Copy link
Copy Markdown
Contributor

rodinux commented Sep 15, 2025

On webadmin, update says this : image But nextcloud is actually 30.0.13.

I think we should wait the maj upgrade to 31.* to avoid this mistake and just be aware...

@tomdereub
Copy link
Copy Markdown
Contributor

tomdereub commented Sep 18, 2025

I think we should wait the maj upgrade to 31.* to avoid this mistake and just be aware...

For me it's already solved.

@tomdereub
Copy link
Copy Markdown
Contributor

It's time to create v31 oldstable ?

@rodinux
Copy link
Copy Markdown
Contributor

rodinux commented Feb 13, 2026

It's time to create v31 oldstable ?

Hello, it could be a good idea to have a v31 branch also, indeed...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.