Re: [AUCTeX] Preparing new AUCTeX version and comments about more frequent releases

2017-08-11 Thread Davide G. M. Salvetti
> NP == Norbert Preining [2017-7-22] NP> Combining what you two said, it seems that the easiest way forward for NP> you (upstream) and not too disturbing for downstream to stop doing NP> whatever "tarball releases" you are doing, and we consider the NP> elpa releases as "the releases" which

Re: [AUCTeX] Preparing new AUCTeX version and comments about more frequent releases

2017-07-21 Thread Norbert Preining
Hi both of you, > > in the long run I could use both, but ATM the most straightforward way > > for me would be to package from a git tag, especially if I could use > > git archive to get a orig.tar.gz. In this case, both the current stable release tags, as well as the hopefully to be done elpa

Re: [AUCTeX] Preparing new AUCTeX version and comments about more frequent releases

2017-07-21 Thread Mosè Giordano
Hi Davide, 2017-07-22 2:55 GMT+02:00 Davide G. M. Salvetti : >> MG == Mosè Giordano [2017-7-21] > > [...] > > MG> We have the Debian maintainer reading us :-) Davide, do you think > MG> you'd be able in the future to prepare the Debian package from a git > MG> tag or an

Re: [AUCTeX] Preparing new AUCTeX version and comments about more frequent releases

2017-07-21 Thread Davide G. M. Salvetti
> MG == Mosè Giordano [2017-7-21] [...] MG> We have the Debian maintainer reading us :-) Davide, do you think MG> you'd be able in the future to prepare the Debian package from a git MG> tag or an ELPA package? Hi everybody, in the long run I could use both, but ATM the most

Re: [AUCTeX] Preparing new AUCTeX version and comments about more frequent releases

2017-07-21 Thread Ikumi Keita
> Mosè Giordano writes: > Hi Keita, > Looks good, and they're also only stylistic changes, so should be safe > to include them right now. Go ahead and install the patch ;-) Done. This is my first time to use `prog2' in a meaningful way :-) Bye, Ikumi Keita

Re: [AUCTeX] Preparing new AUCTeX version and comments about more frequent releases

2017-07-21 Thread Mosè Giordano
Hi Norbert, first of all, thanks for raising the issue of the important bugfix missing in a stable release. Lately the development of AUCTeX slowed down and rolling a new release went outside my radar. 2017-07-21 3:31 GMT+02:00 Norbert Preining : > Hi Mosè > >> In addition,

Re: [AUCTeX] Preparing new AUCTeX version and comments about more frequent releases

2017-07-21 Thread Mosè Giordano
Hi Keita, 2017-07-21 9:13 GMT+02:00 Ikumi Keita : > Hi all, > >> Mosè Giordano writes: >> Dear all, >> the latest stable release of AUCTeX doesn't include the fix for the >> parsing of TeX Live 2017 logs (see >>

Re: [AUCTeX] Preparing new AUCTeX version and comments about more frequent releases

2017-07-21 Thread Ikumi Keita
Hi all, > Mosè Giordano writes: > Dear all, > the latest stable release of AUCTeX doesn't include the fix for the > parsing of TeX Live 2017 logs (see > https://lists.gnu.org/archive/html/auctex/2017-04/msg7.html), so > now that TeX Live 2017 has been release it's a good

Re: [AUCTeX] Preparing new AUCTeX version and comments about more frequent releases

2017-07-20 Thread Norbert Preining
Hi Mosè > AUCTeX 11.91. Is there any other quick change that you would like to > see into this version? Not from my side. > In addition, Norbert Preining expressed[1] the wish to see more > synchronization between ELPA releases and stable releases, because Not necessarily! I leave this to the

Re: [AUCTeX] Preparing new AUCTeX version and comments about more frequent releases

2017-07-20 Thread Ken Brown
On 7/20/2017 7:13 AM, Tamas Papp wrote: On Thu, Jul 20 2017, Mosè Giordano wrote: I'd like to cooperate as much as possible with downstream distributors, but I'm not sure about what's the best way to do it: * start tagging and releasing bug-fix versions also in the main repository (not only

Re: [AUCTeX] Preparing new AUCTeX version and comments about more frequent releases

2017-07-20 Thread Tamas Papp
On Thu, Jul 20 2017, Mosè Giordano wrote: > I'd like to cooperate as much as possible with downstream > distributors, but I'm not sure about what's the best way to do it: > > * start tagging and releasing bug-fix versions also in the main > repository (not only in ELPA)? > * continue to not

[AUCTeX] Preparing new AUCTeX version and comments about more frequent releases

2017-07-20 Thread Mosè Giordano
Dear all, the latest stable release of AUCTeX doesn't include the fix for the parsing of TeX Live 2017 logs (see https://lists.gnu.org/archive/html/auctex/2017-04/msg7.html), so now that TeX Live 2017 has been release it's a good idea to release AUCTeX 11.91. Is there any other quick change