On Tue, 2016-02-02 at 18:11 +0100, Emmanuel Bourg wrote: > 2. Reuse groovy to package the next version of Groovy 2.x and then > remove groovy2 (we keep the 2.x artifact to avoid updating all the > reverse dependencies) > > 3. Turn groovy into a dummy package depending on groovy2. The groovy > package would become the equivalent of default-jdk, always pointing > to > the latest version available. > I like having the ability to install a package and have the latest version available rather than remember that I'm using a specific API version. The versioned api packages do have their uses though. I only count a few packages that depend on groovy2 so it shouldn't take too long for them to get updated. Until we have a need for multiple groovy versions again, it's just extra work to maintain and build a dummy package. Why not leave it until its really needed? I'd vote for (2). Andrew
Attachment:
signature.asc
Description: This is a digitally signed message part