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
Christo Butcher (@t4ngo) has kindly allowed us the use of the original 'dragonfly' PyPI channel for distribution and has archived the original t4ngo/dragonfly repository. I'd like to start releasing new versions via the original channel instead of via dragonfly2.
@calmofthestorm Christo has given you and myself owner-level access to the dragonfly channel. You also have this access to the dragonfly2 channel. This way, we can add new maintainers / owners in the future as necessary.
We can stick with the same version numbers used for dragonfly2. I'm uncertain whether releases for dragonfly2 should continue after this. Maybe we could stop them at version 1.0.0?
TODO
Reupload all previous release versions to the dragonfly PyPI channel.
Make appropriate changes to Dragonfly's source code + documentation
Distribute the next version there.
After the next release, make announcements about this change:
CC @LexiconCode
Christo Butcher (@t4ngo) has kindly allowed us the use of the original 'dragonfly' PyPI channel for distribution and has archived the original t4ngo/dragonfly repository. I'd like to start releasing new versions via the original channel instead of via dragonfly2.
@calmofthestorm Christo has given you and myself owner-level access to the dragonfly channel. You also have this access to the dragonfly2 channel. This way, we can add new maintainers / owners in the future as necessary.
We can stick with the same version numbers used for dragonfly2. I'm uncertain whether releases for dragonfly2 should continue after this. Maybe we could stop them at version 1.0.0?
TODO
The text was updated successfully, but these errors were encountered: