Differences between revisions 4 and 6 (spanning 2 versions)
⇤ ← Revision 4 as of 2015-12-26 09:53:45 →
Size: 609
Editor: Praveen A
Comment: should be under Teams
← Revision 6 as of 2015-12-28 16:29:34 → ⇥
Size: 1272
Editor: Praveen A
Comment:
Deletions are marked like this. Additions are marked like this.
Line 3: Line 3:
 1. Find if unpackaged dependencies are added
 1. Package any new gems and add them to a staging repo untill it clears new
 1. Check for gem updates and add updates to a staging repo
 1. Import the new upstream to a new branch and add packages to staging repo		  1. Find if unpackaged dependencies are added in the new version (compare Gemfile of both versions) or use tracker at http://debian.fosscommunity.in/
 1. Package any new gems and add them to a staging repo until they clear NEW queue
 1. Check for gem updates and add updates to a staging repo(use tracker at http://debian.fosscommunity.in/ for mismatch)
 1. Import the new upstream to a new branch (if the current version is still in experimental) and add package to staging repo.
 1. Refresh patches to match versions in the archive. Relax stable libraries (>= 1.x) and be careful with development libraries (0.x). Update debian/control with stricter dependency for dependency update (it will help in backporting).
  1. Step 1: Refresh patches that is needed for build (Gemfile changes)
  1. Step 2: Refresh patches for bundle install --local (install the newly built package to find out)
Line 8: Line 11:
 1. Move to unstable with dependencies only in experimental (always use experimental, never directly upload to unstable)  1. Move to unstable with dependencies only in experimental (always use experimental, never directly upload to unstable) after testing the new version

  1. Find if unpackaged dependencies are added in the new version (compare Gemfile of both versions) or use tracker at http://debian.fosscommunity.in/

  2. Package any new gems and add them to a staging repo until they clear NEW queue

  3. Check for gem updates and add updates to a staging repo(use tracker at http://debian.fosscommunity.in/ for mismatch)

  4. Import the new upstream to a new branch (if the current version is still in experimental) and add package to staging repo.

  5. Refresh patches to match versions in the archive. Relax stable libraries (>= 1.x) and be careful with development libraries (0.x). Update debian/control with stricter dependency for dependency update (it will help in backporting).

    1. Step 1: Refresh patches that is needed for build (Gemfile changes)
    2. Step 2: Refresh patches for bundle install --local (install the newly built package to find out)
  6. Once new dependencies clear NEW queue, upload new package with dependencies to experimental
  7. Move to unstable with dependencies only in experimental (always use experimental, never directly upload to unstable) after testing the new version