Ok, the apache tag is now blacklisted:
Along with this comes the requirement that a version-specific tag exists for each Apache version being asked about. In practice, this isn't likely to be too different from what was already occurring (since the raw apache tag was being silently renamed to apache-2.2), but be aware that some amount of confusion or mistagging may result - so be prepared to retag (and create new tags) as needed.
Ok, the apache tag is now blacklisted:
Along with this comes the requirement that a version-specific tag exists for each Apache version being asked about. In practice, this isn't likely to be too different from what was already occurring (since the raw apache tag was being silently renamed to apache-2.2), but be aware that some amount of confusion or mistagging may result - so be prepared to retag (and create new tags) as needed.
Ok, the apache tag is now blacklisted:
Along with this comes the requirement that a version-specific tag exists for each Apache version being asked about. In practice, this isn't likely to be too different from what was already occurring (since the raw apache tag was being silently renamed to apache-2.2), but be aware that some amount of confusion or mistagging may result - so be prepared to retag (and create new tags) as needed.
Ok, the apache tag is now blacklisted:
Along with this comes the requirement that a version-specific tag exists for each Apache version being asked about. In practice, this isn't likely to be too different from what was already occurring (since the raw apache tag was being silently renamed to apache-2.2), but be aware that some amount of confusion or mistagging may result - so be prepared to retag (and create new tags) as needed.
