Architecture #7013
closed
Added by Vincent MEMBRÉ over 9 years ago.
Updated over 2 years ago.
Description
We do not make release for ncf (only nightly builds), and this is bad :(
We should make a proper release for ncf (let say 0.9, it needs some stuff for a 1.0 release)
Here is a list of things to do:
- OK: Extract packaging sources into ncf repo from rudder-packages
- Implement proper versionning and clean packaging source
- Add ncf release task into our CI
- Create ncf repo external to Rudder repos
- Include ncf releases into rudder repository
- OK:
Add dependency to ncf 0.9 into proper rudder package v0.9 will be built with Rudder as before
- OK: Add ncf versions in redmine
- prepare changelog for ncf
- Assignee set to Benoît PECCATTE
Benoit do you see missing things in that list ?
- Description updated (diff)
- Related to Bug #7023: Add support for ncf versions in rudder-dev added
- Description updated (diff)
- Target version changed from 0.x to master
- Category set to Packaging
- Assignee deleted (
Benoît PECCATTE)
What is still missing:
- Add ncf release task into our CI
- Include ncf releases into rudder repository and build process
- prepare changelog for ncf
- Subject changed from Make a first final release for ncf! to Make proper ncf releases
- Tracker changed from User story to Architecture
- Target version changed from master to 4.2.2
- Target version changed from 4.2.2 to 4.2.3
- Target version changed from 4.2.3 to 4.2.4
- Target version changed from 4.2.4 to Ideas (not version specific)
- Status changed from New to Rejected
This is now done with ncf having the same release cycle as Rudder
- Project changed from 41 to Rudder
- Category changed from Packaging to Packaging
Also available in: Atom
PDF