En 30/06/25 02:05, David Lecompte escribió:
I had to enable the testing repository for ecne to have Abrowser 140, but I
just did a fresh install of ecne in a vm from the latest netinstaller and it
is Abrowser 140. Was it moved to the main repository already?

Yeah, after I had the jitsi meet issue, I did spend some time testing regular use cases, and checking some details on the release, and nothing seemed that was an anti-feature so far.

If for whatever reason there is plenty of feedback we can hold it longer for review, otherwise waiting one week for some report sounds about right before moving on. Remember that Abrowser is under the rapid release, which mean a release almost monthly, we might need to come up with some routines to review effectively and efficiently for changes that might come up and be an issue to  the community at large.

Anyone has ideas on the subject?

Regards

--
Luis A. Guzmán G.
http://ark.switnet.org

Capitulo Mexicano de Software Libre - https://cmxsl.org
Software Libre con raíz ética, acción local y visión nacional.

Por tu propio bien, y en solidaridad a todos, elige la libertad.
¡Sé Libre! - https://fsfla.org/selibre/

Attachment: OpenPGP_0x35AD8DB3BE2C988C.asc
Description: OpenPGP public key

Attachment: OpenPGP_signature.asc
Description: OpenPGP digital signature

_______________________________________________
Trisquel-devel mailing list
[email protected]
https://listas.trisquel.info/mailman/listinfo/trisquel-devel

Reply via email to