Update "dist" releases, tag when "stable" about templating HOT 5 OPEN

I can easily tag the latest version of the router. It's solid. Now would be
a good time since I'll probably be adding new features again soon. How
should we label the tags?

On Sun, Aug 3, 2014 at 1:35 PM, Caitlin Potter [email protected]
wrote:

So, it's been about 5 months since the last "dist" release was updated,
and there are almost no tagged releases yet.

@EisenbergEffect https://github.com/EisenbergEffect / @tbosch
https://github.com/tbosch do you think you guys could pick out some
suitably stable commits for tagging so that prototypes can be built against
relatively recent changes to the code? Not necessarily the bleeding edge,
but just stable "enough" to be useful, I guess.

—
Reply to this email directly or view it on GitHub
#39.

Rob Eisenberg,
President - Blue Spire
www.durandaljs.com

from templating.

My vote is to tag the dist builds as v<semver>-dist, and the non-dist builds as v<semver> --- although, I think we should only be publishing the dist builds on npm (which is another issue).

from templating.

Hi,
I would not tag the individual projects templating/router in the current development stage, but use the already existing dist branch in the angular/projects project that also contains all of the dependencies like es5-shim.

Reasons:

• the V2 projects templating and router always use the master version of each other and also of di.js, and rebuild them in their build (so they don't use the dist branches). This is good as it makes changes and refactorings in our current stage of development easier. If we would tag one project (say router) then we would also need to tell people (or our demo :-) ) which tag of the other projects they should use with it. However, as they projects themselves don't contain tags in their dependencies, we would actually need tag every dependency of a project when we tag (and tested) that project.
• to know whether the current code or a project is actually working with the other projects we only have the e2e tests in angular/projects right now. So when tagging one project we already need to build angular/projects with the current master branches of every V2 project.

The only open point for this: the build for angular/projects is not triggered yet by a change of a dependent project. However, we can fix this by adding a BUILDNUMBER file to it that we increment whenever we need a new build.

So to summarize:

• remove the dist branches of templating and router
• add BUILDNUMBER to angular/projects
• tag the dist branch of angular/projects
• use lib folder of dist branch for demos (https://github.com/angular/projects/tree/dist/lib)

from templating.

Hi,
I made the following changes:

• remove the dist branch from templating (there was none for router yet)
• add FORCE_BUILD file to angular/projects
• change the travis build of angular/projects to also tag the dist branch

To create a new version when a dependency changes, just change the FORCE_BUILD file in angular/projects, wait for the travis build and use the created tag.

Here is the first automatically created tag: https://github.com/angular/projects/releases/tag/dist-630ea91

BTW: Using angular/projects we are also able to create plunkers (although with ES5 and not ES6 though). The following is a todo plunker for templating that uses a concrete label of angular/projects dist branch: http://plnkr.co/edit/0Gq3IK8Mj5DtBtmzW8gT?p=preview

from templating.

Just realized that if we tag every commit, we can also just use the commit as tag :-)
So changed the build script back to not adding tags, but left the FORCE_BUILD file in the project to force a build.

from templating.