Page Comparison

Former user (Deleted)

...

             a.  Docker hub:  nightly vs. latest vs. 1.3.0-20170228UTC-c69028e

              b.  Atlas:  v2.1.101, v0.15, v0.02.08  Update these appear to be old and should be cleaned up?  AI Former user (Deleted) to send out email on the ones she is going to delete unless someone is has an issue.

              c.  Bintray:  1.3.0-20170228UTC-c69028e

Inconsistency in naming of builds -  AI Former user (Deleted) to verify that latest is not being pushed to Docker Hub, let what is being built on docker hub be the latest.   AI All CC to respond to Peter Pan email around the plan.

Nightly tags will not have any indication of release number they will only include the date.   Former user (Deleted) can you make the changes to the build tools to no longer include release numbering AI Former user (Deleted) to open up RAC issue

  2. Replace bootstrap ubuntu with rancherOS in discovery and Micro-docker Former user (Deleted)

    See PR from Former user (Deleted): https://github.com/RackHD/on-taskgraph/pull/221

We need a plan to switch from current Microkernel to dockerized microkernel as this is a very fundamental change and will bring impact to community and build&release.

AI Former user (Deleted) to link rancherOS documentation to RackHD documentation.   AI Former user (Deleted) to send out PPT on this subject to CC.

3. Automatically run rebase for PR gate Former user (Deleted)

Suggest Jenkins always automatically run "git rebase" for the target repo before PR gate testing, As I have seen a lot out-of-date PRs fail with some odd jenkins test errors (especially those PRs that are opened for a long time). 

AI Former user (Deleted) to sketch out proposal/sequence on how this will work and send to CC for review.

4.  Should the disabling of 1.1 API and the new release of 2.0 be highlighted on the web portal https://rackhd.github.io/  yes more info is better.   Add the disabling message under News section on portal.

AI Former user (Deleted) going to communicate via google docs.

5. All set to release 2.0.0 at end of this sprint?

...