You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In 2d783f7 in March, you have changed Iev to IEV in module names, without informing me, and without doing a gem release.
As a result, when I did an update to the gem and released it last week, this broke standoc.
I have spent the past half hour trying to change IEV back to Iev, and I cannot, the spec files keep complaining that they are not finding the classes (uninitialized constant Iev::DbWriter)
I do not have the time to fix gems I do not maintain. I would prefer to take standoc back to invoking IEV::Db instead of Iev::Db, as the practical thing to do in such a circumstance, but @ronaldtse has vetoed that.
Therefore you need to change all the instances of IEV in this gem back to Iev, release the gem, and take care of any downstream implications in the code you maintain. This is now blocking Metanorma release.
cc @ReesePlews, since you wanted to know the release schedule.
The text was updated successfully, but these errors were encountered:
In 2d783f7 in March, you have changed
Iev
toIEV
in module names, without informing me, and without doing a gem release.As a result, when I did an update to the gem and released it last week, this broke standoc.
I have spent the past half hour trying to change IEV back to Iev, and I cannot, the spec files keep complaining that they are not finding the classes (
uninitialized constant Iev::DbWriter
)I do not have the time to fix gems I do not maintain. I would prefer to take standoc back to invoking IEV::Db instead of Iev::Db, as the practical thing to do in such a circumstance, but @ronaldtse has vetoed that.
Therefore you need to change all the instances of IEV in this gem back to Iev, release the gem, and take care of any downstream implications in the code you maintain. This is now blocking Metanorma release.
cc @ReesePlews, since you wanted to know the release schedule.
The text was updated successfully, but these errors were encountered: