search

TEIC / oxygen-tei

Automatically exported from code.google.com/p/oxygen-tei
15 stars 6 forks source link

add template and script for creating updateSite.oxygen #31

Closed peterstadler closed 1 week ago

peterstadler commented 5 years ago

from GitHub releases. For every release one xt:extension entry will be created.

I'm unsure about both the current directory structure of the repo and whether to replace the current mechanism of creating the updateSite.oxygen entirely with this approach. Feedback and updates to the PR welcome!

martindholmes commented 5 years ago

Is the plan for a release tech to run this manually after every release?

peterstadler commented 5 years ago

I don't know. It could as well be a Jenkins job that gets triggered after every release.

The primary issue I was trying to address is to streamline the creation of the updateSite.oxygen file because at present it highly depends on the machine you're creating it with (how many old versions there are, paths to artifacts).

martindholmes commented 5 years ago

In that case, should we remove the generation of the update file from the stable plugin build process as well? We presumably do need the bleeding-edge plugin to keep working in the old way, but the stable plugin build should presumably push its products to github as a release, then run your process. But I must admit this is pretty confusing at this stage. I think we should really lay out a detailed description of what will run automatically on Jenkins, what will be published on GitHub (and when and how and by whom), who will run your process to update the file for the stable plugin, and where it will be hosted.

ebeshero commented 1 week ago

I am pretty sure this PR is outdated by now! Closing.