| Re: [incubation] parallel releases? |
|
Agreed. My only concern is your community understands what you're doing. A quick note on the community forum stating something similar to what you've stated below should solve that. Wayne On 18/07/16 05:40 PM, Konstantin
Komissarchik wrote:
Parallel releases are not a problem. I've done many of these for the Sapphire project.On Jul 18, 2016, at 14:30, Jeen Broekstra <jeen.broekstra@xxxxxxxxx> wrote: Me again. I need a quick word of advice on doing parallel releases: we (that is, technology.rdf4j) are aiming to get our first proper release out the door - we have tentatively planned to submit for review on Wednesday July 27, aiming to conclude review and release on August 3. We are planning to do two parallel releases however: our main release, 2.0, is the main code base and the most recent version of our project. However, we also want to release a version 1.0, which is a backport of our code base to Java 7 (our main project is Java 8). Technically there is no reason for us not to do both releases at once, but I'm slightly worried about making the review process itself too cumbersome. Should I go ahead and just submit both releases for review at the same time (in separate reviews, of course)? Or would it be better/easier to do them sequentially? Thanks, Jeen _______________________________________________ incubation mailing list incubation@xxxxxxxxxxx To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/incubation_______________________________________________ incubation mailing list incubation@xxxxxxxxxxx To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/incubation --
Wayne Beaton @waynebeaton The Eclipse Foundation |