This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
Jason, any thoughts on how to translate "ready to make a .0 release" into "made a .0 release," in terms of a firm schedule, with dates? I'm assuming that the < 100 bugzilla count is an adequate milestone for the release branch to be cut.
Or do you think < 100 implies branch implies 4.3.0 release, as originally described by Richard is the way to go?
I'm willing to try this. It's just that I would like some advance notice before a release, just to check over things.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |