> It may also be interesting to think about having a head branch for development > and a release branch for releases since this'd allow people to follow releases > via git pull without having to worry about getting the latest unstable > developments.
Well perhaps - but I'm trying to avoid git version complexity and branches and the like. The few intrepid folks who follow the latest often want the latest, even that last bug or feature that we just fixed, and they are sometimes helpful in finding more bugs, so we can fix them *before* any release or version cuts over. Recall when a user found a seg fault just last month and I fixed it, and didn't that happen a month before too? These are our beta testers, and I think they really do want the latest, and we want them to have the latest. It's a win win. Besides, our "unstable" snapshots aren't really that unstable. We are reasonably careful in what we push. I think I'll defer to Chris on whether we should stamp version 3.5.3 now, or put some of his imap changes in first. Karl Dahlke _______________________________________________ Edbrowse-dev mailing list [email protected] http://lists.the-brannons.com/mailman/listinfo/edbrowse-dev
