smartparens icon indicating copy to clipboard operation
smartparens copied to clipboard

Please new tag release

Open arankaren opened this issue 5 years ago • 4 comments

Hello dear developer, I am writing packages for my community and I need a new tag. You would be so kind in doing a new tag

arankaren avatar Feb 05 '20 22:02 arankaren

Hi,

I'm packaging 1.11.0 for Debian, and the package will be inherited by all derivatives. Ubuntu 20.10 would be the most prominent release this year. To get a newer release into 20.10 (and its derivatives), please consider tagging a new release sometime before June or July.

Thank you for maintaining this package. Cheers, Nicholas

P.S. @arankaren, out of curiousity, what is your community? If it's Debian-related then I'd like to invite you to collaborate or even comaintain the package. Let me know if you're interested! :-) The ITP bug is here: bugs.debian.org #906259.

sten0 avatar Mar 04 '20 01:03 sten0

I need a new tag to package from source in my distro and have control of the published versions

arankaren avatar Mar 08 '20 16:03 arankaren

I have some more bug fixes that I want to finish before pushing a release. However I can't give you any guarantees about stability. I'm not sure how good a target are Emacs packages for projects like Debian. But since you do it people probably find it useful :)

Fuco1 avatar Mar 24 '20 21:03 Fuco1

Hi @Fuco1, any update on that tag?

Most stable Emacs packages are a great fit for Debian :-) Users who tend to want their toolset to not change (except for security fixes) prefer the Debian-packaged version on Debian stable. We also have strict policies like how packages must be coinstallable without causing issues or must declare conflicts when packages are not coinstallable, and we also work hard to make upgrades as painless as possible, and when it's not possible to do this automatically the upgrade system notifies the sysadmin required config changes...so it's not just another software stream, it's a massive systems integration project. We also have extensive (three different networks) of CI, to help with early detection of potential issues. We regularly find examples of how various assumptions create subtle (sometimes not so subtle) bugs, and from an upstream project perspective it's useful fuzzing...the end result being higher quality code for everyone, because we have a culture of working closely with upstreams rather than making Debian-specific fixes.

And yes of course lots of users prefer the excitement of bleeding edge! There's nothing wrong with that, of course, but some people's work depends on a boring and predictable toolset ;-)

At any rate, I've started testing 911cc89 and if necessary would like to collaborate on the stabilisation effort.

sten0 avatar Jun 10 '21 19:06 sten0