On feature workflow

The RPM signing is a manual process. It has obvious security concerns, so the RPM release process requires the Packager supervision. However, as you experimented, the development can proceed without accessing the “official” NethForge repo until the final step.

Going further, sometimes I think Redmine becomes a cumbersome host, and I’d like to base the NethForge process on GitHub, where every contrib could find an home with all required tools:

  • code hosting
  • issue tracker
  • wiki
  • pull requests
  • automated builds (? I’m thinking about travis-ci)

What do you think?

I think that ways should become the same :wink:

1 Like