In the next week, we'll be making some changes to the way the parent pom and JIRA work for you. -- a) jgit timestamps Instead of a BUILD_ALIAS like Alpha1 or Beta1, which forces users to download a whole JBT or devstudio install each time we release a new milestone, plugins and features will soon use the timestamp of their last change in github. Note that two plugins will continue to have a BUILD_ALIAS applied: foundation.core & devstudio.central, which define the version of JBoss Tools / devstudio used by ide-config.properties to assign the correct URLs for Central and quickstarts. But as you'll see below, we will start using Sprint numbers here instead of quality labels like Alpha or Beta. This change will roll out next week once we're done with the Jun 27 release. ACTION REQUIRED: Now, when you're building locally, you will need to *check in your changes* (to your local github clone, not to origin!) in order to ensure that your local changes are seen as "newer" than the stuff available on download.jboss.org, or in your ~/.m2/repo. Ref: https://issues.jboss.org/browse/JBIDE-13671 -- b) sprint-based fixversions Because we no longer need to do the waterfall method of Alpha -> Beta -> CR -> Final, we will now start defining fixversions in JIRA using the sprint numbers, S116, S117, S118, etc. I've for the moment left the .Final and .GA fixversions in place for two reasons: * because we need .GA in order to allocate issues to Target Releases in the JBDS JIRA * because this lets you differentiate between things completed for the Final/GA release vs. things simply completed in a sprint. This change has already been done, in order to see the impact on downstream processes like jiralint. I've also renamed the sprints so that they include their start/end dates, rather than just "June 2016" because I figured that was more meaningful. Dates format is yyyy/mm/dd - mm/dd. You can see this on a board such as https://issues.jboss.org/secure/RapidBoard.jspa?rapidView=3410&view=p... ACTION REQUIRED: Nothing. Ref: https://issues.jboss.org/browse/JBIDE-22619 -- If you have any concerns about these changes, please post them on the associated JIRAs: -- Nick Boldt :: JBoss by Red Hat Productization Lead :: JBoss Tools & Dev Studio http://nick.divbyzero.com _______________________________________________ jbosstools-dev mailing list jbosstools-dev(a)lists.jboss.org <javascript:;> https://lists.jboss.org/mailman/listinfo/jbosstools-dev

Nick, I also think that the new long names are too "noise". Too many numbers. It's hard to read. Month is enough IMO even if we have two sprints for the same month. I understand that we all can have different preferences. And what is hard to read for us may provide additional useful information for you or someone else. This is why it's very important to discuss such changes first and got to agreement *before* changing it. Can you just revert it for now then we can discuss it later? On 06/22/2016 01:43 PM, Nick Boldt wrote: > I disagree. > > Using the "main month in the sprint to give an idea" is a far less > useful piece of information than the actual start/end dates, which > give you the ACTUAL dates at a glance. > > When sprints cross months, as most do, which month should be > selected? > The start month? the end month? or the one that makes up the largest > percentage in the sprint? > > If you feel it's too much information, just glance away. >

After further discussion with Max, Nick and Jeff we agreed to use M1, M2, M3, etc suffixes instead of S114, S115 or Alpha1, Beta1 etc in fix versions in JIRA, pom.xml's, etc. Sorry for all these changes and confusion they may cause but we are still trying to find the best way to version our stuff. So, our fix versions will look something like 4.4.1.M1, 4.4.1.M2, 4.4.1.GA, 4.5.0.M1, 4.5.0.M2, 4.5.0.GA etc. If there is no any objections then I would like to ask Nick to go ahead and fix all the relevant places where we use that suffixes for our versions. On 06/22/2016 10:54 AM, Nick Boldt wrote: b) sprint-based fixversions Because we no longer need to do the waterfall method of Alpha -> Beta -> CR -> Final, we will now start defining fixversions in JIRA using the sprint numbers, S116, S117, S118, etc. I've for the moment left the .Final and .GA fixversions in place for two reasons: * because we need .GA in order to allocate issues to Target Releases in the JBDS JIRA * because this lets you differentiate between things completed for the Final/GA release vs. things simply completed in a sprint. This change has already been done, in order to see the impact on downstream processes like jiralint. I've also renamed the sprints so that they include their start/end dates, rather than just "June 2016" because I figured that was more meaningful. Dates format is yyyy/mm/dd - mm/dd. You can see this on a board such as https://issues.jboss.org/secure/RapidBoard.jspa?rapidView=3410&view=p... ACTION REQUIRED: Nothing. Ref: https://issues.jboss.org/browse/JBIDE-22619 -- If you have any concerns about these changes, please post them on the associated JIRAs: _______________________________________________ jbosstools-dev mailing list jbosstools-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/jbosstools-dev