| Re: [elk-dev] ELK Version Handling |
Hi, that's a good point and is something I wanted to bring up before the next release. Using the API tooling, bundle-specific version handling actually is not all that hard and happens during development (API tooling complains if the version is not properly increased after making a significant change to a plug-in). However, I like how increasing all versions simultaneously makes it easier to understand which release a plug-in was part of. To sum up: +1. Should we increase version numbers after a release or before a release? Cheers, Christoph Daniel On 19/10/16 10:40, Miro Spönemann wrote: > Hi, > > I noticed that the nightly update site offers features with version > 0.1.0, but it should now be at 0.2.0, right? > > I propose to increase the version numbers of all plugins and features > consistently after each release, independently of whether there have > been any changes in a bundle or not. That will make the release > engineering a lot easier compared to bundle-specific version handling. > > Regards > -- > Dr. Miro Spönemann > Software engineer and consultant > > TypeFox GmbH > Am Germaniahafen 1, 24143 Kiel > > http://typefox.io > Tel.: +49 151 42679459 > > Sitz: Kiel, Registergericht: Amtsgericht Kiel, HRB 17385 > Geschäftsführer: Sven Efftinge, Dr. Jan Köhnlein, Moritz Eysholdt > > > > _______________________________________________ > elk-dev mailing list > elk-dev@xxxxxxxxxxx > To change your delivery options, retrieve your password, or unsubscribe from this list, visit > https://dev.eclipse.org/mailman/listinfo/elk-dev >
Attachment:
signature.asc
Description: OpenPGP digital signature