Migration to the new forge #13094

Merged
jnsamyak merged 1 commit from main into main 2025-11-18 15:19:21 +00:00
6 changed files with 327 additions and 0 deletions

17
.github/ISSUE_TEMPLATE.md vendored Normal file
View file

@ -0,0 +1,17 @@
⚠️ **ISSUE TRACKER HAS MOVED**
This issue tracker is **closed**.
Please file your issue at the new location:
**https://forge.fedoraproject.org/releng/tickets**
---
All existing issues have been migrated to Fedora Forge.
Search for existing issues before filing a new one:
https://forge.fedoraproject.org/releng/tickets
Thank you!

28
.github/PULL_REQUEST_TEMPLATE.md vendored Normal file
View file

@ -0,0 +1,28 @@
⚠️ **THIS REPOSITORY HAS MOVED**
This repository no longer accepts pull requests.
Please submit your contribution to the new repository:
**https://forge.fedoraproject.org/releng/releng**
---
## How to Submit Your Changes
1. **Clone the new repository:**
```bash
git clone https://forge.fedoraproject.org/releng/tooling.git
```
2. **Make your changes** and commit them
3. **Push to your fork** on Fedora Forge
4. **Open a Pull Request** at:
https://forge.fedoraproject.org/releng/releng/pulls
---
Thank you for contributing to Fedora Release Engineering!

33
CONTRIBUTING.md Normal file
View file

@ -0,0 +1,33 @@
# ⚠️ THIS REPOSITORY HAS MOVED
**This repository is no longer accepting contributions here.**
## 🔗 New Contribution Location
Please submit all contributions to the new repository on Fedora Forge:
**https://forge.fedoraproject.org/releng/tooling**
---
## 📝 How to Contribute at the New Location
1. **Visit:** https://forge.fedoraproject.org/releng/
2. **Read the Contributing Guide:** Available in the new repository
3. **Open Pull Requests:** Submit to the Fedora Forge repository
4. **File Issues:** Use https://forge.fedoraproject.org/releng/tickets
---
## 🔄 Update Your Git Remote
If you have a local clone of this repository, update it to point to the new location:
```bash
git remote set-url origin https://forge.fedoraproject.org/releng/tooling.git
```
---
**All active development is now at:** https://forge.fedoraproject.org/releng/tooling

151
MIGRATION.md Normal file
View file

@ -0,0 +1,151 @@
# Repository Migration to Fedora Forge
## Overview
The Fedora Release Engineering repository has been migrated from its previous location to the new Fedora Forge infrastructure.
## New Locations
| Component | Previous Location | New Location |
|-----------|------------------|--------------|
| **Repository** | https://pagure.io/releng | https://forge.fedoraproject.org/releng/tooling |
| **Issue Tracker** | https://pagure.io/releng/issues | https://forge.fedoraproject.org/releng/tickets |
| **Pull Requests** | https://pagure.io/releng/pull-requests | https://forge.fedoraproject.org/releng/releng/pulls |
## Migration Details
### What Was Migrated
✅ **Source Code**
- Complete Git history preserved
- All branches migrated
- Tags and releases maintained
✅ **Issues**
- All open issues migrated to new tracker
- Issue numbers and metadata preserved
- Comments and attachments transferred
✅ **Documentation**
- README files updated
- Contributing guidelines migrated
- Conventions documentation preserved
### Migration Timeline
- **Announcement Date:** [Date]
- **Migration Date:** [Date]
- **Old Repository Status:** Read-only archive
- **Issue Tracker Status:** Closed
## For Repository Users
### Update Your Git Remote
If you have a local clone of this repository:
```bash
# Check your current remote
git remote -v
# Update to new location
git remote set-url origin https://forge.fedoraproject.org/releng/releng.git
# Verify the change
git remote -v
```
### Fresh Clone
For new clones, use the new repository location:
```bash
git clone https://forge.fedoraproject.org/releng/releng.git
cd releng
```
## For Contributors
### Submitting Changes
1. **Fork** the repository at https://forge.fedoraproject.org/releng/releng
2. **Clone** your fork locally
3. **Create** a feature branch for your changes
4. **Push** your changes to your fork
5. **Open** a Pull Request at the new repository
### Filing Issues
1. **Search** existing issues: https://forge.fedoraproject.org/releng/tickets
2. **File new issues** at the new tracker
3. **Reference** related issues using the new issue numbers
## For Automation & CI/CD
### Update References
If your automation or CI/CD pipelines reference this repository:
**URLs to Update:**
- Repository URLs → `https://forge.fedoraproject.org/releng/tooling`
- Issue tracker URLs → `https://forge.fedoraproject.org/releng/tickets`
- Documentation URLs → `https://docs.fedoraproject.org/en-US/infra/release_guide/`
**API Endpoints:**
- Check Fedora Forge API documentation for new endpoints
- Update authentication tokens if needed
## Benefits of Fedora Forge
The migration to Fedora Forge provides:
🚀 **Modern Infrastructure**
- Improved performance and reliability
- Better integration with Fedora ecosystem
- Enhanced security features
🤝 **Better Collaboration**
- Unified platform for all Fedora projects
- Improved code review tools
- Better issue tracking and project management
🔧 **Enhanced Workflows**
- Native CI/CD integration
- Better Git workflow support
- Improved notification system
## Support
### Getting Help
If you encounter issues with the migration:
1. **Check Documentation:** https://docs.fedoraproject.org/en-US/infra/release_guide/
2. **Ask on IRC/Matrix:** #fedora-releng on Libera.Chat
3. **Mailing List:** devel@lists.fedoraproject.org
4. **File an Issue:** https://forge.fedoraproject.org/releng/tickets
### Common Issues
**Q: My local clone stopped working**
A: Update your remote URL as shown above
**Q: Where did my open issue go?**
A: Check https://forge.fedoraproject.org/releng/tickets - all issues were migrated
**Q: Can I still access the old repository?**
A: Yes, it remains available as a read-only archive for reference
**Q: What about pull requests that were open?**
A: Contact the release engineering team if you had open PRs that need attention
## Historical Reference
The original repository information and licensing details are preserved in `README.old`.
---
**For the latest information, always refer to:** https://forge.fedoraproject.org/releng
**Last Updated:** [Date]

98
README.md Normal file
View file

@ -0,0 +1,98 @@
# ⚠️ THIS REPOSITORY HAS MOVED
## 🔗 New Location
This repository has been migrated to Fedora Forge and is **no longer maintained here**.
**New Repository:** https://forge.fedoraproject.org/releng/releng
**Issue Tracker:** https://forge.fedoraproject.org/releng/tickets
---
## 📍 What This Means
### For Contributors
- **All new contributions** should be submitted to the [new repository on Fedora Forge](https://forge.fedoraproject.org/releng/releng)
- **Pull requests** opened here will not be reviewed or merged
- Please redirect any work to the new location
### For Issue Reporters
- **Issue tracker is closed** here
- All existing open issues have been migrated to [Fedora Forge Tickets](https://forge.fedoraproject.org/releng/tickets)
- **New issues** must be filed at the new tracker
- Search for existing issues at the new location before filing
### For Users
- **Scripts and tools** are maintained at the new location
- **Documentation** has been updated at the new repository
- Bookmark the new repository for future reference
---
## 🚀 Quick Links
| Resource | New Location |
|----------|-------------|
| **Repository** | https://forge.fedoraproject.org/releng/tooling |
| **Issue Tracker** | https://forge.fedoraproject.org/releng/tickets |
| **Documentation** | https://docs.fedoraproject.org/en-US/infra/release_guide/ |
---
## 📋 Migration Information
### Timeline
- **Migration Date:** [Date when migration completed]
- **Repository Status:** Read-only / Archived
- **Issue Tracker Status:** Closed
### What Was Migrated
- ✅ All source code and scripts
- ✅ Git history preserved
- ✅ Open issues and discussions
- ✅ Documentation and conventions
- ✅ Release engineering tools and workflows
### What To Do Next
1. **Update your remotes:**
```bash
git remote set-url origin https://forge.fedoraproject.org/releng/releng.git
```
2. **Clone from new location:**
```bash
git clone https://forge.fedoraproject.org/releng/releng.git
```
3. **Update bookmarks** to point to Fedora Forge
4. **File new issues** at the new tracker
---
## 📞 Contact
For questions about the migration or the new infrastructure:
- **Mailing List:** [devel@lists.fedoraproject.org](mailto:devel@lists.fedoraproject.org)
- **IRC/Matrix:** https://app.element.io/#/room/#releng:fedoraproject.org
- **Issue Tracker:** https://forge.fedoraproject.org/releng/tickets
---
## 🏛️ About Fedora Forge
Fedora Forge is the new unified infrastructure for Fedora project development, providing:
- Modern Git-based workflows
- Integrated issue tracking
- Better collaboration tools
- Improved CI/CD integration
Learn more: https://forge.fedoraproject.org/
---
**This repository will remain available in read-only mode for historical reference.**
**All active development has moved to Fedora Forge: https://forge.fedoraproject.org/releng/releng**

View file