I forgot to mention that this tag should be based on rawhide.

how long should this all take to complete?

side tags cause issues for secondary arches, and we try to avoid them. a change of 10-20 packages should just be done in rawhide. we also have some timing issues right now with the mass rebuild scheduled to start any day.

my inclination right now is to not make a side tag.

Because of the nature of changes it's unclear how long this will take. This feature is not scheduled for Fedora 20 so I guess we could wait until branching if necessary.

These changes are non-trivial and require tagging and untagging multiple builds (build package A, untag, build B, untag, build C, tag A,B,C at the same time). Sometimes older build has to be tagged.

I would insist on a separate tag because if we do this in rawhide then:

• Java stack will be effectively broken for the time of that operation blocking other (unrelated) teams from doing their job
• If we don't complete the whole operation within 24h then broken packages (or otherwise containing prebuilt upstream binary code) will get into composes and will be installable by users. Upgrade path will be broken as older packages may get into compose.
• If some packages are built duting the whole operation by unaware users they may be broken. We would need to identify which packages were built during the operation, verify their correctness and possibly untag, bump and rebuild them
• Not having a separate tag will force us to rush and this may have negative impact on overal quality of Java packages

People already complain that rawhide is often broken. Let's not break it even more. That's why separate tags are for.

As I already said, I can wait some time until branching, it's not F20 feature.

i will look at doing a tag after mass rebuild. separate tags cause problems of thier own, the cost is much higher than most people think.

I have already built the most difficult parts in rawhide. Separate tag is not needed any longer. Closing.