I would like to go ahead and push 389-ds-base-1.2.6 and 389-admin-1.1.11 to Stable. They are currently in Testing.
389-ds-base-1.2.6 is essentially the same as 389-ds-base-1.2.6.rc7. 389-admin-1.1.11 is essentially the same as 389-admin-1.1.11.rc2. Both of the rc releases have been in testing for a while now and have passed the push to Stable criteria. Since the final releases are essentially the same as the rc releases, I would like to go ahead and push the final releases from Testing to Stable.
Well, there is some change right? they have different versions in the package name/spec file and were rebuilt later against a possibly changed build root?
Whats the harm in a short stint in updates-testing? Perhaps you can get folks interested in them going stable faster in testing and adding karma?
Replying to [comment:1 kevin]:
Well, there is some change right?
Right.
they have different versions in the package name/spec file and were rebuilt later against a possibly changed build root?
Yes and yes. The upstream source code between tags 1.2.6.rc7 and 1.2.6 final is just the version number change in the VERSION.sh file.
Ok.
Shall I go ahead and close this now? Or would you like to ask fesco for an exception in the next meeting (or here in the ticket).
I'll go ahead and resolve the issue.
Login to comment on this ticket.