This is the mail archive of the mailing list for the GDB 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]

Re: [commit/branch] Version set to 6.7.90

> Right.  But if you don't make that snapshot, the first prerelease
> should be 6.7.91; version numbers going backwards is bad mojo :-)

Roger that - the first pre-release version number will be .90 if
it is made immediately after cutting the branch, or .91 if made later.

I'm still unsure whether making a pre-release right after cutting
the branch brings value or not. On the one hand, it's easier to
test, and in many ways more meaningful, a pre-release than something
downloaded off a branch. On the other hand, sometimes we know the
branch is missing some changes that will come later. Maybe this
needs to be a case-by-case judgement call. In the case of the 6.8
release cycle, we could have made a first pre-release immediately.

All in all, I'm thinking that we should make it a policy of creating
the pre-release immediately. The only case where this would provide
no benefit is when we know a major piece is missing, but in this case
the branch shouldn't have been cut in the first place, no?


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]