[aerogear-dev] Maintenance branches
Daniel Bevenius
daniel.bevenius at gmail.com
Fri Mar 22 05:12:42 EDT 2013
Hi all,
I'd like to discuss how to handle maintenance branches. Sorry if this has
already been discussed, I think Kris posted something about this but I was
not able to find it.
For example, now that we are about to release 1.0.0 we will tag that
release. After that should we create a 1.0.1 branch for patches/bugfixes
and then continue with new features in master?
Since we are in a waiting state at the moment, which could happen again,
should we perhaps create a branch named 1.0.0, which we can use until the
release and then tag it and remove that branch. After that any issues would
be fixed in the 1.0.1 branch.
Does this sound correct?
Thanks,
/Dan
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20130322/0a99ecff/attachment.html
More information about the aerogear-dev
mailing list