keeping stale dependencies up-to-date

[Feroz Panwaskar]

Hi,

We are using jam for our dependency management within the company.  We are starting to see that a lot of the dependencies we have are stale and once they've been published by someone it has to be maintained by them.  We could publish these to our private repo, but that would not be sustainable.

I was wondering how people have got around this?

What may help is the ability to publish a reference to a package in git.  Then anyone can do the initial publish and the maintainers just need to tag their versions.

Any suggestions/thoughts are much appreciated.

[Caolan McMahon]

Hi Feroz,

This is definitely something we could use a solution to. There was a
plan a while ago to create a github hook to automatically publish to
Jam when a new version is tagged in the repository. Something like
that could help. We might also need to discuss the process for
transferring ownership of existing packages, where the original
uploader is no longer using Jam to keep the package up to date.

Suggestions welcome, especially if you have some time available to
implement them ;)

Caolan

> --
> You received this message because you are subscribed to the Google Groups
> "jamjs" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jamjs+un...@googlegroups.com.
> To post to this group, send an email to ja...@googlegroups.com.
> To view this discussion on the web, visit
> https://groups.google.com/d/msgid/jamjs/a8436b3c-4e19-4900-bb7e-ec8444990ca5%40googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>