Elpa question: helping with maintainance of a package in Elpa

Elpa question: helping with maintainance of a package in Elpa

[Arthur Miller]

I am helping Phillip to maintain his pabbrev package. He has given me write
access to his repository on GH, and I was able to update the package with few
patches It is currently just a "facelift" to skip compiler warnings when
installing.

Do I understand the information in readme file from Elpa repository correctly: I
don't have to do anything special more than just update Phillips repo for the
package on GH, since the Cron job uses that URL to update the package
automatically if the version is changed? Or do I need to do something more to
get the new version into Elpa too?

Since this is just a minor release; not new features, no changes in usability it
does not have to have "announcement" on this list, or do you always announce?

Thanks for the help in advance
Best regards
/arthur

Re: Elpa question: helping with maintainance of a package in Elpa

[Philip Kaludercic]

Arthur Miller <arthur.miller@live.com> writes:

> I am helping Phillip to maintain his pabbrev package. He has given me write
> access to his repository on GH, and I was able to update the package with few
> patches It is currently just a "facelift" to skip compiler warnings when
> installing.
>
> Do I understand the information in readme file from Elpa repository correctly: I
> don't have to do anything special more than just update Phillips repo for the
> package on GH, since the Cron job uses that URL to update the package
> automatically if the version is changed? Or do I need to do something more to
> get the new version into Elpa too?

The cron job will synchronise the mirror with the changes made on the GH
repository.  Just note that to release a package, you'll have to bump
the version tag (any commit changing the line with the version number
should do).

> Since this is just a minor release; not new features, no changes in usability it
> does not have to have "announcement" on this list, or do you always announce?

No, package updates are usually never announced on emacs-devel.

> Thanks for the help in advance
> Best regards
> /arthur

Re: Elpa question: helping with maintainance of a package in Elpa

[chad]

[-- Attachment #1: Type: text/plain, Size: 1020 bytes --]

On Tue, Feb 6, 2024 at 12:02 PM Philip Kaludercic <philipk@posteo.net>
wrote:

> > Do I understand the information in readme file from Elpa repository
> correctly: I
> > don't have to do anything special more than just update Phillips repo
> for the
> > package on GH, since the Cron job uses that URL to update the package
> > automatically if the version is changed? Or do I need to do something
> more to
> > get the new version into Elpa too?
>
> The cron job will synchronise the mirror with the changes made on the GH
> repository.  Just note that to release a package, you'll have to bump
> the version tag (any commit changing the line with the version number
> should do).
>

Note (mostly for future search results): "version tag" in this context
means "the line
in the file that looks something like ";; Version: 0.4", rather than
anything having to
do with git tags. (This sometimes confuses people who are/were familiar
with, for
example, Melpa Stable.)

Hope that helps,
~Chad

[-- Attachment #2: Type: text/html, Size: 1471 bytes --]

Re: Elpa question: helping with maintainance of a package in Elpa

[Philip Kaludercic]

chad <yandros@gmail.com> writes:

> On Tue, Feb 6, 2024 at 12:02 PM Philip Kaludercic <philipk@posteo.net>
> wrote:
>
>> > Do I understand the information in readme file from Elpa repository
>> correctly: I
>> > don't have to do anything special more than just update Phillips repo
>> for the
>> > package on GH, since the Cron job uses that URL to update the package
>> > automatically if the version is changed? Or do I need to do something
>> more to
>> > get the new version into Elpa too?
>>
>> The cron job will synchronise the mirror with the changes made on the GH
>> repository.  Just note that to release a package, you'll have to bump
>> the version tag (any commit changing the line with the version number
>> should do).
>>
>
> Note (mostly for future search results): "version tag" in this context
> means "the line
> in the file that looks something like ";; Version: 0.4", rather than
> anything having to
> do with git tags. (This sometimes confuses people who are/were familiar
> with, for
> example, Melpa Stable.)

Right, my bad, I should have said "Version" header or "Version"
attribute in the package header.

> Hope that helps,
> ~Chad

Re: Elpa question: helping with maintainance of a package in Elpa

[Arthur Miller]

Philip Kaludercic <philipk@posteo.net> writes:

> Arthur Miller <arthur.miller@live.com> writes:
>
>> I am helping Phillip to maintain his pabbrev package. He has given me write
>> access to his repository on GH, and I was able to update the package with few
>> patches It is currently just a "facelift" to skip compiler warnings when
>> installing.
>>
>> Do I understand the information in readme file from Elpa repository correctly: I
>> don't have to do anything special more than just update Phillips repo for the
>> package on GH, since the Cron job uses that URL to update the package
>> automatically if the version is changed? Or do I need to do something more to
>> get the new version into Elpa too?
>
> The cron job will synchronise the mirror with the changes made on the GH
> repository.  Just note that to release a package, you'll have to bump
> the version tag (any commit changing the line with the version number
> should do).
>
>> Since this is just a minor release; not new features, no changes in usability it
>> does not have to have "announcement" on this list, or do you always announce?
>
> No, package updates are usually never announced on emacs-devel.

Thank you very much; this was exactly the info I needed!

I saw it auto-updated last night. Not that I meant to do it; should have
reversed version :-), but it is ok.

Re: Elpa question: helping with maintainance of a package in Elpa

[Arthur Miller]

chad <yandros@gmail.com> writes:

> On Tue, Feb 6, 2024 at 12:02 PM Philip Kaludercic <philipk@posteo.net> wrote:
>
>  > Do I understand the information in readme file from Elpa repository correctly: I
>  > don't have to do anything special more than just update Phillips repo for the
>  > package on GH, since the Cron job uses that URL to update the package
>  > automatically if the version is changed? Or do I need to do something more to
>  > get the new version into Elpa too?
>
>  The cron job will synchronise the mirror with the changes made on the GH
>  repository.  Just note that to release a package, you'll have to bump
>  the version tag (any commit changing the line with the version number
>  should do).
>
> Note (mostly for future search results): "version tag" in this context means "the line
> in the file that looks something like ";; Version: 0.4", rather than anything having to
> do with git tags. (This sometimes confuses people who are/were familiar with, for
> example, Melpa Stable.)
>
> Hope that helps,
> ~Chad
Yeah; I got that, but thanks anyway!