branchy development

Say we release versions 1.0, 1.1, 1.2. Then we make significant changes, move up a major release number, and release versions 2.0, 2.1

Then we see there's a bug in 1.2. Typical development problem. From the perspective of source control, we'd clone/update back to 1.2, fix the bug, tag version 1.2.1, and merge the fix into what will become 2.2 (currently under development). At this point, however, we may only want to deliver the 1.2.1 fix to our 1.2 customers, rather than giving them the whole upgrade to 2.2.

This means separate wyBuild projects per major release?

This means separate wyBuild projects per major release?

Unfotunately, yes. We're working to fix this so all separate branches (or channels) can be added from the same project. But as it is now each major release should get its own project.

I guess there'd be no other way to prevent 1.1 clients to update to 2.x instead of 1.2 anyways right?

Thanks for the quick reply.

I guess there'd be no other way to prevent 1.1 clients to update to 2.x instead of 1.2 anyways right?

That's correct. We're working to improve this, but for now you'll have to have a separate project for your major versions.

Reply
Discard post